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. 

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