Skip to main content
Enthusiast I
June 14, 2019

SMB2 (or SMB3) support must be supported NOW!

  • June 14, 2019
  • 281 replies
  • 30268 views
We are writing summer 2019 and still Sonos only supports SMB version 1 for the Music Library share.

This is not acceptable.

A file share running SMB1 is extremely vulnerable to all the variants of cryptolocker virus that exists today. File share servers (NAS, Windows, Apple OS) can only support one version of SMB - so you cannot from the same box have one file share (for Sonos) using SMB1 and the other file shares using SMB2 or SMB3. This way Sonos puts each and every file share at serious risc - just because they don’t update their file share protocol to comply with this century.

And for the record - the “solution” through PLEX is not a solution. Unstable at best.
This topic has been closed for further comments. You can use the search bar to find a similar topic, or create a new one by clicking Create Topic at the top of the page.

281 replies

Bumper
December 12, 2020

Do they (Sonos) really have no space to update the kernel? 😳

Airgetlam
December 13, 2020

In general, many of us believe that is the case in S1 legacy devices. The amount of memory on those devices is extraordinarily limited. The common belief is at some point, hopefully in the near future, the extra memory in newer S2 devices will allow Sonos to replace the old kernel with a newer version in the S2 firmware, that is capable of including a newer version of Samba. 

There has been no confirmation from Sonos, one way or another. So essentially we’re making a guess here, but it seems logical, and fits the facts as we know them. 

Bruce
Bumper
December 13, 2020

I was under the impression that S2 devices have lots of space so confused by the “… as does Sonos ...not enough space to update their kernel” but I’m not totally up on all the details and acknowledged I may not be comprehending the nuance of what you are saying.

 

Anyway Sonos needs to fix this yesterday! (If there is space etc)

Contributor I
December 13, 2020

I can say that it seems with Synology DSM 7.0 beta Sonos libraries won’t work anymore, even with SMB 1 selected.

 

https://community.synology.com/enu/forum/20/post/139200

Stanley_4
Grand Maestro
December 14, 2020

Sonos has been maintaining an antique Linux kernel, they had to as the changes made to Linux took them past the memory limits on their earlier hardware. Trying to port all the changes they made to the old kernel to a modern kernel is not something that can be quickly done, once done a LOT of testing needs to follow before releasing it to the user base.

My suggestions are:

Use a NAS to SMB v1 gateway device, a Pi for example will support any common NAS file share on the input and SMB v1 on the output. 

Use a SMB v1 capable NAS just for your Sonos music. Most of the tiny computers like Pis will support this with the addition of a storage medium, thumb drive, USB hard drive or the like.

 

I don’t have a warm fuzzy feeling about SMB v1 on a NAS containing important data and I wouldn’t do that.

Contributor I
December 14, 2020

The issue of them using SMB surely still exists under Pi, they create an insure network?

 

In the end they did a big fancy update recently to the Sonos OS, so surely they can update SMB.

 

There is another option as well, remove the 5 Sonos devices I have and replace them with something else.

 

I’ve currently got it going via Plex, which adds another layer which really shouldn’t be needed.

Trending Lyricist I
December 14, 2020

Hi Sonos team

as Synology does not support anymore SMB1 in their NAS from DSM 7.0 beta and probably from official releases of the upcoming official DSM 7 F/W, Sonos equipments cannot connect anymore to the music.

SONOS must now port SMB2 or SMB3 Otherwise many peoples will buy products from competition

regards

 

Stanley_4
Grand Maestro
December 15, 2020

Using a Pi as a gateway to offer Sonos SMB v1 isn’t secure but since it has no access to your real NAS and data, the worst case scenario is you get compromised and have to swap out the boot SD card and reboot.

Using one as a v1 server you might have to re-copy your music too if that got corrupted. You can minimize that risk by mounting the music in read-only mode if you wish.

 

Yes Sonos should fix this but I can’t see a way to do that for S1 and while possible for S2 it is not a simple or fast project.

Bumper
December 15, 2020

Sonos talk up S2 as a new operating system so it is BS that they don’t fix it. This is a very old flaw and shame on them that they have not fixed it yet. 
 

Yes there are work arounds but we shouldn’t require this on new hardware and an OS that was released in 2020. 
 

They lack the will to do it and frankly I hope people keep coming at them here and on social media until they fix this. 

Trending Lyricist I
December 15, 2020

Hi,


This post just to inform that there are 3 solutions for fixing that sad issues ( sad for Synology and Sonos)

- Use a cheap Raspeberry PI 0 that will make the link between the Synology/SMB2 or 3 and the Sonos/SMB1. I did not experiment that solution as it would require additional hardware and a good minimal Linux skill.

- Use the Plex solution . I am currently experimenting that solution. I would say that it did not start at the beginning but finally it did without clear reasons. Therefore I have some doubts about its reliability. The big advantage of this solution is that you have the  jackets of the albums just beside each album name that you don't have with the usual method.

- use an additional Docker Samba interface between the SMB>1 Synology and the SMB1 Sonos. I am currently experimenting as well that solution that is working well.

So currently I have both methods running between my Sonos equipments and the DSM 7.0 beta.

My wife is happy !

But let's be honest : I hope both Synology and Sonos will find TOGETHER a solution for music lovers.

Regards (from France )

Philippe