Answered

Access denied to Synolog NAS server – can’t play files in one room other rooms are fine?

K
Userlevel 2
Badge +5

Access denied to Synolog NAS server – can’t play files in one room other rooms are fine?

 

I am a long time user of Sonos. I have 4 zones that all uses S1. I do have a Roam also (S2) but hardly ever uses it at my home.

 

My zones are: 

 

Office: two Play 5: gen1

Livingroom: Soundbar, Sub and two Play:3

Room 3: Play:1

Room 4: Play:1

 

I do have a booster as well. 

 

Out of the I can no longer play my music files from my Synology NAS – BUT only in my office…. I can play my files in the livingroom, room 3 and 4 – but NOT in my office.

 

I have tried from my MacBookPro App and from my iPhone app – but it will not play the files. Radio and streaming services are doing fine.

 

I can perfectly see my files/folders in the app – but access for playing is denied in my office. If I combine livingroom with office I can play the files in the office – but I can not start music from files in the office.

 

On my NAS I have 5 different main folders with files and it is all the same. Will not play in office but other zones are playing fine.

 

All systems are updated and I have rebooted computer, iPhone, modem, router, server, Play:5’s.

 

Can someone help me?

 

 

 

icon

Best answer by sjw 7 May 2023, 15:20

View original
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.

56 replies

S
Userlevel 7
Badge +15

OK great, I’ll put all the instructions into one post.

Connect to the NAS via SSH (use PUTTY). (you may have to enable SSH in the NAS Control Panel)

Type sudo -i  (note the space after sudo).

Press enter. (it should give a slightly humorous prompt).

Type the root password.

Type cd /etc/samba  Press enter

Then type ls -al (they are lowercase L’s)

It should list the smb.conf file.

Type cp smb.conf smb.conf.backup  (that gives you a backup)

Now type:

vi smb.conf    Press enter

This takes you into a text editor in the smb.conf file

Check the line unix extensions=no isn’t already there.

Now press the down arrow until you reach the end of the file.

Type the letter o.  It should put the cursor below the last line - and you can now insert text.

Type the line unix extensions=no

Then press the esc key (top left of keyboard) a couple of times.

Now press the : key.  (Shift ;)

The cursor should go to the bottom of the file.

Type wq and then enter.

That writes the changes and quits out of the text editor.

The change is now made.

If anything seems to go wrong when you are in the file, press escape a couple of times, then : and then q! and enter.  This will quit the editor and make no changes.

F
Userlevel 1

OK great, I’ll put all the instructions into one post.

Connect to the NAS via SSH (use PUTTY). (you may have to enable SSH in the NAS Control Panel)

Type sudo -i  (note the space after sudo).

Press enter. (it should give a slightly humorous prompt).

Type the root password.

Type cd /etc/samba  Press enter

Then type ls -al (they are lowercase L’s)

It should list the smb.conf file.

Type cp smb.conf smb.conf.backup  (that gives you a backup)

Now type:

vi smb.conf    Press enter

This takes you into a text editor in the smb.conf file

Check the line unix extensions=no isn’t already there.

Now press the down arrow until you reach the end of the file.

Type the letter o.  It should put the cursor below the last line - and you can now insert text.

Type the line unix extensions=no

Then press the esc key (top left of keyboard) a couple of times.

Now press the : key.  (Shift ;)

The cursor should go to the bottom of the file.

Type wq and then enter.

That writes the changes and quits out of the text editor.

The change is now made.

If anything seems to go wrong when you are in the file, press escape a couple of times, then : and then q! and enter.  This will quit the editor and make no changes.


Thank you very much. After the update Synology my Sonos system failed, but with this help it's working again. You're a genius!

N
Userlevel 1

OK great, I’ll put all the instructions into one post.

Connect to the NAS via SSH (use PUTTY). (you may have to enable SSH in the NAS Control Panel)

Type sudo -i  (note the space after sudo).

Press enter. (it should give a slightly humorous prompt).

Type the root password.

Type cd /etc/samba  Press enter

Then type ls -al (they are lowercase L’s)

It should list the smb.conf file.

Type cp smb.conf smb.conf.backup  (that gives you a backup)

Now type:

vi smb.conf    Press enter

This takes you into a text editor in the smb.conf file

Check the line unix extensions=no isn’t already there.

Now press the down arrow until you reach the end of the file.

Type the letter o.  It should put the cursor below the last line - and you can now insert text.

Type the line unix extensions=no

Then press the esc key (top left of keyboard) a couple of times.

Now press the : key.  (Shift ;)

The cursor should go to the bottom of the file.

Type wq and then enter.

That writes the changes and quits out of the text editor.

The change is now made.

If anything seems to go wrong when you are in the file, press escape a couple of times, then : and then q! and enter.  This will quit the editor and make no changes.

Thanks champion!!!

S
Userlevel 7
Badge +15

Perfect.

OK, firstly, we will take a backup of the file!

Type:

cp smb.conf smb.conf.Rob  (that gives you a backup)

Now type:

vi smb.conf    Press enter

This takes you into a text editor in the smb.conf file

Check the line unix extensions=no isn’t already there.

Now press the down arrow until you reach the end of the file.

