Skip to main content
Enthusiast I
April 13, 2023
Answered

Sonos Connect can no longer play music after Synology SMB update

  • April 13, 2023
  • 96 replies
  • 12588 views

My Sonos Connect can no longer play any music following an update to the SMB package on my Synology drive.

 

I’ve followed the guides about setting up the appropriate SMB1 access allowing NTLM access, but when I try and connect, I just get “access denied” even though my S2 products are pointed at the same share.

 

The NAS logs show the S1 product connecting but the Sonos app is throwing the error.

 

Has anyone else experienced this and does anyone have a solution?

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 DuncanF

I found this thread this morning after updating my DS918+ yesterday and not being able to use my Sonos (all S1) Connects. Fortunately I found a solution on Reddit, but I thought I’d paste here for others who have this issue.

The solution is simply to downgrade the Synology SMB package from 4.15.x (Apr-2023) to 4.10.x. I used the final version of 4.10 (4.10.18-0548 dated 22-Dec-2022). You can download individual packages from Synology’s archive here: https://archive.synology.com/download/Package/SMBService

  • Login to your NAS using Putty or similar. Stop the SMB service and uninstall it. 
sudo -i
synopkg stop SMBService
synopkg uninstall SMBService
  • Logon to your NAS in a browser. Go to the Package Centre and click “Manual Install”. Select the package you downloaded and install it.
     
  • Finally go to the Control Panel and re-enable SMB (File Services → SMB). Don’t forget to double check that NTMLv1 is enabled (File Services → SMB → Advanced → Others).

This takes only a few minutes and, for me, it restored my Sonos capability. YMMV. Obviously make sure you have appropriate backups in place.

 

Moderator edit: added space to “sudo -i”

96 replies

Enthusiast II
May 30, 2023

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. 

Lyricist I
June 18, 2023

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.

Lyricist I
July 7, 2023

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

Trending Lyricist I
September 1, 2023

I found this thread this morning after updating my DS918+ yesterday and not being able to use my Sonos (all S1) Connects. Fortunately I found a solution on Reddit, but I thought I’d paste here for others who have this issue.

The solution is simply to downgrade the Synology SMB package from 4.15.x (Apr-2023) to 4.10.x. I used the final version of 4.10 (4.10.18-0548 dated 22-Dec-2022). You can download individual packages from Synology’s archive here: https://archive.synology.com/download/Package/SMBService

  • Login to your NAS using Putty or similar. Stop the SMB service and uninstall it. 
sudo -i
synopkg stop SMBService
synopkg uninstall SMBService
  • Logon to your NAS in a browser. Go to the Package Centre and click “Manual Install”. Select the package you downloaded and install it.
     
  • Finally go to the Control Panel and re-enable SMB (File Services → SMB). Don’t forget to double check that NTMLv1 is enabled (File Services → SMB → Advanced → Others).

This takes only a few minutes and, for me, it restored my Sonos capability. YMMV. Obviously make sure you have appropriate backups in place.

 

Moderator edit: added space to “sudo -i”

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.

Contributor I
November 19, 2023

I’m not sure whether this is an option on Synology drives, but instead of downgrading one could add “unix extensions = no” to the smb.conf file. Samba 4.15 includes a security change that makes this addition needed for some devices (old Linux Kernels). 

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.

Lyricist I
November 20, 2023

I’m not sure whether this is an option on Synology drives, but instead of downgrading one could add “unix extensions = no” to the smb.conf file. Samba 4.15 includes a security change that makes this addition needed for some devices (old Linux Kernels). 

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.

Lyricist I
December 17, 2023

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.  

Lyricist I
December 22, 2023

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. 

Lyricist I
January 2, 2024

I found this thread this morning after updating my DS918+ yesterday and not being able to use my Sonos (all S1) Connects. Fortunately I found a solution on Reddit, but I thought I’d paste here for others who have this issue.

The solution is simply to downgrade the Synology SMB package from 4.15.x (Apr-2023) to 4.10.x. I used the final version of 4.10 (4.10.18-0548 dated 22-Dec-2022). You can download individual packages from Synology’s archive here: https://archive.synology.com/download/Package/SMBService

  • Login to your NAS using Putty or similar. Stop the SMB service and uninstall it. 
sudo -i
synopkg stop SMBService
synopkg uninstall SMBService
  • Logon to your NAS in a browser. Go to the Package Centre and click “Manual Install”. Select the package you downloaded and install it.
     
  • Finally go to the Control Panel and re-enable SMB (File Services → SMB). Don’t forget to double check that NTMLv1 is enabled (File Services → SMB → Advanced → Others).

This takes only a few minutes and, for me, it restored my Sonos capability. YMMV. Obviously make sure you have appropriate backups in place.

 

Moderator edit: added space to “sudo -i”

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

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

Trending Lyricist I
January 9, 2024

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