SMB2 (or SMB3) support must be supported NOW!

Curious for your perspective on b). If the group is correct about there not being enough RAM on the devices to hold the larger kernel to support a higher version of SMB, how does that get resolved? Do all customers who have these devices get to send them in, and pay for new electronics (motherboard, CPU and RAM, plus manpower to install it) to get them updated? Or does Sonos just say ‘too bad’ and brick millions of currently running devices? Is there a third alternative I’m missing?

For those who are struggling with SMB and don’t want to compromise security on their NAS…

There is already the idea to use a Samba Docker (the one I’m also using), but… for those wo want another option/solution… It look and works impressive, I’m playing with it at the moment.

You can install a docker with Navidrome (https://www.navidrome.org/docs/installation/docker/) or install it differently. To integrate Navidrome with docker you can install bonob SMAPI. When you do that you can add a service in the Sonos App and access all your music without SMB :) A nice extras is that each family member can have it’s own login and favorites section within the service.

More info about bonob can be found here: https://github.com/simojenki/bonob

The both together look like Subsonic, although I’m not 100% if I’m correct since I never installed Subsonic (only read about it).

Maybe this is interesting for some Sonos owners since there is no Samba/SMB security issue in any way.

I faced the same problem. Strange that after 3 years!!!! There stil is no update.

I didn't know this problem until I updated to Synology DMS 7 and I couldn't connect to my music library anymore. I activated NTLMv1 on my NAS, buit I'm not happy it needs to be done

When will this updated to the newest save standards (NTLMv2)??

Look on the other thread. Sonos have acknowledged they are working on smb 3 support. No timescales but it’s good to know pots coming. 

Thanks for the answer.

This discussion is in regards to the Sonos Controller software, correct?

I want to make sure that I’m not confused here. My experience with Sonos and SMB is trying to set up a folder from within the Sonos Controller that runs on a PC. And, that doesn’t seem to work unless it’s SMBv1.

It seems to me that the controller software has the ability to add local folders with music to the controller in a music library.

Presumably, that’s so the controller software can serve the bytes from the local music files to the Sonos speakers via some proxy scheme. 

If that’s the facts here. Why is firmware for the speakers part of this discussion at all?

If the controller software is what’s responsible for delivering bytes to the speakers, who cares what network protocol the speakers support?

If the controller software isn’t what’s actually serving bytes for local music files, why does it exist in the first place?

And if the controller software serves bytes from a local drive, why can’t it broker bytes from a network share on SMBv2/3? Why does the speaker care at all?

@lastmuel you are entirely mistaken. The controller is required to set up the link between the library and your speakers, yes. Once set up it is the speakers that read the files over the network, and have the SMBv1 limitation.

The controller is a remote control. It does not participate in playing music at all. (Unless using AirPlay or Android-on-this-device). It is not required once the music has been started.

Controlav, how do the speakers get access to local music files in a directory on a PC that has the Sonos controller installed? Is the controller software opening a file share on the PC using smb v1?

No. On a PC Sonos install an http server (SonosLibraryService.exe) that reads the local file system. The speakers do http GET calls to that. PC local libraries hasn’t used SMB in a year or three.

controlav,

With respect, please go back and read my first post.

If the controller is able to serve the bytes of the local files, why can it not serve the bytes of files on an SMBv2/3 share?

I imagine that the Venn diagram of people that own at least one Sonos speaker, a NAS - but a network that lacks the throughput for this operation looks a little asymmetric.

If the controller is able to add multiple local directories to share via a local HTTP service, it can also add the ability to proxy bytes that aren’t hosted on a local drive. I’ve written this same chunk of code myself. This issue is easily solvable without touching the speaker at all.