Let me add something here which might help others having difficulty with Sonos and Synology. I recently updated my NAS with DSM 7.0, which immediately broke Sonos access to the shared Music drive on the Sonos. The solution for me, as suggested by others in similar posts, is to go to the SMB settings under File Services, then Advanced, and then other. There is a setting called enable NTLMv1 authentication. Once you do, you will get a nasty warning message about potential vulnerabilities with this aging standard. This fixed the problem for me.
The key takeaway is that Sonos needs to update its SMB protocols to a higher standard, in the interest of greater security. While the future is streaming, many of us still have lots of audio files on servers that we want to use with our systems.
Let me add something here which might help others having difficulty with Sonos and Synology. I recently updated my NAS with DSM 7.0, which immediately broke Sonos access to the shared Music drive on the Sonos. The solution for me, as suggested by others in similar posts, is to go to the SMB settings under File Services, then Advanced, and then other. There is a setting called enable NTLMv1 authentication. Once you do, you will get a nasty warning message about potential vulnerabilities with this aging standard. This fixed the problem for me.
The key takeaway is that Sonos needs to update its SMB protocols to a higher standard, in the interest of greater security. While the future is streaming, many of us still have lots of audio files on servers that we want to use with our systems.
There’s already user community/Staff awareness about support for the later SMB encrypted transfer of music files mentioned in this rather long thread…
It at least shows Sonos are aware of the issue.
@BillFair thanks I had the same issue. I upgraded to DSM 7.0, Sonos could see my music library but I kept getting access denied when trying to play a song from my Synology. I was about to enable NTLMv1 but got scared with the warning messages. I was still stumped and only solved it when I saw this post and enabled it and it all worked.
So thanks for sharing. I was going nuts because the Music folder on my NAS was accessible from Windows 10 via file explorer
\\IP_address_of_NAS\Music_Folder_Name_on_NAS
in Sonos it is accesses via
//IP_address_of_NAS/Music_Folder_Name_on_NAS
Let me add something here which might help others having difficulty with Sonos and Synology. I recently updated my NAS with DSM 7.0, which immediately broke Sonos access to the shared Music drive on the Sonos. The solution for me, as suggested by others in similar posts, is to go to the SMB settings under File Services, then Advanced, and then other. There is a setting called enable NTLMv1 authentication. Once you do, you will get a nasty warning message about potential vulnerabilities with this aging standard. This fixed the problem for me.
The key takeaway is that Sonos needs to update its SMB protocols to a higher standard, in the interest of greater security. While the future is streaming, many of us still have lots of audio files on servers that we want to use with our systems.
Thank you very much, fixed my issue for me!
Thanks BillFair! “ enable NTLMv1 authentication “ worked for me too.
Sonos needs to update its SMB protocols to a higher standard, in the interest of greater security.
But it doesn’t.
When you charge premium prices you should do better Sonos
This is a good trick if you cannot wait for the SMB2/3 update and if you don’t want to drop your security settings for your Synology NAS as a whole.
I am not sure as customers that we should have to do all this to ‘stick a plaster’ on the problem for Sonos, they should resolve it and not expose their customers into having insecure settings within their network - this is not acceptable but even more so given the price tag of Sonos equipment.
Agree 100%. Just offering someone’s ready-right-now solution.
I have already sent the CEO the request to fix SMB2/3 and also to filter out incompatible files or at least downsample high resolution audio that’s on a music library.
Thank you so much Bill. Many hours of aggro and scratching my head and swearing...a lot!!
FFS Sonos, keep up with latest security and be more on-the-ball with the likes of the hugely popular and brilliant Synology drives. We should have to figure this stuff out for ourselves and rely on clever and kind people like Bill!
I am not sure as customers that we should have to do all this to ‘stick a plaster’ on the problem for Sonos, they should resolve it and not expose their customers into having insecure settings within their network - this is not acceptable but even more so given the price tag of Sonos equipment.
Well it appears the update is coming from Sonos, based on the information seen in the link below, but I guess these things do take time and have to be fully tested before they can be made available to all. We just have to be patient and wait for any announcement, but in my view probably more security risks come from poorly configured SMB NAS shares and local network security implementation, than they do from the wannacry or petya exploits .. Anyhow see this link:
https://en.community.sonos.com/advanced-setups-229000/smb1-security-issue-lack-of-response-from-sonos-6860761?postid=16551779#post16551779
Enabling an insecure protocol isn’t a solution. Sonos needs to implement smbv2.
Enabling an insecure protocol isn’t a solution. Sonos needs to implement smbv2.
They’re doing that by all accounts, according to the information provided in this thread …
I had just the same problem: once updated Synology NAS to DSM7, with NTLMv1 disabled by default, SONOS cannot connect anymore.
I solve by enabling NTLM1 on Synology, but this represents a security issues.
I kindly ask SONOS to considering implementing support to NTLMv2 as soon as possible.
Let me add something here which might help others having difficulty with Sonos and Synology. I recently updated my NAS with DSM 7.0, which immediately broke Sonos access to the shared Music drive on the Sonos. The solution for me, as suggested by others in similar posts, is to go to the SMB settings under File Services, then Advanced, and then other. There is a setting called enable NTLMv1 authentication. Once you do, you will get a nasty warning message about potential vulnerabilities with this aging standard. This fixed the problem for me.
The key takeaway is that Sonos needs to update its SMB protocols to a higher standard, in the interest of greater security. While the future is streaming, many of us still have lots of audio files on servers that we want to use with our systems.
Many thanks for sharing your knowledge!! It works now. Best.
+1. “enable NTLMv1 authentication” worked for me on 7.0. Thanks for sharing.
Hey, man. Good to see ya. S1. A few pieces are too old for S2.
Let me add something here which might help others having difficulty with Sonos and Synology. I recently updated my NAS with DSM 7.0, which immediately broke Sonos access to the shared Music drive on the Sonos. The solution for me, as suggested by others in similar posts, is to go to the SMB settings under File Services, then Advanced, and then other. There is a setting called enable NTLMv1 authentication. Once you do, you will get a nasty warning message about potential vulnerabilities with this aging standard. This fixed the problem for me.
The key takeaway is that Sonos needs to update its SMB protocols to a higher standard, in the interest of greater security. While the future is streaming, many of us still have lots of audio files on servers that we want to use with our systems.
There’s already user community/Staff awareness about support for the later SMB encrypted transfer of music files mentioned in this rather long thread…
It at least shows Sonos are aware of the issue.
I really thought of buying some more sonos devices for my whole family. But now I have to accept security issues in the future. Seems that I have to switch to another vendor if there is no update from sonos !
Thanks @BillFair. You are a legend!
Hi @49ermuse, thanks for sharing this with the Sonos Community! I’m sure this information will be able to help others who may be having trouble with Synology NAS drives :)
Hi, maybe recent updates have solved the issue. At present no problem at all for me after some adjustments. Sonos Connect. Synology 218 play. Windows 10 PC, on a wired connection and 2 Macs running OS 12 Monterey and Sonos app wireless.
SMB and AFP enabled so that the NAS software DSM can talk to the PC and Sonos and to the Macs.
At first Synology and Sonos collided on the wifi. Synology was discovered by my iPhone but not Sonos. Wired connection solved that problem.
Now everything seems to work. I haven’t fiddled with different settings of SMB or NTLMv1.
I have a WDMyCloud and a QNAP NAS as well building up the library on Sonos.
One other item if you get to the end of this thread.
In the File Services » SMB » Advanced Settings, make sure you set the minimum setting to SMB1 as I had missed it and by default it is probably SMB2 if you took the defaults.
enjoy
Thanks @kiddude
I am on DSM 6.2.4 so don’t have the NTLMv1, but still needed to adjust the minimum setting to SMB1 via File Services>SMB Advanced settings
Very helpful!
Huge thanks to you, BillFair. I think it’s a damn miracle that I found your post. After wondering why my path was no longer good, and searching for solution for an hour and half, I stumped upon your post. Many, many thanks!
Thanks for this fix. My WD MyBookLiveDuo is dying a slow death. I’m moving everything over to my eight disk Synology… how insecure is this now? Can’t seem to find an answer out there.
Depends on if you’re using S1 or S2. S2 now can use up to SMB v3.
Thanks BillFair - this solved my problem as well.
There’s been no ability to make any changes to S1, there’s apparently not enough memory available to update the kernel to allow other versions of SMB. So from your perspective, nothing has changed.
Yeah, but how at risk am I now?
