You think that the S2 controller is new? I have limited experience with it, but I don’t think so.

I think that it is just the old controller, which has been allowed to expend its footprint so that they could apply some overdue patches to accommodate the 21st century, like half decent security and Hi Res tracks.

I think that the only thing “new” about it is its name.

You know more than that?

I believe this because the switch to S2 had negligible impact upon community projects which click into Sonos s/w internals. The only significant change that I remember is that there was a change to the way the external music service authentication was handled.

Also I seem to remember reading an interview with Patrick Spence that hinted towards a new controller. 

What app are you using? I’ve been looking for an app that would play my latest additions to the music collection for years! Smart lists that play tracks I’ve never listened to and random lists that exclude certain tracks I don’t like but I don’t delete to keep the album complete.

Or did you write your own personal app?

Outburst’s solution to add “unix extensions=no” to /etc/samba/smb.conf on the Synology NAS worked like a charm for me. Remember to “sudo synopkg restart SMBService” to put the change into effect.

What app are you using? I’ve been looking for an app that would play my latest additions to the music collection for years! Smart lists that play tracks I’ve never listened to and random lists that exclude certain tracks I don’t like but I don’t delete to keep the album complete.

Hi Ivo_4,

I wrote the app. 

I sent you a PM, so we can discuss elsewhere.

Hi Vijay or Outburst,

has this workaround got any security protection advantage over running the downgraded SMBService, ie. are we more protected than when we were running SMB1?

It looks like that config change has global effect. ie affects all Windows connections to the NAS, not just connection our Music Share.

I think that’s a question you can’t really fully answer, but personally I think it’s safer to have a newer Samba version and change the smb.conf file because the newer Samba version will have other security and bug fixes that you would otherwise not have. 

And yes, it’s a global setting, but it should not affect Windows shares assuming you use SMB2/3 for those machines. This is a setting only valid for SMB1 as far as I remember. 

As Outburst has mentioned, all cybersecurity is about risk assessment. Downgrading is an all-or-nothing exercise. You fix the issue leading to the downgrade decision, but you also lose any other benefits of the release. When new upgrades are released will you have to keep downgrading? I don’t know how Synology decide to apply an upgrade to answer this question. What other vulnerabilities addressed by an upgrade are you also sacrificing? You would have to read the release notes to determine that, if such detailed release notes are available.

A configuration change is much easier to apply or undo, plus you get all the benefits of any other improvements included in the upgrade. You can (should) assess the impact of the configuration option to ensure that you are ok with the consequences of the change. The day Sonos fix the problem in Sonos 1, or you upgrade all your Sonos devices, it is simple to undo the configuration change.

 spent almost 1hr on phone top sonos, in the end just said synology firmeware issue with above 7.0 version, call them to help you roll back from version 7.2 which i am on..

sudo -i
synopkg stop SMBService
synopkg uninstall SMBService

Do you happen to know if this also works on the latest DSM 7.2 releases? I’m still on 7.1 and did the downgrade of the SMB package but I would like to have the newer features of 7.2 without losing my Sonos music access.

Just to add to this thread. My Synology is running v7.2 and it would not allow me to install the downgraded v4.10 it insisted that v4.15 was the minimum allowed, But the quoted solution appears to have worked with the edit in the config file.

Thanks to all in the community who are so active providing answers to those of us who only come when there is a problem.

+1 that this works and, i believe, a preferred solution over uninstalling and downgrading the smb.  

although it has been confirmed that this work by plm and vijay, there’s a lot more talk about the downgrading, so i’ll add another confirmation in hopes that it raises the awareness of this (imho preferred) solution.

in my search for a solution here, i did happen upon plex.  i’ve now configured the plex service for playing my music from synology.  (essentially bounces through plex when needed, but establishes a local connection when possible).   if you haven’t tried it, you might consider doing so.  i hesitatingly did it.  however plex has some capabilities that sonos’s music management is woefully poor at.    it’s not perfect, but at this point now that i have both working, i’m trying to evaluate which i prefer, and there’s a lot leaning towards plex.

I too successfully used Outburst’s solution of adding “unix extensions=no” to /etc/samba/smb.conf

I signed in via SSH (I already had it enabled, some may need to enable on DiskStation control panel.  then I typed “sudo -i” to enable writing the changes to the file.  Then I edited the file with vi appending the above as the last line.  

Another successful use of Outburt’s solution, using the post above from rich_and_poor. Thanks both.

I used the inbuilt terminal on my mac, and SSH and vi did the rest. 

sudo -i
synopkg stop SMBService
synopkg uninstall SMBService

Solution to Sonos Connect on S1 NOT granted access to Synology music folder.

The above SMB downgrade sorts out the issue….Thank you.

Hi everyone. Am having the same problem, for a long time, started a thread here too, but then was pointed to this one. I read the solution by Duncan, but….too scared to do it. Not really savvy enough with all those terms...*sigh*. 

So, have got a Synology DS 918+, Two Gen 1 Play 5 speakers, the controller sonos S1. 

Can’t get it to run neither on Win PC or Samsung mobile. 

I get the usual message to check my username password yadayada and that the access to my path to my NAS is denied. 

Is Duncan’s solution really the only way?

Many thanks….Amar

Well, silly. If the sonos app doesn’t work, which it doesn’t without me doing some major stuff I do not understand, I’ll switch to to DS audio, tried it out, works well, and maybe there are alternatives to sonos controller, that let’s you control your sonos speakers. 

Just wanted to say that this solution also worked like a charm for me. I myself couldn’t apply it, as I don’t understand a thing about it, but I had someone do that modification to my Synology NAS. Many thanks!

I have this issue too with my DS418play after updated to DS 7.x.  Very frustrating with a Sonos system that has been running pretty much constantly for 10 years (2x Connect, 2x Connect amp, 1x Play 5, 1x Play3), and Spotify etc continue to work just fine.  The NAS is clearly accessible to the network (all on Win 10).  I did try ensuring SMB1 and NVLTM1 were enabled, but I cannot point Sonos to the music library.  I don’t feel confident to be “messing” with my Synology DS418play via Linux, or downgrading to 6.x etc.  I have my (large) photographic image library on my NAS too. As an alternative, I could shift my music library to a new single-drive-bay NAS.  Can anyone recommend a brand that is known to work without this issue?  Alternatively I am willing to try the Raspberry Pi plus SSD suggestion - can anyone provide a link as to how this is constructed?

Cheaper since you already have a NAS is to use a Pi as a gateway, less power too. I tried an old Zero and it ran four FLAC streams with no problems.

This should get you there but it is a bit dated:

https://stan-miller.livejournal.com/357.html

U are right. Finally, downgrade SMB version may solve this problem. But this mustn’t be a perfect solution. Sonos technical engineers may take more care about the old users of Sonos. They may tell us why S1 cannot support SMBv2 or SMBv3. Is it a hardware problem or just they think S1 should be knocked out?

It has been discussed often, the S1 hardware does not have enough memory for the newer Linux kernel or Samba SMB application.