Does Sonos S2 support SMB V2 V3?

I suspect the “move to streaming” (as a priority for Sonos) will kill the company.

If I wanted to use e.g. spotify I’d just use a Google Home Hub ..I have plenty . I can also buy them much cheaper. The Unique Selling Point  of the SONOS is the ability to actually play my own music collection. It feels like they are trying to play catch-up with what they see as “the new trend” and end up turning themselves into another me-too stream player ...where they will lose. I suspect they would do better making “apps” for the popular NAS and for desktop computers, phones etc . I suspect an “unlock your collection” works a lot better than “almost like an Alexa box”

I am keeping a eye on the SMB1 discussion as it impacts more than my SONOS system. I have Netgear NEOTV550 and Zappiti media players that also require SMB1. I just purchased the Zappiti as a replacement for the Netgear NeoTV 550’s  and did NOT notice the SMB1 only requirement until it was to late to return to Amazon.

I am using a SYNOLOGY DS1815+ NAS for all my music and videos. I expect that when SYNOLOGY launches the DSM 7.0 update they will drop support for SMB1 due to security and support issues.

I have stopped all purchase of SONOS and Zappiti hardware until I get a clear direction on where they are headed.

I have been a SONOS user since the product came out and the ability share my own music was a primary reason for purchasing the system. I am NOT interested in converting my system to just a “streaming service” player.

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

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…

Given you have a Linux based sever you can probably do better than SMB . Sadly no NFS v3 support. Looking at my media library it looks like an http: type address. In anycase there are DLNA servers  (if I understood more about UPnP I’d suggest that) The setup of the Sonos Media library is very clunky .

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.

I recently switched from using Rygel to minidlna ( https://help.ubuntu.com/community/MiniDLNA  [can’t vouch for the guide, I use Debian]) it seems a bit quicker. Mind you I use it for video rather than audio …. the Sonos I drive from a NAS (Qnap) so it has all sorts of protocols under the covers … without digging around and tracing it’d be hard to spot which one I’m actually using . (I know, when I first got the SONOS it was SMB , which pained me a little)

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.

While a good firewall is certainly useful (I have multiple, stacked ones) sadly with modern “appliances” it affords little/no protection.  My Home Hubs. nest, Sonos devices all “call out” to their manufacturers , thus creating a NAT (iptables established) relationship though the firewall.  If you think about it, the fact that Sonos, Google et al are able to apply updates to their boxes through your firewall, without you granting them an incoming port rather makes the point.

My Sonos took to un-pausing and playing loud rock music (AKA Music)  at random points on it’s own (yes I sent diagnostics to Sonos) which I’m assuming was due to some operations somebody (my hope is Sonos) were doing on the device. Short or running wireshark 24X7 and catching it happening, I could not see a way to spot the cause (from outside the Sonos)

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.

Well SONOS have been giving priorities to bugfixes, features etc... which is fine.

But it's all fun and jokes for them until some catastrophe happens about SMBv1 on their systems.

To be honest I have no clue about security and hacks. But a lot of times when problems luke these arise, the company will be throwing all kinda excuses and showing all kinds of reasons why they can't do something. Then something goes horribly wrong and it hits the news. Then within a month there will be a fix for the problem.

And "no". I am not hoping for them to remove all SMB options cuz i also have a private collection on my NAS.

I am just sad that even though many users are having this problem, companies will just show all the bottlenecks about "why it can't be done".

Yet Sonos have proven to be able to achieve a lot of things that other companies are unable to achieve.