Skip to main content
Contributor I
February 6, 2021

SMB1 still required in 2021 for music shares?

  • February 6, 2021
  • 35 replies
  • 6042 views

As reported in many other topics apparently it's still necessary to use SMB1 for playing music from a Synology Diskstation system? It's now 2021 and I just had to change the settings on my diskstation to allow the unsecure SMB1 in order to be able to add a shared folder to my Sonos music library.

Sonos seems to be closing all topics on this forum about this subject for further comments, but is not addressing the problem?

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.

35 replies

Lyricist I
August 26, 2021

The best solution is to use Plex, instead of a fileshare.

this have the bonus of providing access from a phone or desktop pc to the music library everywhere.

Lyricist I
September 18, 2021

Airgetlam, I know that Sonos is ignoring the SMBv1 security issue because SMBv2 was released by Microsoft in 2006.  It’s been 15 years.  If they were going to provide SMBv2 support, they would have done so by now.

There are several misconceptions that I see throughout these threads regarding SMB v1, v2, and v3 with regards to Sonos (and Denon, too).  The first misconception is that Sonos has to change the protocol on all their old devices.  What kind of development roadmap and product-line architecture prevents you from introducing improvements into new products because your old products can’t support them.  Sonos (and Denon) could let new products support SMBv2, while older units continue to support only SMBv1.  The new units could even support both v2 and v1.  This would allow owners of old Sonos products to work with a NAS that supports SMBv1, and new Sonos products to work with a NAS that supports SMBv2.  Sucks for owners of older Sonos products, though.

The second misconception is that a NAS can support only one version of SMB.  That is certainly not true for Synology DSM.  DSM 7 allows you to configure the minimum supported version of SMB as low as v1, with a default of v2. The maximum version is v3.

The third misconception is that SMBv2 is more complex than SMBv1.  Actually, in some ways it is less so.  SMBv1 has over 100 commands and subcommands.  SMBv2 has just 19.  SMBv2 also eliminates many of the underlying protocols that SMBv1 supports:  NetBIOS over IPX, NetBIOS over UDP and NetBEUI.

The fourth misconception is that a separate NAS just for streaming to Sonos is secure because it limits the vulnerability just to this single-purpose NAS.  Unfortunately, having any SMBv1 devices on your LAN compromises the entire LAN.

I’ve been thinking about an SMB gateway running on a Raspberry Pi that accesses an SMB v2 or v3 share (from a NAS), and re-shares it as SMBv1 (for shameful speaker-manufacturers’ products).  With a firewall on this host configured to allow access only to the NAS and the Sonos devices it might provide reasonable security, but I haven’t finished my evaluation.  It would be very important, though, to ensure that no other devices on the LAN have access to this gateway.

I think that Sonos’s (and Denon’s) failure to provide SMBv2 support in new products is very disrespectful to their customers.  As with many companies that don’t really understand security (or even the need for security), they think it’s OK to ignore their customers’ security needs as long as sales are good.  For shame.

Ken_Griffiths
September 18, 2021

@rbandes,

Have you not seen this, posted by another user here with regards to a reply from Sonos CEO on this topic?

https://en.community.sonos.com/advanced-setups-229000/smb1-security-issue-lack-of-response-from-sonos-6860761?postid=16551779#post16551779

 

jgatie
September 18, 2021

Airgetlam, I know that Sonos is ignoring the SMBv1 security issue because SMBv2 was released by Microsoft in 2006.  It’s been 15 years.  If they were going to provide SMBv2 support, they would have done so by now.

There are several misconceptions that I see throughout these threads regarding SMB v1, v2, and v3 with regards to Sonos (and Denon, too).  The first misconception is that Sonos has to change the protocol on all their old devices.  What kind of development roadmap and product-line architecture prevents you from introducing improvements into new products because your old products can’t support them.  Sonos (and Denon) could let new products support SMBv2, while older units continue to support only SMBv1.  The new units could even support both v2 and v1.  This would allow owners of old Sonos products to work with a NAS that supports SMBv1, and new Sonos products to work with a NAS that supports SMBv2.  Sucks for owners of older Sonos products, though.

