Trending Lyricist I

Answered

SONOS S1, Synology DSM7 and music library

Forum|Forum|1 year ago
November 11, 2024
27 replies
1394 views

Has anyone had luck adding their music library from a Synology NAS with DSM 7+ to a S1 configuration?

After Hours with L2 support they finally told me, oh it wont work with DSM 7, you may want to downgrade back to DSM6.

I just want to see if anyone out there has been able to add the music library under these conditions.

Thank you, Mike

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.

Best answer by Jamie A

Hi @MVillella,

Sorry to hear you’re having issues connecting your Synology NAS to your Sonos System.

What you heard from our L2 support is correct, a Synology NAS with the DSM7 update isn’t compatible with an S1 system. Our internal information recommends reaching out to Synology support as this cannot be resolved by our support team.

We don’t have any steps suggesting how to downgrade to DSM6, but contacting their support and requesting this would be your best solution.

Show previous replies

M

MVillellaAuthor

Trending Lyricist I

I’m not sure who marked it best answer. Probably SONOS. Based on the replies it suggests that answer is not true as people have apparently found ways to make it work which I suspect is true and that SONOS isn’t really interested in going the extra mile to figure this out. If it was true I doubt my level 2 tech would have spent over an hour trying to get it to work for me before telling me it wouldn’t work with dsm7 which he knew upfront I was running.

I’ll be trying all of these suggestions while off next week and if any work will report back.

J

jreddaway

Renowned Enthusiast I

I’m not sure who marked it best answer. Probably SONOS. Based on the replies it suggests that answer is not true as people have apparently found ways to make it work which I suspect is true and that SONOS isn’t really interested in going the extra mile to figure this out. If it was true I doubt my level 2 tech would have spent over an hour trying to get it to work for me before telling me it wouldn’t work with dsm7 which he knew upfront I was running.

I’ll be trying all of these suggestions while off next week and if any work will report back.

HI, @MVillella and @ClausN , this is a topic which seems to just keep running, but I agree with your comment re best answer.

This will be my last comment on this thread, but I thought I would check my two systems running off the library on my Synology DS118, which has the latest software (DSM V7.2.2-72806 Update 1) installed. The two systems both run off the same Android handheld controllers and off my Windows 10 PC.

The S1 system has App V11.15 Build 572259130 on the controllers and the same version number as the firmware on the speakers.

The S2 system has App V80.12.04 release 20241114.cfc873c and firmware V81.1-58210 on the speakers.

Both systems work perfectly simultaneously. I did not have to do any tricky workarounds to get them set up.

Based on this, I cannot understand how the Sonos L2 techs came to the conclusion that S1 could not run on a NAS using DSM7. It does for me.

S

Stam

Contributor I

Hi,

I have a Synology NAS (DSM 7.2.2-72806 Update 2) and sonos S1 can connect without any problems.

First of all you have to enable SMB v1 on Synology, after that you have to enable NTLMv1 (on advanced settings). Let me know if you need help on enabling those settings.

(If you have a S2 system you don’t need underneath additional steps, but with the new courageous updated app the NAS library doesn’t works as expected, sorry for the OT comment)

Connect through SSH to your Synology NAS

type:

cd /etc/samba/

perform a configuration backup, type:

sudo cp smb.conf smb.conf.backup

modify smb.conf file, type:

sudo vi smb.conf

(basic vi commands https://www.thegeekdiary.com/basic-vi-commands-cheat-sheet/ )

go to last row and type:

o

in order to add a line

insert the following text:

unix extensions=no

the file should looks like:

[global]

printcap name=cups

winbind enum groups=yes

include=/var/tmp/nginx/smb.netbios.aliases.conf

min protocol=NT1

access based share enum=yes

security=user

local master=no

realm=*

passdb backend=smbpasswd

printing=cups

max protocol=SMB3

winbind enum users=yes

load printers=yes

workgroup=WORKGROUP

unix extensions=no

Press ESC and type:

wq

Restart SMB service:

Control panel -> File service
Disable SMB service
Press apply
Enable SMB service
Press apply

P

pwaara

Contributor I

Hi,

I have a Synology NAS (DSM 7.2.2-72806 Update 2) and sonos S1 can connect without any problems.

First of all you have to enable SMB v1 on Synology, after that you have to enable NTLMv1 (on advanced settings). Let me know if you need help on enabling those settings.

(If you have a S2 system you don’t need underneath additional steps, but with the new courageous updated app the NAS library doesn’t works as expected, sorry for the OT comment)

Connect through SSH to your Synology NAS

type:

cd /etc/samba/

perform a configuration backup, type:

sudo cp smb.conf smb.conf.backup

modify smb.conf file, type:

sudo vi smb.conf

(basic vi commands https://www.thegeekdiary.com/basic-vi-commands-cheat-sheet/ )

go to last row and type:

o

in order to add a line

insert the following text:

unix extensions=no

the file should looks like:

[global]

printcap name=cups

winbind enum groups=yes

include=/var/tmp/nginx/smb.netbios.aliases.conf

min protocol=NT1

access based share enum=yes

security=user

local master=no

realm=*

passdb backend=smbpasswd

printing=cups

max protocol=SMB3

winbind enum users=yes

load printers=yes

workgroup=WORKGROUP

unix extensions=no

Press ESC and type:

wq

Restart SMB service:

Control panel -> File service
Disable SMB service
Press apply
Enable SMB service
Press apply

I have done all of these steps on my Synology, but I am still getting “file not found” error. I can browse and see my files, but I cannot play them. Is there something else that needs to be set or cleared? I really want my music library back.

P

pwaara

Contributor I

I just realized that it works on all my devices except my Sonos Connect, which is where I play these files most often. I’ll try to reboot that device and see if that helps.

P

pwaara

Contributor I

Well, rebooting the Sonos Connect seems to have fixed it. I now can access my Music Library (over 41,000 songs, so it was very important for me to get those back.)

A

atebit

Avid Contributor I

Hi,

I have a Synology NAS (DSM 7.2.2-72806 Update 2) and sonos S1 can connect without any problems.

First of all you have to enable SMB v1 on Synology, after that you have to enable NTLMv1 (on advanced settings). Let me know if you need help on enabling those settings.

(If you have a S2 system you don’t need underneath additional steps, but with the new courageous updated app the NAS library doesn’t works as expected, sorry for the OT comment)

Connect through SSH to your Synology NAS

type:

cd /etc/samba/

perform a configuration backup, type:

sudo cp smb.conf smb.conf.backup

modify smb.conf file, type:

sudo vi smb.conf

(basic vi commands https://www.thegeekdiary.com/basic-vi-commands-cheat-sheet/ )

go to last row and type:

o

in order to add a line

insert the following text:

unix extensions=no

the file should looks like:

[global]

printcap name=cups

winbind enum groups=yes

include=/var/tmp/nginx/smb.netbios.aliases.conf

min protocol=NT1

access based share enum=yes

security=user

local master=no

realm=*

passdb backend=smbpasswd

printing=cups

max protocol=SMB3

winbind enum users=yes

load printers=yes

workgroup=WORKGROUP

unix extensions=no

Press ESC and type:

wq

Restart SMB service:

Control panel -> File service
Disable SMB service
Press apply
Enable SMB service
Press apply

After enabling smbv1 & NTLMv1, I was still unable to connect my S1 to my music library under Synology DSM7. After I modified smb.conf using Stam’s instructions, it now works. 👌

One question: After already wedging the door open by enabling smbv1 and NTLMv1, so we know what the effects of “unix extensions=no” are when using the shares with Unix, Linux or MacOS?

Sign up

Login to the community