Type the letter o.  It should put the cursor below the last line - and you can now insert text.

Type the line unix extensions=no

Then press the esc key (top left of keyboard) a couple of times.

Now press the : key.  (Shift ;)

The cursor should go to the bottom of the file.

Type wq and then enter.

That writes the changes and quits out of the text editor.

The change is now made.

I don’t know if a reboot is needed for them to take effect - try it…

If anything seems to go wrong when you are in the file, press escape a couple of times, then : and then q! and enter.  This will quit the editor and make no changes.

Stanley_4
Userlevel 7
Badge +22

You might try the suggested setting on your NAS smb.conf instead of downgrading.

unix extensions = no

S
Userlevel 7
Badge +15

When you say access is denied in a room, do you mean you're literally getting an error saying ‘denied’ or that you are unable to play music in some rooms but others are OK?

If one room is able to access the NAS, then your whole system has access - the speakers/rooms don't have individual ‘permissions’.

S
Userlevel 7
Badge +15

OP can play in some rooms though so I’m not fully understanding the issue.  Unless by ‘other parts of the house’ they mean non-Sonos devices too?

However, as @Ken_Griffiths , make sure your SMB is set to V1 as the minimum allowed version.

It looks like this:

 

R
Badge

Great, I am sure this will help others as well.

M
Userlevel 1

Hello,

I have 8 rooms; Synology DS920 NAS; 3 rooms couldn’t play music from the NAS; getting the “access denied” error; I am using Windows 10 Home on a Dell XPS 13; Sonos S1 app

I had removed and added NAS music folders as well as re-booted the offending Sonos speakers in the 3 rooms - that didn’t help

I followed the Connect to the NAS via SSH (use PUTTY) from @sjw and then rebooted the NAS and everything worked. FYI, my root pswd was the same as the initial login pswd.  

Thanks, Mike

S
Userlevel 7
Badge +15

You need to enable ssh and follow the Guide posted.

Depending on how Synology do updates would decide if they change the conf file each time but the setting would be changeable again.

M
Userlevel 2
Badge +2

Linux has a hold command to stop apt-get update for a specific package. Alternatively, I flashed an image of the pi disc to my computer that I can revert to if it goes wrong again.

S
Userlevel 7
Badge +15

All I would say is disabling it again can't do any harm..? If your NAS isn't exposed to the Internet it's not an issue anyway but at the end of the day we should all reduce our exposure to risks..

S

Yay! Thank you!

It worked, but if you have trouble, please check your spelling. 

It didn’t work the first time and when I went back to check the file, I had written “unit extensions=no”

That will not work. 

S
Userlevel 7
Badge +15

Hi, it looks like others are having similar issues where certain devices can connect and others not.  Seems to be related to an SMB update on the NAS.

See here -

Depending on your knowledge of accessing the NAS via ssh/Putty, there is also a fix a little lower.  

 

Ken_Griffiths

Thanks for the quick reply. I checked the second link but I am not sure what the technical changes  are that you refer to. I see several options mentioned (downgrade SMB, which I do not want to do - add unix extension etc.)

Can you be please be more specific on what I can/should do?

Again thanks.

In the last post @Outburst mentions this…

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

…so perhaps try that option or you might have to uninstall/downgrade the extensions as suggested before that - If you don’t make any changes, then I guess you’re stuck for the time being.

S
Userlevel 7
Badge +15

The changes are simple but require you to connect to your NAS in a way that most users are not familiar with (ssh). Until it's fixed their end (hopefully it will be), if you don't want to make those changes you won't be able to resolve the issue yourself.

They are very simple changes though and you just need to type and follow those instructions above (you need an Admin/root account for the NAS).

R
Badge

Perfect, that did the job. Thank you so mu.

Great help. Much appreciated.

Enjoy your day.

B

Thanks heaps for this answer. 

 

sjw wrote:

N

when i got my new synology nas (never had issue with old one apart from it died), it took me ages to sort out the smb for s1 vs s2 was fine straight off.

now is denied again even though settings are as detailed. why cant sonos fix this as clearly a big problem...and sorry i dont understand the access via SSH >use PUTTY

D

I have a problem with the SJW mod to smb.conf file. If you reboot the NAS (DS218+) the file reverts to the previous version. So I still have a problem whereby the Play 1 works correctly but access is denied for my Connect. They both work if grouped together (sometimes).

K
Userlevel 2
Badge +5

I’m not that technical to be able to do that I guess..

A
Userlevel 2
Badge +2

Add me to the list of grateful users… I have a mix of newer and older Sonos products, and this has been driving me nuts! Thanks

Majikthise

Thanks sjw, initially I had rolled back the SMB package to an earlier version to fix the “access denied” problem but your SMB.conf tweak using the latest SMB is obviously a more elegant solution.

F

Another satisfied user.  Thank-you jsw!

J
Badge

Thank you VERY much @sjw you are a super star.

I had the same issue, that Sonos iPad app suddenly started to report “access denied” when attempting to play music from my music library on my Synology NAS. Added “unix extensions=no” to the “smb.conf” of my Synology NAS DS218 solved it for me, and my old Sonos S1 system now works again.

Curious @sjw, how did you figure out this was the solution??

Terms & ConditionsCookie settings