Enthusiast I

Answered

Sonos Connect can no longer play music after Synology SMB update

Forum|Forum|3 years ago
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”

Show previous replies

D

dlipetz

Avid Contributor I

Hello,

i coulnd´t install the x86 file - error - this package isn't supported or compatible!?! any ideas - restarting the disk station doesn't help. DSM 7.1.1-42962 Update 5

Use @sjw solution, no need to downgrade SMB software, just a minor change to file. Worked great for me! See post a few up with link.

T

tomlangbroek

Lyricist I

Perfect solution, thanks a lot!

M

MSHHH

Lyricist I

YES!!! Everything works! THANK YOU!!!

A

andyh747

Avid Contributor II

I raised a support ticket with Synology and after several emails with support here is their response to this issue:

After investigating the issue, we have found that the problem is caused by the default server response of Samba v.4.15 to a specific client command (SET_FS_INFO) sent by the Sonos S1 device. Synology has followed the specification from Samba and has not implemented a proprietary solution, meaning that any SMB server that uses open-source Samba version 4.15 may encounter this same issue.

By adding unix extensions=no as a default option in the Samba configuration file would make the NAS less secure and therefore is not a viable solution. We fully understand that updating to SONOS S2 is not financially viable for many users, and we apologise for any inconvenience caused. However, we would like to assure you that we take security very seriously, and therefore cannot sacrifice security for backward compatibility.

So it appears the only solution is either staying or downgrading to a previous version of SMB on Synology or modifying the SMBService config file as described previously.

ozzerbyjohnny

Contributor I

YES! You brilliant man, DuncanF!! THANK YOU!!!

BarryM

I have the same problem after upgrading the SMB package on my Synology NAS.

I will look at the fix described by DuncanF later (thanks!) , but in the meantime I got the unit playing by the following:

queue|play the tracks to a newer Sonos unit (I have the problem on one of the original Play:5 units)
then add the failing unit to the group (drop the volume on the original unit if you want)

That gets the music happening again.

I

Ivo_4

Trending Lyricist I

Thanks for the downgrade hack, it worked. I did have to reboot in between stop and uninstall, could not uninstall without it. Let’s hope this will work with the latest OS update 7.2.

I

Ivo_4

Trending Lyricist I

Is the SMB downgrade still working with 7.2 or did the latest Sonos app update solve the issue?

BarryM

Hi Ivo,

this is just my opinion, but I don’t believe that Sonos have any intention of fixing this issue.

They have long claimed that the early Sonos units have insufficient memory to allow upgrade to the more secure version of the s/w component that is causing the connection problem.

I don’t know if this is factual, but anyway they have long since stopped upgrading their S1 controller. My guess is that the latest “upgrade” is just another downgrade, ie. it removes the capability to play local tracks, on an android device, to your Sonos units.

The connection “problem” has been with us for a long time. Previously the Sonos Apologists in this forum have said that it is not a real-world problem, and that it can be readily worked around. In the past I have asked for the recipe for that workaround, but I have not seen any response to that.

What has happened now is that Synology, unlike the Sonos S1 controller, have continued evolving their package. They have zero interest is leaving their units open to exploitation, and they have follow best practice to protect their reputation and their customers’ data.

I don’t to know enough to understand exactly how serious this problem is. You can research it yourself by searching “smb1 vulnerability”.

eg “Do NOT use SMBv1. SMB1 lacks encryption, is inefficient, and has been exploited in the wild by ransomware attacks.” from here

The Sonos S1 controller uses SMB1

Stanley_4

Grand Maestro

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.

Show more replies

Sign up

Login to the community