The second misconception is that a NAS can support only one version of SMB.  That is certainly not true for Synology DSM.  DSM 7 allows you to configure the minimum supported version of SMB as low as v1, with a default of v2. The maximum version is v3.

The third misconception is that SMBv2 is more complex than SMBv1.  Actually, in some ways it is less so.  SMBv1 has over 100 commands and subcommands.  SMBv2 has just 19.  SMBv2 also eliminates many of the underlying protocols that SMBv1 supports:  NetBIOS over IPX, NetBIOS over UDP and NetBEUI.

The fourth misconception is that a separate NAS just for streaming to Sonos is secure because it limits the vulnerability just to this single-purpose NAS.  Unfortunately, having any SMBv1 devices on your LAN compromises the entire LAN.

I’ve been thinking about an SMB gateway running on a Raspberry Pi that accesses an SMB v2 or v3 share (from a NAS), and re-shares it as SMBv1 (for shameful speaker-manufacturers’ products).  With a firewall on this host configured to allow access only to the NAS and the Sonos devices it might provide reasonable security, but I haven’t finished my evaluation.  It would be very important, though, to ensure that no other devices on the LAN have access to this gateway.

I think that Sonos’s (and Denon’s) failure to provide SMBv2 support in new products is very disrespectful to their customers.  As with many companies that don’t really understand security (or even the need for security), they think it’s OK to ignore their customers’ security needs as long as sales are good.  For shame.

 

I don't know where you are getting these "misconceptions" from, but it's not here.  Nobody ever stated them.  Matter of fact, the fact that S2 will allow Sonos to upgrade to a higher version of SMB was expressly stated as one of the benefits of the S2 split.

106rallye
September 18, 2021

In the Sonos system all speakers need to be on the same software. That’s probably why you can’t have some speakers on SMBv1 and others on v2.

Contributor I
October 7, 2021

The best solution is to use Plex, instead of a fileshare.

this have the bonus of providing access from a phone or desktop pc to the music library everywhere.

Thank you for this! Genius and I just killed SMB1 on my Synology. Works great and now secure. Love me some Plex. 

Lyricist III
November 12, 2021

Yes, this is ridiculous. But don’t just complain here, complain directly to Sonos.

Sadly, they no longer accept email at support@sonos.com

You can open a real time chat, which is mildly annoying. The person claimed “This case will be added on the list of customers that have the same concern.” I have no clue if that’s a lie or not, but it can’t hurt to try.

 

Lyricist I
November 29, 2021

So with the new Update 13.4 its Support now SMB2 and SMB3. 

 

“If you have problems with album covers: I have them too. Obviously they are not quite finished with SMB2 and SMB3, because otherwise you would have announced the possibility in a big way. The Sonos 13.4 changelog only officially included other improvements”

 

Source: https://stadt-bremerhaven.de/sonos-unterstuetzt-endlich-smb2-und-smb3/

el rubio
November 29, 2021

for those who want to try it, I have SMBv2 working fine with my Synology NAS - see my post here

 
salu2.eu
Lyricist III
December 29, 2021

I’ve found a workaround for using S1 with a Synology NAS without activating SMB1.

  1. Create a free Plex account. A free Plex account won’t work on mobile stand alone, but that’s not an issue for our use case.
  2. Install Plex via Package manager on your Synology. From there, point Plex towards your music share folder.
  3. Add a music service in your S1 Sonos setup and look for Plex
  4. All set! Play all your lossless files without compromising security. Sonos’ in app search function will also look within Plex which is great.

You might need to add a wired connection to your Connect as I encountered bandwidth issues. But with an ethernet cable plugged in, this setup ran smoothly.