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

Stanley_4
Grand Maestro
April 30, 2023

If Sonos is working on other NAS devices Sonos isn’t likely to get too deep into another manufacturer’s problem.

I had many NAS issues, picked up a Raspberry Pi computer and pulled an old SSD from my scrap box and it happily runs my music library with zero issues.

DuncanFAnswer
Trending Lyricist II
April 30, 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”

Enthusiast II
April 30, 2023

Got the exact same issue here. Been using Sonos for 10+ years and have no reason to ditch my Play 5 speakers for new ones….. I think this issue is really annoying and think that Sonos and Synology ought to have a chat and fix this very soon. Don't wanna downgrade my SMB since the upgrade must be there for a reason…..

Contributor I
April 30, 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.

Why would this make a difference as I have been into Synology and ensured that SMB 1 to 3 is available?

What else uses SMB?

Enthusiast II
April 30, 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). 

Lyricist II
April 30, 2023

Thanks DuncanF

Downgrading the SMB service sorted the Sonos S1 snag for me.

If you use Sonos S1 players avoid that recommended SMB service upgrade from Synology. If ever there was an example of “if it ain’t broke don’t fix it” then this was it!

These Notes might help if you’re not familiar with using the direct connection into the NAS:

1// Search for “SSH in to a Synology NAS” for details on how to use PuTTY etc to make the connection.

2// It all works as described, the commands are case sensitive.

3// You have to select the correct SMB file (*.spk) from the list to match the CPU in your NAS which can be found in NAS DSM Control Panel - Info Centre.

4// I had to re-start my NAS after uninstalling the SMB Service before the downloaded one would install.

5// I had to re-start my NAS again after re-installing the SMB Service before it became “enabled”.

6// Some of the steps take quite a while to execute.

Best of luck.

Avid Contributor III
April 30, 2023

I too just discovered Denied access VIA smb 1….  

The SMBService  Parent Directory Lists 10 different versions (.spk) of the previous version of SMB to install…. I use a 920+, and would appreciate any help in determining which SMB Version I should install…

The 920+ uses the Intel Celeron J4125…..  Just not seeing a clear link from it to the replacement choice of SMB File…..

 

Thanks! 

Trending Lyricist II
April 30, 2023

I too just discovered Denied access VIA smb 1….  

The SMBService  Parent Directory Lists 10 different versions (.spk) of the previous version of SMB to install…. I use a 920+, and would appreciate any help in determining which SMB Version I should install…

The 920+ uses the Intel Celeron J4125…..  Just not seeing a clear link from it to the replacement choice of SMB File…..

 

Thanks! 

You’ll need the “...x86...” version.

Trending Lyricist II
April 30, 2023

Why would this make a difference as I have been into Synology and ensured that SMB 1 to 3 is available?

What else uses SMB?

 

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

Avid Contributor III
April 30, 2023

Thank you Duncan for that little hint!

I’m now encountering the inability to “uninstall” the SMB Service from the Package Center.

I’ve done the following:

 

For DSM 7.0 and above:

  1. Go to Control Panel > File Services > SMB and click Advanced Settings.
  2. Select Force from the Enable server signing drop-down menu to enable it, or select Disable to disable it, and click Save.

However when I go into the Installed Packages, it shows the SMB Service still running, and the “OPEN” Drop-Down only shows “Auto-Update” as a option.

Must be missing something simple….  

 

marc