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

    Collaborator I
    June 13, 2018
    Hi everyone, starting with today's update, Sonos 8.6, Windows computers will be able to set up shares to their local libraries to Sonos without using SMB file sharing. We aren't removing support for SMB at this time, and you will continue to need to use it for NAS drives, but Mac computer and Windows computers now both have the ability to share using our implementation of HTTP file sharing using the Sonos app. For more details, see the post here.

    Thank You.

    Can confirm it is working too.

    Pete
    MikeV
    June 13, 2018
    Many NAS boxes do have the ability to run a web server... it's just a matter of getting things configured in such a way that Sonos would be able to connect to it... like the odd port number, authentication (if any), and any path structure that Sonos might use ahead of the actual folders/files.

    Shouldn't be too hard to monitor with something like Wireshark, since it's HTTP. Of course, then getting Sonos to use it as a web service rather than SMB might be the next trick.
    The S in IOT stands for Security.
    Lyricist I
    June 14, 2018
    Mac computer and Windows computers now both have the ability to share using our implementation of HTTP file sharing using the Sonos app.

    I consider this a weird hack to “solve” the issue of Win 10 dropping OOTB support for SMBv1 (for good reason!). We asked for an alternative for SMBv1 since *years*, and now only one months after latest Win 10 version, you deliver a half-baked “solution”. Still, this is a weird hack, implementing a web server inside a client application to allow external (speaker) access to local files. Let us see how long it takes someone finds a security issue inside the Sonos “client”, as I guess Sonos’ development strengths do not necessarily include secure http servers. And what happens next, will the application become a full functional email client (ref: http://www.catb.org/jargon/html/Z/Zawinskis-Law.html)?

    Besides all the fuzz: what is so difficult in implementing an SMBv2 or v3 client in Sonos speakers? I guess we all would accept any reasonable answer much more than just no communication and weird hacks/incomplete workarounds.

    Jonas
    passopp
    June 14, 2018


    Besides all the fuzz: what is so difficult in implementing an SMBv2 or v3 client in Sonos speakers? I guess we all would accept any reasonable answer much more than just no communication and weird hacks/incomplete workarounds.

    Jonas


    As long as Sonos does not officially state the name of the actual Linux distro and, more importantly, the kernel version which is running on all of their zone players, we'll never know the particular reason for dodging a much required SMBv2/3 implementation.

    Could be insufficient physical memory (at least on older components), a very much outdated kernel version or even a bit of both.
    MikeV
    June 14, 2018
    [quote=passopp]
    Could be insufficient physical memory (at least on older components), a very much outdated kernel version or even a bit of both.

    Considering IPv6 was recently discovered to be present on some newer speakers (namely, those that have been identified as having Airplay support coming soon, though someone found it on a newer Play:1 too), a lack of device resources on older devices is a good possibility for why SMBv1 hasn't been updated to a newer version. Of course, there's also the possibility that they're using multiple kernel versions, with newer devices on a newer version.

    And while I know Macs aren't attacked as often as PCs are, this HTTP sharing process has been present with the MacOS Sonos controller for a while now... I scratched the surface of it over 8 months ago, but I think it had already been in use for a few months before then.
    The S in IOT stands for Security.
    Stanley_4
    Grand Maestro
    June 16, 2018
    As long as Sonos does not officially state the name of the actual Linux distro and, more importantly, the kernel version which is running on all of their zone players, we'll never know the particular reason for dodging a much required SMBv2/3 implementation.

    Sonos Linux source code is available, this post and the next few talk about that:

    https://en.community.sonos.com/controllers-software-228995/support-for-smb-v2-or-v3-6787081/index3.html#post16228313
    Contributor I
    August 4, 2018
    The 8.6 "solution" is no solution at all. NAS users tend to be the audiophiles who were drawn to Sonos for its audio quality and have ginormous libraries on NAS. And Sonos has ignored us for years. In fact, it seems they are preparing to abandon their most committed customers to compete with Echo, Home and HomePod.

    But now that they are public, they will probably be more likely to respond to a social media campaign. As posters here know, they've consistency ignored the feedback from these forums. Join me on Twitter and let's see if they respond any differently: https://twitter.com/yobyot/status/1025790462072967169
    Lyricist I
    October 1, 2018
    For those of us not using Windows to share our libraries, can we expect an update to HTTPS or SMB 2/3 or are we locked in at smb1?
    We're still looking into options for NAS drives but don't have any specific details I can share. The HTTP share is created by the Sonos app, which NAS drives don't and can't run. I'll make sure to let you all know if there's any news regarding NAS sharing away from SMB1 that I can let you in on in the future.


    Any news? In times of WannaCry Sonos should be much faster...
    Lyricist II
    December 2, 2018
    Like so many others before me, I find myself on these forum threads after having just purchased my first Sonos product and finding out it doesn't support any modern file sharing mechanisms.

    Hi everyone, starting with today's update, Sonos 8.6, Windows computers will be able to set up shares to their local libraries to Sonos without using SMB file sharing.

    For those of us who can't or don't want to use the Sonos app on the media server, is there any hope of seeing support for a standard like WebDAV, rather than the proprietary Sonos HTTP protocol? I don't even need TLS (in case certificate management is considered a showstopper), since my media is streamed over its own, isolated wired network.

    If WebDAV is not on the horizon, as there have been no updates here for the past few months, may I again ask if SMBv2 or SMBv3 are going to be available any time soon?
    Stanley_4
    Grand Maestro
    December 2, 2018
    I think you'll have time to plant a redwood tree, watch it grow, harvest and dry the lumber and build yourself a new deck for your Sonos to sit on before we hear even an announcement. :-)

    Just get a Raspberry Pi and set it up to serve your music and be done with it. Maybe by the time th Pi goes out of support Sonos will have news.