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.

Is this any help?  It needs a little technical know how.

If it does work, you’re effectively lowering the security of the NAS to the level that Sonos S1 systems need.

https://kb.synology.com/en-ca/DSM/tutorial/I_cannot_access_shared_folders_from_WinXP_computer

 Use at your own risk.

Thanks MoPac, I did enable SMB1 and NTLMv1 with no luck. 

Thanks SJW, A bit over my head, but I’ll read up on using putty and see how far I get. Appreciate this. I don’t love the idea of compromising the Synology system, but the only real alternative is to find a new streaming system to replace the SONOS.

You could add an SMB gateway to re-share your NAS over an SMB v1 share, that requires no changes to your NAS and you can limit the gateway's connectivity to minimize the SMB v1 risks.

https://stan-miller.livejournal.com/357.html

Which speakers are you running? Why are you restricted to running S1?

Bruce, I was an early early adopter . I still have 4 zones of ZP80, 100 and old play 5. All still work perfectly other than this issue so if I was to replace them all, it would probably be with a less expensive platform before I dropped a couple thousand on new Sonos for the only purpose of getting a NAS library that worked a week ago to work agian. Considering how popular SONOS AND Synology are, I’m surprised this isnt more common.  Maybe I’m the only one running older SONOS.

Stanley, thanks for this info. A rather inexpensive alternative, though I’ve never played around with a Pi before, I’ll look into it. It’s starting to feel like these older units are being left so behind by SONOS that it may be time to look for a new streaming option.

I don’t think you are, but wanted to be certain why you were running S1 before making a subsequent suggestion just to move to S2…and there are many still out there that don’t understand that they can, although you clearly can’t. 

It is unfortunate that electronics ‘age’. The RAM/CPU in the older Sonos products just isn’t large or fast enough to handle the requirements for an updated Linux kernel that can handle other versions of SMB, and Synology has chosen (somewhat prudently, IMHO, but frustratingly for people like you) to remove access to SMB v1 in their latest software stack. A conundrum, to be certain. Not helped, I’m sure, by lawyers concerned about lawsuits. 

I suspect ​@Stanley_4 ‘s solution might be the best for you, although I’ll admit it seems daunting, at first glance, but inexpensive. And I have faith that his reference materials are good enough for semi-competent people like me to muddle through, it shouldn’t be overly complicated for someone like you. 
 

Edit: I don’t hate all lawyers, I’ve worked with many fine ones in my software development history…but there are varying types, as in all other walks of life ;)

Bruce, it’s definitely a cost effective approach and I'm going to read up on it. Regarding the older SMB, I have been able to set the Synology to work with SMB1 and it seemed like this worked for may people based on the posts I read, but no luck for me unfortunately. So I dont think Synology removed it, they just did default to using that version. I was hoping that would be all I needed to do.

Thanks iufore, I think I agree, it may be best to just start looking at other hardware solutions at this point as I feel like I’m either throwing good money into devices SONOS doesnt really support anymore, or going through a lot of time and effort to get a workaround which kind of defeats the purpose of using SONOS to begin with. I had some hope of it being a simple software setting based on a lot of posts I was reading, so I’m to sure why it didnt work on my end. I keep feeling like I’m just missing that one setting somewhere. But some excellent options advice above I’m going to look into.

I used a Pi as my gateway but any SMB v1 device will work. 

Sadly there just isn't the memory space for v2 on older Sonos. 

And it’s not only Sonos who doesn’t ‘support’ SMB v1 anymore. Most companies don’t, due to liability potentials, I suspect. Certainly Microsoft and Apple, as well as apparently Synology. 

SMB v2 was released in 1988, because SMB v1 was so vulnerable to hacks. It’s been out there quite a while. To be honest, having Sonos stick with it for S1 was amazing to me, until I figured out there just wasn’t enough memory available to the to update the kernel that runs their early speakers. 

Synology though does support SMB1, that’s what makes it frustrating that I cant get the two to work together as is. 

Hi, ​@MVillella , my experience with a my little Synology DS118, which has the latest software (DSM V7.2.2-72806 Update 1) installed is that, while the system gives you all sorts of dire security warnings when you do so, I have had no problems enabling SMB1 as the Minimum SMB Protocol with SMB3 as the Maximum and running with it.

I need to do this as I have an ageing (all of 8 years old!) TV which only does SMB1 for streaming recorded material from the NAS and I’m prepared to take the perceived security risks as access to my system is pretty well protected.  As I had to have it running for the TV I thought I might as well dig out a couple of old S1-only speakers and use them as well. They work fine alongside my S2 gear, all running off the same library.

I have never had a Synology-induced problem with deleting/installing or indexing the library, both of which I have done a number of times recently, although I do recall having to do a bit of fiddling with permissions, user profiles etc when I set it up some years ago; any issues that do come up seem to arise from third parties……

I can understand your frustration at not being able to get set up.  Based on my experience, my only thought is that your unit is probably newer/more sophisticated than mine and is perhaps running a newer software version.  If that’s the case I wish you luck and hope that whatever upgrade Synology may have pressed on to you does not roll down to me.  I’ll be looking out for it.

I have the same set up and was having terrible problems getting it working via my ‘old’ set up - i.e. wireless access but all the main deviced wired via EoP devices. This had worked fine for years, but kept getting the library set up rejected. The issue and solution can be found at :-

thanks Amun for the link, I’ll give it a read through, looks like having the computer running S1 and the Synology hardwired to the same router could be a solution.

Thanks jred, so it is possible regardless of what SONOS support tells me. I had heard there were people getting it to work with n nothing more than some settings, permissions, etc set correctly. I actually have the same exact DSM version.

Yes, but you can put it all back to normal once the library has been added and indexed. Further indexing tasks work fine.

The reply from ​@Jamie A has been marked “best answer” - but according to ​@amun it is possible to run S1 with DSM7.

What is correct?

I’m running an older NAS with DSM6 but plan to upgrade to a newer NAS, but prefer to stay on S1.
 

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. 

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:

Press ESC and type:

wq

Restart SMB service:

1. Control panel -> File service
2. Disable SMB service
3. Press apply
4. Enable SMB service
5. Press apply