SMB2 (or SMB3) support must be supported NOW!



Show first post

281 replies

You can still force samba to work with Sonos by editing the smb.conf file and adding

       client min protocol = NT1
       server min protocol = NT1
       ntlm auth = yes

to the global section of that file.

Userlevel 1

You can still force samba to work with Sonos by editing the smb.conf file and adding

       client min protocol = NT1
       server min protocol = NT1
       ntlm auth = yes

to the global section of that file.


I only had to add

server min protocol = NT1

to get it to work. However, #disappointed

Userlevel 2
Badge +1

I had come across the SMB1 issue and the fact Sonos only support SMB1 a long time ago so I am shocked that apparently even the new S2 software still requires it.

Apparently Sonos have a workaround for their Windows app in that it uses http as per https://en.community.sonos.com/setting-up-sonos-228990/smb2-or-smb3-support-must-be-supported-now-6826700?postid=16341722#post16341722

That message does not give any details and Sonos have pretty much been totally silent about this entire SMB issue for years.

I would not regard NFS as a solution and AFP even less so, however what about WebDAV? This is basically http/https and without any details on how their PC share via http works it could be they are close to doing this already.

At least some if not all NAS boxes have built-in WebDAV support.

Whilst I feel it is absolutely necessary for Sonos to fix this themselves another approach I have not seen mentioned in this thread would be to run a VM on a NAS purely for the purposes of operating the SMB1 share. It would then not require additional hardware, would use the content already on the NAS, would allow the NAS itself to leave SMB1 turned off but would make the music accessible via ugh! SMB1.

Hello,

My sonos read my music library on a synology NAS.

Synology support SMB1, 2 and 3. It is recommended to disable SMB1 for security reasons.

The majority of my devices connect to it using SMB2 or 3.

Unfortunately, I cannot disable SMB1 because it is the only version supported by sonos.

When will sonos also support SMB2 or 3 ?

SMB1 : has been created in 1985 : 36 years ago

SMB2 : was released in 2006 : 15 years ago.

SMB3 : was released in 2018 : 3 years ago.

Thanks in advance.

Michel.

Maybe a all should complain by email to the Sonos CEO: ceo@sonos.com

That’s his/her email address according to:
https://support.sonos.com/s/contact?language=nl_NL

I’ve already send an email, wo is going to follow?

Please sort it out as I can’t backup to my NAS drive as the OS on those systems won’t backup to NAS with v1.  So I’m stuck and have to have a special NAS drive for Sonos with old school stuff on it.

Hello everyone, thanks to the introduction of our S2 platform, we've now added support for SMBv3. Sonos S2 devices will use the highest version of SMB supported by your NAS device. To access this update, you may need to manually change the configuration of your NAS device.

But the OP said that they were using old kit “Deciding I am probably safe to continue linking my (very) old Sonos setup (think Zoneplayer 100) “, so surely  this can’t run S2 software.

Bruce,

Sorry if my message was not clear or in a wrong section, english is not my mother langage.

Let me share my experience

I received last week a new PORT (S2). I upgraded the firmware and I use the latest S2 app on a mac.

I disabled SMB1 on my synology then created a new share volume. Sonos was not able to connect to it.

I re-enabled SMB1 on the synology and sonos was able to connect to it.

My oldest sonos device is a play1 running Sonos OS: S2, Version: 13.1.1 (build 63289260)

My conclusion is that a S2 devices does not support SMB2 or 3 and I just ask for the planned release date because I didn’t find it in the thread.

Michel.

Userlevel 7
Badge +22

That may or may not work, many NAS devices today refuse to support SMB v1 due to the security issues, others will if you can find the proper settings.

Even if a device supports v1 now that may be removed if it is updated.

Maybe we should start a petition to the CEO? I’m another Synology DMS 7 user with this same issue.

Userlevel 2
Badge +1

That’s true historically right, but do we know the current state? Maybe they’ve sold out with S2 and we dont know it lol. Also Have they monetized their data collection? - I know they don’t sell my personal data, but what about aggregate? Don’t forget about Sonos radio, they’ve monetized that!.

 

I don't think you need to worry about data collection from Sonos for streaming services. There is nothing left to collect. Amazon, Google or Spotify is already collecting everything with surgical precision every time you play a track, since these services handle everything for Sonos.

I don't think you need to worry about data collection for playing your local library either. If data collection was their intent they would have been a lot more eager to support local services….   

Userlevel 1

Hello,

My sonos read my music library on a synology NAS.

Synology support SMB1, 2 and 3. It is recommended to disable SMB1 for security reasons.

The majority of my devices connect to it using SMB2 or 3.

Unfortunately, I cannot disable SMB1 because it is the only version supported by sonos.

When will sonos also support SMB2 or 3 ?

SMB1 : has been created in 1985 : 36 years ago

SMB2 : was released in 2006 : 15 years ago.

SMB3 : was released in 2018 : 3 years ago.

Thanks in advance.

Michel.

Hi Michel,

Just seen release notes from Synology on DSM 7, they are dropping support for SMB1, so if Sonos don’t update to SMB2/3 with immediate effect then I don’t think it will work anymore.

Userlevel 7
Badge +22

Don’t hold your breath, that was first asked for back in the 2006 time-frame.

Work around it with a dedicated to Sonos SMB v1 NAS or a NAS (any protocol) to Sonos gateway and be done with waiting for Sonos to make the major changes required.

My Live Journal How-To: https://stan-miller.livejournal.com/

