Sonos Connect can no longer play music after Synology SMB update

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.

It should be the x86 option from here.

Or just change the smb.conf file and stay on the latest version.

“Access Denied” is an Error Message that can apply to several different access problems, including this SMB issue.

If you successfully rolled back to the earlier SMB Version and still get the “Access Denied” like I did, try setting up a new dedicated user… named e.g. “Sonos” (instead of guest) with a new dedicated Password for your Music Folder.  Setting up a new user for a folder is one I found regarding a different problem on another site.

This worked for me after Synology was kind enough to do the rollback.… after all other attempts doing diagnostics failed after I logged the problem in Support. They will notify the DEV’s about the issue, but realistically they will need to see many complaints logged before the Red Flag to correct the issue is raised. He also mentioned that this SMB issue may not be a BUG, but a Security change.

Perhaps it’s not entirely clear. You need to access the NAS’ unix operating system directly using a terminal emulator (e.g. PuTTY) on your Windows PC in order to “stop” and then “uninstall” the SMB Service. You can’t do this from the normal NAS login to DSM.

This direct connection (to the NAS) is referred to as “SSH” (secure shell) or sometimes “using SSH-in”. The Sudo -i command might appear a bit cryptic but this is giving you root access (hence the warnings and requirement to re-enter your password etc).

It’s all OK as long as you follow the commands exactly as DuncanF shows above.

The two commands to “stop” and “uninstall” took quite a while to execute (on my low-performance DS216se) but you should eventually see a lot of gobbledegook including a confirmation of sucess after each command!

When you have completed the two steps to “stop” and then “uninstall” the SMB service, use the command “exit” to leave the terminal emulator.

Now when you log back in to your NAS in the usual way, the SMB service will have gone so you must then re-install it from Package Centre. The point is you must use the “manual install” option to install the older SMB Service that you downloaded NOT the default one which is the recent update that caused all the problems for Sonos S1 users.

Sorry if I’m stating the obvious, just trying to help out.

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.

I, too, had a cause-and-effect experience today after updating my Synology NAS to the last version of DSM.  And so I spent hours on this, blowing my entire Saturday.  And now it’s fixed, but I can’t be 100% certain why.  I will share this:

• I had basically given up and started searching for an alternative.  After striking out with attaching a USB drive to my router, I landed on attaching the drive drive to one of my Windows 10 boxes, then sharing a folder on said drive containing my music.
• I ran into the usual Microsoft headaches, and after futzing with my 3rd party firewall and internet security app and changing the Microsoft network sharing settings to “no password required”, I finally made a small bit of progress by proving that Sonos could access the music on the drive.
• This process required me to use the Sonos desktop app to add a shared music folder by browsing to a folder on my PC. Part of this process involved the Sonos app asking for permission to access this new shared folder, and doing something behind the scenes to make it work. This process gave me a file system tree to browse, which got me thinking:  since it worked when sharing my USB drive folder, why not take one more shot at browsing to my NAS folder through this tree.  Note that this was different from the failed approach I took prior to this, which was to use the option for entering the path to a “Networked device (ex. NAS drive)”.  Instead, I clicked on Sonos’ option to add music via “Another folder or a drive connected to my computer”.  I browsed to my NAS folder via the tree, and it freakin’ just worked.

I don’t know how useful this is to any of you or if it will work in your case.  And, of course, I was trying so many things for hours that didn’t work wrt both Windows and Synology folder sharing and permissions options.  I honestly don’t know if what I’ve described above would have worked had I tried it first.

I hope this helps.  It’s a simple approach that might be worth a shot.  I recommend using a test folder within your library, because it took almost 45 minutes for Sonos to reconstruct its database from my huge library.

SMB 1 is enabled, NTMLv1 is checked.  Username and password correct.  All folder permissions are correct.

I am able to add the music library but still receive the Access Denied error when a song is selected to play.

I wouldn’t put my primary NAS at risk by allowing SMB v1 but there are many other fairly simple solutions to providing SMB v1 connections to your music so you can safely use the antique S1 only Sonos units.

An inexpensive SMB v1 NAS, like a Raspberry Pi or the many clones works for many. A bit more interesting is an SMB v1 gateway to your primary NAS music collection.

Sorry you haven’t seen my many posts on the work-around options:  (both a bit dated but should work)

SMB v1 Gateway  https://stan-miller.livejournal.com/357.html

SMB v1 NAS for Sonos  https://stan-miller.livejournal.com/650.html

There are also many posts here discussing the memory limits with explanations that are simple to follow or with technical data that most aren’t interested in. You can of course do your own research both on the internal Sonos memory and the requirements for the current Linux code and Samba server code.

Windows file mounts for one. But you can enable SMB3 with the 4.10 pacakge.

sudo-i
synopkg stop SMBService
synopkg uninstall SMBService

Thanks so much for posting this.  It worked perfectly for me too running a DS920+.  

I’ve raised a support ticket with Synology just to add to others with the vain hope they might issue a fix.  I very much doubt SONOS will do anything as they’ve been trying to move everyone off S1 units for a long time.  However with 6 SONOS amps in the house I simply can’t afford to replace them all.  On top of that they do everything I need them to and I really don’t see a need to replace perfectly operational units.

However I suspect updates like these will eventually render our S1 units unusable…….😞

An update a while back required the ‘Enable NTMLv1 Authentication’ option to be set.  That is in my case, and I’m seeing the issue. The log files show the Sonos Connect connecting successfully to the NAS, but the Sonos app is throwing the error.

Hi @DuncanF 

Correct - you get one hour to edit.

I have added the space for you.