Does Sonos S2 support SMB V2 V3?

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,

I’m using Sonos v14 on a PC, android, and a bunch of older and newer sonos play 1/one devices.

Years ago, since I don’t trust enabling SMBv1 from my Synology NAS, I set up a power efficient laptop to copy my music library to, and left that running 24/7 just to serve sonos music media files.

After updating to v14, I thought I’d try removing my local library from sonos, and renaming the folder just in case it could still ‘see it’, and have added my synology served media without enabling smb v1.

IT’S WORKING!!! So minimum SMB protocol set to v2, maximum SMB protcol SMB3. Transport encryption mode is client defined, and enable server signing is force. Enable opportunistic locking is ticked, and enable smb2 lease is ticked. Enable SMB durable handles is not ticked.

I do also have NFSv2 to v4.1 enabled, but when I disabled NFS as an experiment, then Sonos can still play the music. When I disable SMB, it can’t.

So,  SONOS SUPPORTS SMB v2!!! Hooray!!! (And possibly v3, but I can’t enable only v3 on my Synology)

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.

I’m using SMB2 on my SYNOLOGY.

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.

Refer: 

Curious as to why you’re pointing to this same thread?

It’s not a link to this thread per se, but to a post above where it’s detailed that SMB1 is now in fact no longer required for Sonos.

My Sonos (S1) system was unable to find my SMB share until I turned on SMB1 and NTLMv1. Then it worked find. Does this statement “this was resolved long ago” apply to S1 systems? Because with the stock Synology setup I could easily connect to the music library from windows, using the same account that Sonos uses. But the Sonos could not see a share until I turned on SMB1, and then it could see the share, but could not access it until I turned on NTLMv1.

This is of course with a fully updated Sonos system, and fully updated Synology.

Only S2 supports SMB versions greater than SMB1.  The S1 kernel was created well before any other versions existed, and cannot be updated due to size issues.