Does Sonos S2 support SMB V2 V3?

I thought S2 was going to be more of a ‘from the ground up' update but its been confirmed in other thread that still only V1 is supported so maybe they've just reused the old kernel instead if the new one, despite having more room available for it now.

I expect it is on the ‘to do’ list but was expecting there to be more in the big S2 release than there is.

Thanks for the clarification!

When does s2 support SMB v3 ?

Nobody knows, except maybe some Sonos software engineers.

Just tested to connect my Sonos S2 installation directly to my NAS (no SMBv1 support, located on another IP subnet) and failed misserable

I guess I have to continue to run a Linux VM that acts like a SMB bridge, with one leg connecting to my NAS using SMBv3 and in parallell providing my Sonos system with a SMBv1 share to be able to enjoy my music

Not supporting anything higher than SMBv1 these days is just sad!

..especially when Sonos claim that they have changed to an ’all new’ operating system

Where do they claim it is “all new”? The UX has had a refresh, for sure, but the code that runs on the players hasn’t changed much that I can tell. The switch to S2 means they have a lot more ram/flash for future expansion, but nothing so far has shown signs that much of the new capacity is in use yet.

Moving away from outdated unsecure protocols like SMBv1 is vital in the modern age to keep your customers safe. That is called maintenance, and I would see that as the bare minimum for both S1 and S2

SMBv2 was released in 2006 so no one can say they didn’t have time to patch their software..

Security aware NAS manufacturers removed support for SMBv1 a long time ago, making them unreachable for the part of Sonos customer base that own their music vs just renting it from Spotify or others

Ps, the ’all new’ is kind of to be expected after all the fuss Sonos made in the ads about their new cool OS combined with the drastic cut of supported products.

From a user perspective, as you say, nothing has really changed going to S2

Only a problem for NAS users though. Folks using Macs or PCs to share their files don’t have the SMB problem thanks to the new https library server.

Hi controlav,

Interesting how you again and again try to divert from the initial question 😉: Why Sonos doesn’t keep their base software updated and secure .. (the SMBv1 limitation is an example that apparently affect customers and sets the expectation about the quality of the underlaying system)

>> NAS vs Workaround

The logic is to have your music/files/photos on a dedicated secure (often with raid) and always on NAS reachable from all your devices in your home network (and on the road using the latest editions)

It’s a waste in so many ways to have a Mac/Windows host powered on just to mitigate a limitation in the Sonos implementation of a standardized protocol

Suggesting a proprietary solution is even worse as we are moving towards open source software + standards, that even giants like Microsoft have seen and implement

*To add SMBv2/3 should be easy to do unless the developers made a serious error in the initial implementation causing a dependency (wish I hoped had been solved in the ’new’ S2)

Thanks for the insight into the state of Sonos development.

The answer to the original question is simple: No. Not at this time. No diversion necessary.

The reason for SMBv1 on the Sonos S1 system has been well documented for years: the players’ Linux kernel is too old to support the newer versions of Samba.

With the move to S2 there is the possibility of updating the Linux kernels on the newer devices, and when/if they do that then newer versions of Samba become available. This whole area has been de-prioritized since the popularity of streaming took off, so who knows whether it will happen.

It would take a developer a few hours to get the Sonos https library service running on any NAS that supports .Net Core. I have offered to help on other threads, but no-one seems interested in doing so.