Sonos Connect can no longer play music after Synology SMB update

Hmm. I did nothing more nor less that I laid out above. And for some reason, I had no need to reboot.

Just to be clear, you need to stop/uninstall the service via a Linux terminal, not from the user interface in a browswer. I don’t know if it is even possible to unistall via the UI, hence the need to use a Linux terminal window.

When you stop the service via the command line in a terminal window, you should get a JSON response with loads of 0’s in, which I took to be a good thing. A smaller but similarly positive response when I uninstalled the service from the command prompt.

Now you go to the UI and install the new SMB package via the  Package Manager.

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.

But this is just not a solution for many users. We need Sonos and Synology to communicate.

Any Sonos Staff online?

As more of us who use a NAS (Synology in my case) to supply our Music Library’s to our SONOS Systems discover access is now denied, we are again faced with the unintended results of updates that have rendered our systems useless in this way..

Would anyone in the community help those of us who are not familiar and/or comfortable in performing what appears to be a solution using PuTTY?

Having been through this before with similar issues, we need a clearly written STEP by Step Instructional detailing how to perform the Uninstall of the problematic SMB Version using PuTTy.

Screen Captures of each step would be a great addition to its procedure.

I know we would be grateful for anyone who has experience (and success!) in performing this modification in having a method to do this that anyone could attempt.

Thanks all….

Thanks, followed DuncanF’s instructions (expect for the missing space for the sudo -i command) and it all worked a treat. No reboot and only took a a few minutes. I just used the Terminal app on my Mac.

Obvious frustration that Package Centre will keep reminding me the SMB package can be updated, but not as frustrating as not being able to access my Music Library on all my SONOS devices. Odd it effected some ZP120s but not all.

One note, if you have SSH disabled by default (as I do) you need to turn it on for access, and if you want turn it off again when done.

Finally I am not sure who to be annoyed at, Synology for breaking something, or Sonos for not getting a very old protocol standard updated on older devices.
 

I appreciate the rollback instructions, I was able to do that.  However still no connectivity. Before the rollback I reset sonos user password to the share and also deleted the share paths in sonos in a poor attempt at resolving things.  Trying to re-add those libraries now fails with access denied despite me knowing 100% that the user and password entered are correct. No logging of use Synology side to help so kind of SOL right now.

As has been covered many times in many threads, there is not enough memory available on S1 devices to update the Linux kernel with a newer version of SMB. You can blame Sonos, I suppose, for not inflating the original purchase price of the devices in order to fit more RAM in, if you wanted to. 

Remember that it won’t work with Sonos S1 unless you have set the SMB parameters correctly in the NAS DSM i.e.

Control Panel - File Services - SMB - Advanced Settings - General - Minimum SMB Protocol = SMB1

and

Control Panel - File Services - SMB - Advanced Settings - Others - Enable NLTMv1 authentication = Ticked

If that dosn’t fix the problem then I’ve no idea!

“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.

DuncanF thank you so much for this. I had to remove Active Backup on the Synology since there were dependencies with SMB Service but after that everything worked. I added Active Backup back in after and it is perfect. 
thank you!