Skip to main content
Williams_Nest
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

    Show previous replies
    apb78
    Lyricist III
    February 1, 2021

    That would indeed be odd, since both of those run on your local device or the server,and not on the limited memory of the Sonos equipment.

    Well one of my speakers is the new Play One which Sonos said we needed to support Airplay and other features.  I imagine implementing Alexa is a little more memory demanding than adding an SMB2 stack.

    Stanley_4
    Stanley_4
    Grand Maestro
    February 2, 2021

    Well one of my speakers is the new Play One which Sonos said we needed to support Airplay and other features.  I imagine implementing Alexa is a little more memory demanding than adding an SMB2 stack.

     

    Actually no, Alexa is an app that can easily run on the current Linux kernel. SMB is s system service that is tightly integrated into the current kernel. Going to v 2 or 3 requires a newer kernel, as well as porting all the Sonos patches and tweaks. Not fast or easy and you don’t find Linux kernel programmers cheap either.

      Buckingham_Crimpysnitch
      Lyricist I
      February 7, 2021

      I just started using Sonos and tried to connect to a Synology NAS. The S2 controller was showing error messages that made no sense (https://support.sonos.com/s/article/262?language=en_US&utm_source=cr-care&utm_medium=serverstack&utm_campaign=de-cr-care-serverstack).

       

      I finally found this and reactivated SMB1 which I feel uncomfortable with because it is old and full of security flaws.

       

      Sonos need to get their act together and implement SMB3 asap.

        Stanley_4
        Stanley_4
        Grand Maestro
        February 7, 2021

        Been saying that for many years, no Sonos update in sight.

        Easy solution to the security issues is use a NAS to SMB v1 gateway so your NAS can run in secure mode but Sonos can see your music through the v1 gateway.

        I did it on a Raspberry Pi, a Zero W is a good choice.

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

        apb78
        Lyricist III
        February 8, 2021

        Well one of my speakers is the new Play One which Sonos said we needed to support Airplay and other features.  I imagine implementing Alexa is a little more memory demanding than adding an SMB2 stack.

         

        Actually no, Alexa is an app that can easily run on the current Linux kernel. SMB is s system service that is tightly integrated into the current kernel. Going to v 2 or 3 requires a newer kernel, as well as porting all the Sonos patches and tweaks. Not fast or easy and you don’t find Linux kernel programmers cheap either.

        They have a Windows client they regularly update.  There is no reason they couldn’t do a secure proxy through their own software without additional configuration or accommodation by their users.  Windows programmers are not rare, nor necessarily expensive.  Again, Sonos is a “premium” product and they charge accordingly for those products.  So I get it, you think we should all roll out our own hardware to address Sonos’s unwillingness to address well know, long existing security flaws.  So noted, I respectfully disagree.  We can agree to disagree.

        controlav
        controlav
        Lead Maestro
        February 8, 2021

        They have a Windows client they regularly update.  There is no reason they couldn’t do a secure proxy through their own software without additional configuration or accommodation by their users.  Windows programmers are not rare, nor necessarily expensive.  Again, Sonos is a “premium” product and they charge accordingly for those products.  So I get it, you think we should all roll out our own hardware to address Sonos’s unwillingness to address well know, long existing security flaws.  So noted, I respectfully disagree.  We can agree to disagree.

        The Windows client already includes SonosLibraryService, which is a proxy designed specifically to avoid the SMB problem. SMB is not required when sharing files from Windows (or Mac) devices, this is purely a NAS issue.

        Author of the leading independent Sonos apps for Android, MacOS, iOS, Windows and Xbox.
          Airgetlam
          Airgetlam
          February 8, 2021

          Additionally, it’s the software on the speakers, and not the desktop/mobile controller that is accessing the music on the NAS. Hence the oft referred to memory issue for an updated kernel that supports a higher version of SMB on the early players/speakers. 

          Bruce
          Stanley_4
          Stanley_4
          Grand Maestro
          February 8, 2021

          For folks like me that have neither Windows or a Mac running, neither are a good option.

          The Pi fixed my issues for a few bucks and a couple watts of power, no other solution comes close here.

          I don’t think we should roll out our own hardware to fix a Sonos option. I just don’t see another viable option for NAS users.

          I’ve been bitching about the Sonos SMB v1 issue since about 2008. Not seen any result.

          I have abandoned any hope of seeing a Sonos solution and dealt with the issue as the only viable alternative.

          Hundreds of posts here have had no impact, so don’t hold your breath.

          Particularly for a SMB v2 fix for S1 systems although a dedicated Sonos Music NAS or Gateway in a Boost case would be really neat for S1 folks. Easy to just stuff a Pi in there and ship it too.

          PLCMAN58
          Chromatic Producer I
          February 14, 2021

          I am looking for a resolution to the SMB1 fiasco. It appears that SYNOLOGY is going to disable support for SMB1 when DSM V7.x is released.  I have multiple SONOS, NetGear NEOTV550 and now Zappiti media players that require SMB1 and they will not work with latter versions.

          I just purchase the Zappit OneSE4K HDR in December 2020 and will try to return it back to Amazon since it appears that it cannot be updated to support a newer version of SMB. None of  the reviews of the product mention that the product required SMB1.

           

          Palle Louw 1
          Lyricist I
          March 4, 2021

          After upgrading my Synology NAS to version 7 I can not link to my music library from my Sonos system. The error is detected by Synology as follows:

          This issue is occurring as NTLMv1 is disabled in DSM 7.0 Beta for security concerns, and only NTLMv2 is supported by default. Whereas Sonos does not support using NTLMv2.

          Is it possible for Sonos to correction this?

          Show more replies
          Terms & ConditionsAccessibility statement