Controversial I know …but perhaps a very large majority of Sonos customers have now switched to using online streaming music services and that NAS/Local Library users have become very much in the minority, to the extent that there is no ‘mileage’ in developing this feature…🤔?

I have a fair-sized local music library myself stored on a NAS box, however I do find myself using some of the ‘millions’ of tracks/albums/playlists etc; now easily accessible online via the paid/free streaming music services, probably much more often these days. My local library has started to become a little neglected, truth be told.

Userlevel 7
Badge +23

A bigger concern for me would be if Sonos want to stop supporting local file servers completely.

 

Sonos could simply delete SMB support tomorrow (which would be the most secure option), and those of us using PCs or Macs to host music files would still be fine, as SMB is not required for those platforms any more.

If NAS users want a solution, they just need to get the http server running on those NASs, which would take a few hours of work. However there has been zero interest expressed in this work to date.

Sonos have the telemetry to know how many users rely on file servers, and how many of those use NASs and need SMB support. One can only assume the numbers are small enough for them to not be too concerned about that demographic.

Userlevel 7
Badge +23

If NAS users want a solution, they just need to get the http server running on those NASs, which would take a few hours of work. However there has been zero interest expressed in this work to date.

Are you saying that that I could get this to work over HTTP with a few hours of work?  Care to share?

Sure, PM me and I’ll give you the details. Requirement: A NAS platform that can run .NET Core and knowledge of C#.

Userlevel 7
Badge +23

I think Sonos should simply pull support for NAS users entirely. Sharing files from PCs and Macs will still work, and NAS users can use Plex and, more importantly, quit complaining about SMB support.

I don’t think, @PudgyChicken, that you understand what has been discussed. There is no additional memory space in which they could store a backported version of the kernel. The current kernel appears to have taken all available memory. 

And there just isn’t any spare space on the devices at all, inside or external to the kernel, without removing features. 

Now, if you’re talking S2 devices, that’s a whole different beast, and I could agree with what you’re saying. Which, if you read the thread, we’re all hoping at some point they’ll do. But, as @controlav  and others have pointed out, the amount of folks that want this, while vocal,  is relatively small. It may not be financially intelligent to do that work, which is likely both extensive and costly. It may behoove them to put their limited resources elsewhere, as there are already several solutions, as described in this thread. 

Userlevel 6
Badge +13

If they have no desire to support this or want to pull it all together then they need to come clean with their customers.

Agree with @PudgyChicken that leaving this unpatched reeks of ineptitude or indifference- both are unacceptable IMO. 

Userlevel 7
Badge +22

Since you already have a NAS the Raspberry Pi gateway will be your cheapest option. Pick up a minimal Raspberry Pi Zero-W kit. Follow the instructions here and it should be working with no issues.

https://stan-miller.livejournal.com/357.html

If you want a wired Ethernet instead of WiFi connection then one of the Pis with wired Ethernet would be the way to go. A used Pi 3b, 3b+ would be less but a 4 2GB would work as well.

-----

Without a NAS the SMB v1 file server setup is the better option.

https://stan-miller.livejournal.com/650.html

 

If you have a problem PM me so we don’t clutter up the forum with non-sonos troubleshooting posts.

Badge

I guess some of you are already aware, just to state here that Synology new OS (DSM 7.0) currently does not support anymore SMB1, and it seems it’s not planned to do so.

Such an issue for NAS users!

Badge

Hi,

 

Would you be so kind as to provide a link to this information? I’ve just spent five minutes on Google, looking for this data, and haven’t been successful in finding it. 

 

yeah I am following this thread in the Synology forum here 

 

ciao

mk

Userlevel 7
Badge +22

If you are concerned about security you can share your SMB2/3 or other protocol NAS to Sonos using an SMB v1 Gateway.

Here is how to do it on a Raspberry Pi, the same settings will work on most Linux computers.

https://stan-miller.livejournal.com/357.html

Badge +1


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

Sure you can 

you create a Docker Macvlan network with a dedicated list of IPs and with sole read access to your music ( with a dedicated login/password).

And you can deactivate definitively the SMB1 support in Your Synology for the native network.

This makes a specific dedicated local network for your Sonos only.

cheers 

PHILIPPE 

 

Userlevel 7
Badge +22

From the Samba 4.17 release notes:

https://github.com/samba-team/samba/blob/master/WHATSNEW.txt

 

NEW FEATURES/CHANGES
====================

Configure without the SMB1 Server
---------------------------------

It is now possible to configure Samba without support for
the SMB1 protocol in smbd. This can be selected at configure
time with either of the options:

--with-smb1-server
--without-smb1-server

By default (without either of these options set) Samba
is configured to include SMB1 support (i.e. --with-smb1-server
is the default). When Samba is configured without SMB1 support,
none of the SMB1 code is included inside smbd except the minimal
stub code needed to allow a client to connect as SMB1 and immediately
negotiate the selected protocol into SMB2 (as a Windows server also
allows).

None of the SMB1-only smb.conf parameters are removed when
configured without SMB1, but these parameters are ignored by
the smbd server. This allows deployment without having to change
an existing smb.conf file.

This option allows sites, OEMs and integrators to configure Samba
to remove the old and insecure SMB1 protocol from their products.

Note that the Samba client libraries still support SMB1 connections
even when Samba is configured as --without-smb1-server. This is
to ensure maximum compatibility with environments containing old
SMB1 servers.

Reply