Does Sonos S2 support SMB V2 V3?

This was resolved a long time ago. I’m also using SMB2. In synology settings, go to file services, SMB. Enable SMB service. I have checked WS-Discovery, if that matters. In advanced settings, General, Maximum SMB3, Minimum SMB2, Transport encryption mode as client defined, enable server signing as fore, enable opportunisitic locking is checked, enable smb2 lease is checked. Then clear your SMB cache, reboot synology and sonos, and try again.  You should not under any circumstances have SMB1 enabled! MASSIVE security issues with SMB1.

Just went through this pain. Brought up a new Synology box. Super hard to get Sonos to recognize it. Not only do you need SMB1, you also need NTLMv1. Works fine now.

Moral of the story:
1) Sonos makes you turn on two ancient protocols that servers and security pros hate.

2 Synology can be configured to work.

now - what about that horrible STP protocol we need to use on our switches? Blech.

It appears that Sonos does now work with SMB2.

See post by  Sotiris C of the 14th December on this  thread:

Since over a year ago when SMB1 was dropped by ubuntu (for sound security reasons) I’ve been struggling  to get my library of CD quality (16bit 44.1KHz FLAC) files to play on my Sonos.   I tried Plex - this handles  the art workwell but  for some reason the FLAC playback is unreliable,   (I Tried reinstalling plex re-registration, nothing solid I could  find that would fix the  issue,  Some tracks would never play some  tracks fine even from the same rip\encoding job.  All the while MP3 to Plex to Sonos works fine.)

This morning I reconfigured my library with new share and bingo I’ve got access to my library on sonos again.  Very Happy,
 

Kit list Ubuntu 20.04 LTS for the library share.

Sonos Play3,  Beam.  Controller on iOS and windows.

All upto date as of today. Sonos App 13.4.1, Sonos OS S2,

There may be some glitches with the SMB v3 addition, several topics here on them.

I’m happy to have SMB v1 gone at long last and will happily live with the glitches until Sonos fixes them.

I hesitate to say this, but my Amp and Ones appear to be talking to my Synology NAS using SMB3 now.  All devices and controllers are running S2 v13.4.

I’ve been running Sonos for 10+ years, and yes it’s surprising that they only support smb1. 
 

I read on another thread that if you have Plex running, you don’t need to use SMB at all.  I just shut off smb1 on my Synology and boom.  Now I just browse via Plex in Sonos and forget about “music library” direct access. 
 

problem solved - Plex ftw

Or, there are technical reasons as to why this is hard, and they’re working on figuring out how to make it happen. Just because they’re not really saying anything shouldn’t always mean you need to assume the worst. 

Sonos does not support latest versions, however with Synology you can do thisAs a last resort, you can go to DSM > Control Panel > File Services > SMB > Advanced Settings > Others to tick Enable NTLMv1 Authentication. This will lower the security level but allow legacy devices/applications to authenticate via NTLMv1.

I wasn’t talking about Sonos or other devices calling out but a local SMBv1 server that has no reason to call out and can easily be prevented from doing so should it for some reason attempt it. The Pi, the Linux OS and the SMB server are easily restricted to the local LAN.

Dealing with IOT stuff that calls out is an interesting problem but with a bit of networking research you can block a good bit of it, or redirect it to a local service if that makes sense. It is easy to block a lot of the Sonos Internet chatter and you see no loss of functionality for most of it and little loss for a bit more. The core stuff of course can’t be blocked if the system is to remain functional.

The Sonos being activated by something is usually best dealt with by sending Sonos a diagnostic and asking them to look at it. They can usually find the issue quickly. If you want to look at it locally it should be as simple as adding a rule to your firewall and logging packets that trigger it.

For S2 systems with their larger memories there are a lot more possibilities than there are for S1 gear.

Worst case I’m keeping a master copy of Raspberrian (Raspberry Pi OS) well backed up so I’ll be able to reinstall it on my Pi music servers at need. Don’t need the latest OS for a system well locked down behind a good firewall.

Interesting you should say that - MythTV can apparently be set up as a DLNA server but… I couldn’t figure out how to do it!

Samba was a real pain to get working, and I have an uncomfortable feeling that it’s a major hole in my network’s security.

Perhaps I should look at Rygel, which is a DLNA server that is available from the Ubuntu/Mint repositories. I wonder if it could be any less awkward to configure than Samba?

And yes - the complete lack of NFS support by Sonos is annoying, because that is almost trivial to set up under Linux.

Wow - I wish I had known that when I bought my Sonos setup last month. All I can hope is that if this happens, it happens within the Sonos “return and refund” period, because if it does - it’s all going back! All £1600’s worth.

My media server is Linux based (it has to be because it is also the server for my MythTV network) and if Samba ceases to support SMBv1, my audio library is going to stop functioning with Sonos…

All I can hope is that the balance between “it will cost us too much to upgrade our kernel to support SMBv2” and “we will lose too many sales if we don’t upgrade to support SMBV2 or later” will swing in our favour before then.

It seems that Sonos have had since around 2006 to prepare for an upgrade of some sort, so it’s not as if this is a surprise development that they could not have planned for...