Synology NAS music library folder - only works with admin account

Check that the base share point is the same for user and admin accounts.

Not synology but this is from my samba config:

[music]

Comment = Pi shared folder

Path = /mnt/music

Browseable = yes

Writeable = Yes

only guest = no

create mask = 0555

directory mask = 0555

Public = yes

Guest ok = yes 

You can create a user account that has admin privileges.

 I have disabled the Synology admin account and the guest account. There is just my admin account that has access to my folders.

Are you 100% sure that the account you're using in Sonos to access the share(s) actually have read access to them?  If you can access an area with one account but not another, it's usually a simple permissions thing.

I would not give the account Admin privileges, but would certainly create one, just for Sonos, to access the Music share.  Read only access to the minimum area(s) necessary.  Creating an account won't necessarily have access.  Go into the share's properties and make sure it has access.

I have found this with Synology also. The account used for Sonos share seems to need admin access to the shared folders now.

This manifested a while ago when my named access paths stopped being accepted by Sonos in favour of IP.

This was true on an older DS414 and now a current DS124. I use a dedicated Sonos admin user locked down to shared folders only... and keep my library backed up 🫣

I concluded it was a Sonos thing rather than Synology since it coincided with a firm/software release, from memory, towards the end of last year. It would be a strange coincidence if not.

Yep agree, and that's what I've tried to avoid the account having full admin privaleges. But any combination of access permissions (R or RW) on a non admin account doesn't work.  The question is what does an admin account do over and above a user account to disable/ignore/override in order to be accepted by Sonos?

Good to know it's not just me then 👍🏻.

One thing I did try after posting was setting my ‘sonos’ synology account to admin, then add the folder, then switch it back to a standard user account. The library still appeared and music would play. As I don't intend to add further files once setup this might be my work around.  When I get back home I'll see if the 2am ‘check for new files’ has knocked the library off, which makes it feel like an indexing issue that only admin accounts can handle 🤷🏻‍♂️. If it has disappeared I'll just set to not daily update.

Cheers.

Hate to be the odd one out, but the “Sonos” user on my Synology DS225+ has read-only access to the  Music share (//nas3/Music) and it works just fine.

When I set this up, it was new. I let it use Synology’s weird file system permissions and didn’t tell it to use linux/unix permissions. Maybe that’s the difference?

The music share was originally populated using the usb copy feature from a usb drive that contained my full music library. After that, all new files are copied from my linux box (fedora) that has the share mounted using a user with read/write access being a member of the “Music” group. The “Sonos” user is not a member of the “Music” group and only has read-only access to the share.

Edit (again): Another thing that may be different. I also use this share with S1, so SMBv1 is enabled. In File Services, SMB, Advanced, I have Max SMB = SMB3, min SMB = SMB1. NTLMv1 auth enabled under Others.

Let us know the result 👍

Ah, I’m avoiding running with SMB1 and NTLMv1, although I did try it and it still didn’t seem to work anyway.

The Music Library is still there and working 👍🏻.

I’ll add a new file for it to find overnight and see what happens.

I’m a bit curious, since this sounds like a Synology implementation issue, if someone has contacted Synology’s CS to report / ask about it? I wouldn’t think Sonos ‘knows’ what’s at the other end of their data request. 

I'm curious too, why you think it's a Synology implementation issue?

I'd say if there was an issue with Synology where you needed Admin access to a Share in Read only mode, they'd have definitely been aware and resolved it.

Far more likely is there's a Sonos issue that doesn't view the contents without Admin access?

I have perfect access with a Sonos account with read only access to the share.

Users could map a drive to the Share on a PC for example using the Sonos details.  I would bet the contents are viewed perfectly.

We've heard strange things previously with access not working consistently from Sonos and needing to use IP address etc. for access. 

Because it’s only being reported with Synology, and not other SMB accessed drives? My imagination suggests Sonos is making a standard SMB coded request for data to access. The fact that it is being rejected, and only with Synology drives, suggests an issue on the other side, to me. I can’t imagine there’s a bit in the Sonos code that says ‘if the drive is Synology, then do this’. I’d think the Sonos code is merely making a standard request, and has no physical knowledge about what it is connecting to. 
 

Dunno. I haven’t seen any ‘official’ data from Sonos, I was wondering if there was any response from Synology. If it is truly an issue on Sonos’ side, that will be interesting to me, but right now, given the data in this thread, I’m not sure it is. 

My simple SMB / Samba,  Linux based, NAS is showing no issues with Sonos access.

By the same logic, Synology surely just receives some credentials and the Share name and either allows or otherwise?  i.e. although you “can’t imagine there’s a bit in the Sonos code that says ‘if the drive is Synology, then do this”, you totally can “imagine there’s a bit in the Synology code that says ‘if the requester is Sonos, then do (or don’t...) do this”?  But those same credentials are fine accessing the NAS/share from all other devices?
My guess is it’s possibly related to a couple of things - and may depend on how the files got there in the first place.

Sonos could be requesting an elevated access to the files or the root volumes.  Maybe it tries to lock files to read the ID3 tags?  Maybe it’s trying to traverse folders?

I think Sonos has changed something (maybe in the SMB 3 implementation?) where it no longer copes consistently well with NetBIOS names - maybe try using the IP address instead.

Ensure the Sonos user has been Allowed access to SMB Files Service.

Ensure the Sonos user has access to the actual files.  Select the Share - Properties - Permissions and select the Sonos user, click Edit, and set permissions to Read.  Make sure to "Apply to this folder, sub-folders and files".  That should fix issues with linux/ACL mismatches (especially if the files were copied there by Admin).

Can the user connect to the Share and view its conents as the same account from a PC?  If so, it suggests Sonos needs a little more than ‘basic’ read access.  I’d try this first.

Yeah, my Synology NAS is showing no issues with Sonos access either - but it’s running an older firmware.

As I said, I don’t know. What I’m looking for is both sides of the equation, so I can make a more reasoned understanding of the situation. Obviously, I’m not able to fix it. And it could be possible what you’re suggesting is true, I still don’t know. 
 

You state your Synology NAS isn’t having issues with your Sonos system, which is great…but which is running older firmware, the Sonos or the Synology?

I’m running the current Synology firmware, DSM 7.3.2-86009 Update 4. My Sonos user has read-only access to the Music share. It works. I can’t tell you why it doesn’t work for others. But it must have to do with access permission and/or file permissions. But Sonos does not need more than read-only access to an SMB share. That is provided the permissions on the share are correct for that user’s read-only access. As sjw mentioned, this can be easily tested by mounting the share with read-only user credentials and see what you can access.

Edit: If I had to guess:

The Sonos.