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

Airgetlam
April 13, 2023

I’m a little confused. You mention both S2 and S1. Are you running both OS on different “systems” in your home?

S1 does indeed require SMB v1 and NTMLv1 in order to connect. For what it’s worth, I’ve had SMBv1 turned off by “updates” to my NAS’ firmware, without regard to whether I had it turned on or not. It’s always worth logging in to the NAS to confirm that those settings have not been changed for you, without your input. 

It may be worth a call Sonos Support directly to discuss it. They may have more knowledge about the specific update to your Synology device, and certainly any hard data in  a system diagnostic might be helpful in tracking down where the interruption is coming from. 

When you speak directly to the phone folks, they have tools at their disposal that will allow them to give you advice specific to your Sonos system and network. 

Bruce
Lyricist II
April 13, 2023

Same here.  Only running s1 app and after SMB Update, this…..

 

Airgetlam
April 14, 2023

As a guess, the Synology update turned off SMBv1.

Bruce
Enthusiast I
April 14, 2023

As a guess, the Synology update turned off SMBv1.


It’s still there and active but I get the “Access is denied…check the username and/or password” error.

 

Other S2 products (using the same connection credentials) work just fine,

Lyricist II
April 14, 2023

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.

Enthusiast I
April 14, 2023

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 removed and tried to re-add the library settings, but I can’t get that far now.  There are no errors in the Synology logs. In fact everything looks ok there. 

Airgetlam
April 14, 2023

So, what did Sonos Support say, when you called in? 

Unfortunately, I’m no longer running S1 to do any relevant tests. 

Bruce
Enthusiast I
April 17, 2023

After a lengthy call to Sonos support, the conclusion was that everything is working correctly at the Sonos layer and have been asked to contact Synology.  
 

I’ve raised a ticket with Synology and I’m awaiting their response. 

Airgetlam
April 17, 2023

Thanks for keeping us updated. 

Bruce
Lyricist II
April 17, 2023

Same story here. I seem to remember having this problem a few years ago after a Synology update to SMB, but I don’t remember how it was resolved.

Following this for a solution (hopefully).  Thank you.