Access Denied to Music on Synology Drive



Show first post
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.

50 replies

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 for posting this solution.  And Sonos -- please, please get your act together on this topic.

Thanx for the information. This did it for me too! 

I’ve given up on Synology as my NAS solution for my ripped music. Way too involved to get it to work the way I need it to (yes I have too much stored music) and the WD MyClouds work perfectly with shares and specifying actual folders and even specific subfolders when necessary. Thanks for all the insite.

 

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.

 

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.

Userlevel 6
Badge +15

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 :)

Userlevel 7
Badge +21

I’m sure such motivational words will have Sonos employees positively skipping to work ;)

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 @BillFair.  Solution worked for me as well. 

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. 

Userlevel 2

I had already a sonos dedicated user account before updating to 7.0, and suffered the same denied access. BillFare solution worked at once. Thanks!!!

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!

Reading this comments here solved my problem finally before I go nuts….Enabling the NTLMv1 worked for me - thanks!

Thanks BillFair - this solved my problem as well.

Great to hear that the NTLMv1 solution from Bill Fair worked so well for numerous people. Well done Bill! Accordingly, I implemented that fix (after updating to DSM 7.0) but, alas, it didn’t work for me. Does anyone have any other suggestions? I’m a computer luddite, so need a reasonably complete explanation (and have found the ones in this thread comprehensible).

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.

Hey, man. Good to see ya. S1. A few pieces are too old for S2.

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?

The same as before. No change. 

Assuming you have a firewall set up, still relatively low, as long as you keep it updated, IMHO. 

Help me with this, Bruce, if you can… Previously:

 

\\MyBookLiveDuo\Jazz was the share. Easy enough to do on the WD. I created a folder called Music, and under that folder was Jazz, and I shared it. I can’t get it set up the same way on the Synology. I don’t want to create just a \\Jazz share… I’d like all shares to be under a music folder. Any idea or link on how to set this up? It is defying all my IT experience. Thanks for any help.

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 ! 

 

Unfortunately, I’m unable to help. I’m a WD MyCloud user, and have no working knowledge of the Synology system. Not to mention why it should be any different in use than the WD setup…

I’d try calling the folks at Sonos, I’d imagine they have some sort of script for this. 

Would be interested in what you find out, though. The fans on my WD are failing, and expect a Synology is in my near future. 

I am mildly concerned about your use of S1 still, though. Makes me wonder if there’s some setting in the Synology, either SMB v1, or NTML v1, that’s not set properly. I’ve seen quite a few posts that suggest that OS updates to NAS devices frequently change these settings without explicit declaration. Have certainly experienced that before with WD. And Vizio, on my TV’s audio settings. Didn’t figure that out for several days, when I noticed that surround data wasn’t being played. 
 

Sonos, please update asap. I also took a lot  of time to figure out what was going on.  I can’t believe Sonos actually wants to force it clients to run any security risks.