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?
Best answer by dlipetz
View original
I find the logic unusual. Sonos operated under one operating system from 2005 until S2 was released in August of 2020. Why would they need to bring out this supposed S3 so soon?
You think that the S2 controller is new? I have limited experience with it, but I don’t think so.
I think that it is just the old controller, which has been allowed to expend its footprint so that they could apply some overdue patches to accommodate the 21st century, like half decent security and Hi Res tracks.
I think that the only thing “new” about it is its name.
You know more than that?
I believe this because the switch to S2 had negligible impact upon community projects which click into Sonos s/w internals. The only significant change that I remember is that there was a change to the way the external music service authentication was handled.
Also I seem to remember reading an interview with Patrick Spence that hinted towards a new controller.
Collecting becomes pointless without smart playlists and browsing indices, that enable shrinking the collection to a smaller scale when the mood requires, eg.
* just albums that I have not heard for a year and a half
* or jazz albums that I brought in the last 2 years, which I have played less than 5 times
My app:
* detects and identifies everything I play on Sonos, and separates it from tracks played by other household members
* it aggregates these plays, with tracks that it has identified that I have played, away from home, on non-Sonos equipment
* all play data is fed into a MediaMonkey database, from which I can browse, and|or publish album level playlists for use in Sonos and elsewhere, or to sync albums into my mobile devices.
What app are you using? I’ve been looking for an app that would play my latest additions to the music collection for years! Smart lists that play tracks I’ve never listened to and random lists that exclude certain tracks I don’t like but I don’t delete to keep the album complete.
Or did you write your own personal app?
Outburst’s solution to add “unix extensions=no” to /etc/samba/smb.conf on the Synology NAS worked like a charm for me. Remember to “sudo synopkg restart SMBService” to put the change into effect.
What app are you using? I’ve been looking for an app that would play my latest additions to the music collection for years! Smart lists that play tracks I’ve never listened to and random lists that exclude certain tracks I don’t like but I don’t delete to keep the album complete.
Hi Ivo_4,
I wrote the app.
I sent you a PM, so we can discuss elsewhere.
Outburst’s solution to add “unix extensions=no” to /etc/samba/smb.conf on the Synology NAS worked like a charm for me. Remember to “sudo synopkg restart SMBService” to put the change into effect.
Hi Vijay or Outburst,
has this workaround got any security protection advantage over running the downgraded SMBService, ie. are we more protected than when we were running SMB1?
It looks like that config change has global effect. ie affects all Windows connections to the NAS, not just connection our Music Share.
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.
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.
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..
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
sudo -i
synopkg stop SMBService
synopkg uninstall SMBServiceThis 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.
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.
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.
Enter your username or e-mail address. We'll send you an e-mail with instructions to reset your password.