SMB2 (or SMB3) support must be supported NOW!

Oh, forgot to add, I don’t work for Sonos and I have not been quiet or kind to them over many of their decisions that have had negative impacts on me.

A 20 minute / 20 buck fix to a minor problem just doesn’t rise to that level.

Stanley, thanks for the summary. That explains it more clearly than the other posts I’d been flipping through. 

I don’t fully understand the kernal memory issue as I’m not that technical. Does Sonos still use the same kernal on both the S1/S2 hardware, so is that why the S2 hardware won’t be updated with a kernel supporting SMB2, even though S1 is now legacy equipment?

Knowing what Sonos is actually doing has always been hard, almost impossible now that they locked us out of almost all internal data.

I think both S1 and S2 are still on the same old kernel, can’t prove it though. If you dig through the Sonos GPL documentation you might find evidence of their direction.

I’m sure the S2 will migrate to a newer kernel, maintaining the old one is likely getting more and more difficult. Once migrated it would actually be difficult to force many of the new native protocols back to the antique versions S1 is limited to. When is hard, times are grim and free money to do things is short everywhere, the change will not be cheap.

Memory in Sonos comes in two basic flavors, persistent code/data storage, where the data like music index and playlists live and the programs downloaded from Sonos that run the hardware reside when the device is powered down and random access memory where the programs are run and transient data stored, all that is blanked at power down.

There are charts around that show the amounts of memory in the different devices and versions. The main take-away is the S1 stuff has much less of both types of memory than the S2 stuff.

The lack of memory has forced Sonos to make some hard choices pre-split, removing stuff some customers really liked in order to add new stuff that more customers wanted. With the S2 split they can keep adding to the S2 gear while leaving the S1 alone and not aggravating the S1 owners.

Come on SONOS get with the times when DSM 7 become GA. you will be getting a lot of calls as Synology do not support SMB 1.0 by default. 

OK, I am now hit with this issue, I have the Synology DSM beta installed and I now cannot connect my Sonos system as they have disabled ntlmv1

More info here

[Update] Lost SMB access with NTLMv1 in DSM 7 Beta | Synology Community

I don;t understand what this means apart from I now cannot access my music

Hi Mick

you will need to install the “SMB Service” package on your DSM 7 NAS drive to enable SMB 1 protocol and get your music library back. 
 

it worked for me. 

Yes I have done that but I wonder how long Synology will provide that!

Dunno but it should be OK with DSM 7 as it’s an additional add on. 
 

i think the main point here with SONS is for them to update there software so that this can be uninstall from DSM and reduce a security risk and get it working by default. 

My first choice would be for Sonos to drop SMB v1 and enable the new versions too.

As an alternative you can easily set up a gateway from your NAS, using any Linux supported protocol to the required SMB v1 for Sonos.

Not great but is sure beats burning your Sonos gear in the drive in protest. :-)

Another user affected by the upgrade to DSM 7 and losing access to the music folder.

Using android and synology, I do not see any options to cast music to sonos. 

@Sonos  - either support chromecast on sonos arc to cast from android or atleast upgrade to SMB 2 or 3 and allow access to the music files from within sonos app

Edit: updated to refer to sonos to support chromecast with Sonos Arc, One SL