Skip to main content
Contributor I
May 8, 2023
Answered

Cannot connect to Synology NAS

  • May 8, 2023
  • 13 replies
  • 2094 views

I have two pieces of Sonos gen 1 gear (a Play:5 and a Connect), which I use to play songs kept on my Synology NAS.  I have SMB1 and NTLMv1 authentication both enabled.  This used to work fine, but as of the last Synology software update it fails.

No other devices on my home network (and there are many) have any issues; it is only my Sonos gear.

I have seen many other posts with this same issue, and your response in all cases that I’ve seen is that this is my problem because I’m still on S1, and you’ve fixed this in S2.  Fine, how do I run S2?  What is my upgrade path?  Because if the upgrade path is to throw out all my Sonos gear and spend over $1000 on new gear, that doesn’t really work for me.

This topic has been closed for further comments. You can use the search bar to find a similar topic, or create a new one by clicking Create Topic at the top of the page.
Best answer by sjw

There seem to be a couple of options - one downgrades the updated SMB addon and the other edits the smb.conf file.  Both solutions need a small amount of technical knowledge and accessing your NAS via PUTTY.

The latter option is detailed here.

13 replies

Airgetlam
May 8, 2023

In the other threads, there has been a solution posted.

However, this change was made by Synology, not Sonos. It feels like your anger is misplaced. Sonos has not altered anything on their side of the equation. 
 

Bruce
Contributor I
May 8, 2023

If you could point me to a solution, I’d appreciate that--every post I could find that offered a solution either said to enable SMB1 or enable NTLMv1 authentication.  I have enabled both. 

I disagree about whose fault this is--Sonos has elected not to support their older gear on their newer software platform, and has elected not to continue development on the older software platform they require me to use.  They are the only equipment provider I have that has this problem--every other hardware producer can work with Synology NAS’s.

Airgetlam
May 8, 2023

I’d start with this thread:

 

 

@sjw has provided links to other threads inside that thread, as well.

I’m not sure exactly how you expect Sonos to put new software on devices that don’t have the RAM/CPU available to hold that new software. My ‘386 computer with a 512 Meg HD won’t run Windows 11. To whom should that blame be apportioned?

Bruce
sjwAnswer
Local Superstar
May 8, 2023

There seem to be a couple of options - one downgrades the updated SMB addon and the other edits the smb.conf file.  Both solutions need a small amount of technical knowledge and accessing your NAS via PUTTY.

The latter option is detailed here.

Contributor I
May 8, 2023

@sjw: thanks!  Disabling unix extensions did it for me.  (And mad props for walking people through how to use vi)

Local Superstar
May 8, 2023

Yeah, vi 101 🤣

Lyricist I
May 14, 2023

Editing SMB.config did unfortunately not do anything for me/my Setup . Have not yet tried downgrading SMB addon but it appears do be considerably more complicated than editing SMB.config.

irrespective of who‘s responsible, my system is currently just useless. If there is no easy fix soon I am going to replace either the NAS or the sound system with another provider. And will not likely go back to the replaced one for the foreseeable future.

Stanley_4
Grand Maestro
May 14, 2023

Since no other NAS company seems to have the issues I’d change brands there.

My dirt cheap NAS solution, a Raspberry PI and plug-in USB music storage drive has worked flawlessly for years.

Airgetlam
May 14, 2023

Honestly, I’d just upgrade to S2, and if necessary, replace any device that is S1 only. Computers ( which is what Sonos devices are ) do age out. 

Bruce
Contributor I
May 14, 2023

The root issue is that SMB1 has problems--it is insecure and very chatty on the network; SMB2 is a far better protocol.  The problem is that Sonos elected not to support SMB2 in their S1 systems, even though the protocol was well-established while they were selling product.  Essentially, Sonos requires your NAS to use an insecure, suboptimal protocol.

All the solutions to this problem involve forcing the Synology NAS to be less secure and to chew up more network bandwidth.  The fact that Synology alone of all the NAS providers has its systems more secure and more efficient by default is evidence that they are doing the job better than their competition, not worse.

Upgrading Sonos gear to S2 is a very expensive remedy, and one that rewards Sonos for doing a poor job engineering their S1 systems, and a worse one in customer service.  SMB2 was released in 2006; Sonos was selling S1 systems long after that (I bought mine in 2013, I believe).  This is not a case of computers aging out, this is a case of a company selling ancient technology and then bailing on it without offering their customers an upgrade path.