Skip to main content
Phil.Coleman
Contributor I
May 14, 2017
Answered

Support for SMB v2 or v3

  • May 14, 2017
  • 108 replies
  • 23234 views
With all the recent reports and issues with the WannaCry ransomware I wanted to restrict use of SMB v1 on my home network. My NAS blocks this to the outside world but I wanted to secure things internally as well. I can configure the NAS to not support SMB v1 but this then prevents the Sonos controller app from seeing the share. When will Sonos support later versions of SMB? I had seen another thread on this somewhere and it sounded like it wasn't going anywhere. Is it possible to get an update on this please.
      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.
      Best answer by Phil.Coleman
      The problem is that as long as companies produce products that rely on old out of date software other companies have to continue to support them to remain relevant in the market, it's a vicious cycle.

      108 replies

      MikeV
      MikeV
      May 15, 2017
      Here's the link to the previous topic regarding SMBv1. I fully agree that at this point it should be removed, but NAS devices still ship with it enabled, and most don't provide any way to turn it off either. I would imagine if most NAS manufacturers started removing support for SMBv1, you'd probably find Sonos moves pretty quickly to update their devices.

      https://en.community.sonos.com/troubleshooting-228999/sonos-smb-implementation-error-900-when-adding-music-library-6765736
      The S in IOT stands for Security.
        Bright Shadow
        Lyricist I
        May 15, 2017
        Ya with you guys. I shut off SMBv1 on everything internally including my NAS which broke my SONOS music share. I hope it gets resolved soon. I'm not about to enable SMBv1.
          Phil.ColemanAuthorAnswer
          Contributor I
          May 15, 2017
          The problem is that as long as companies produce products that rely on old out of date software other companies have to continue to support them to remain relevant in the market, it's a vicious cycle.
            Stanley_4
            Stanley_4
            Grand Maestro
            May 15, 2017
            I put my insecure stuff on a dedicated LAN segment that is blocked from communicating with the rest of my stuff on other, more trusted segments. It isn't a solution but at least it limits any problems as much as possible.
              Mattias_4
              Avid Contributor III
              May 16, 2017
              Just disabled SMB2 in our network and moved the library to a Linux box instead.
              A shame that SONOS still doesn't support SMB2. Last time I looked in the calendar it was 2017.
                Stuart_W
                Stuart_W
                World-Class Superstar
                May 16, 2017
                As far as I'm aware there have been very few if no reports of domestic infection from the WannaCry ransomware.

                So, I don't want to cry (wolf).
                Arc + Sub (Gen 1) + 2 x Play 1/ Stereo Play 3s/ Era 100 Stereo in Kitchen, One Stereo in Bedroom, Play 1 stereo pair in Study, Play 1in Bathroom, Sonos Move 2
                  MikeV
                  MikeV
                  May 16, 2017
                  Reality is, as long as you've kept your computers patched, the fix was released two months ago for operating systems still supported by Microsoft. But that still doesn't mean that SMBv1 should be used when there are better, more secure options available in the form of newer versions of SMB.

                  Keep in mind that US-CERT is recommending not using SMBv1 as part of its SMB Best Practices... so I think it's pretty important to move on to a newer, more secure version.
                  The S in IOT stands for Security.
                    Constantin
                    Enthusiast II
                    June 3, 2017
                    I put my insecure stuff on a dedicated LAN segment that is blocked from communicating with the rest of my stuff on other, more trusted segments. It isn't a solution but at least it limits any problems as much as possible.
                    I did something similar by putting my Sonos content on a disposable hard drive attached to an Apple Airport. For the meagre NAS bandwidth requirements of a Sonos, this solution is adequate. That way, I can keep the minimum connection requirements for the main server at SMB3. As the music share on the main server is updated, I simply clone the Airport drive to match.

                    I don't expect a major shift in the industry until ransomware broadly infects SOHO sites. Why Sonos is putting off the inevitable is a mystery to me, however. Updating the ZP network stack with more recent versions of readily-available SMB libraries should be trivial compared to the work that went into developing their innovative mesh networking strategy.
                    Constantin
                    Enthusiast II
                    June 3, 2017
                    Here's the link to the previous topic regarding SMBv1. I fully agree that at this point it should be removed, but NAS devices still ship with it enabled, and most don't provide any way to turn it off either.

                    AFAIK, current versions of Windows server as well as FreeNAS ship with SMB1 and NTLM v1 authentication turned off by default. They have to be manually enabled.
                    jgatie
                    jgatie
                    June 3, 2017
                    Constatin, you have no idea whether Sonos is "putting off" anything. Sonos is very tight lipped as to what is being worked on, and anyone who does know is bound by an NDA. For all you or I know, the very next Sonos release could contain support for other versions of SMB, so you definitively stating that Sonos is putting it off is pure speculation and negativity.
                    Show more replies
                    Terms & ConditionsAccessibility statement