Skip to main content
Stuart_49
Stuart_49
August 29, 2021
Answered

connecting music library on Synology NAS to Sonos

I’ve got a new Synology NAS and trying to connect Sonos to the music folder on it. I’ve enabled SMBv1 and tried everything else that I’ve read in the Sonos community and Synology knowledge base. (I used a WD NAS for years with Sonos, BTW)

I’m using a Mac and the path to the music folder is:

//NASsynology/Volume 1/for sonos

(I’ve tried creating a separate folder just called “sonos” thinking maybe it doesn’t like the space in the name; also tried removing the “Volume 1” from the path and/or taking the space out and just calling it “volume1” which is how the name appears sometimes in Synology; also tried the IP address in place of the “NASsynology”...all with no luck)

 

I’m getting an access denied error (telling me to check the ID/password) when using the Synology user-ID/password, as well as when I just skip the ID/password step and just leave it blank.

 

Thanks for any help!

 

 

 

 

    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.
    Stuart_49
    Stuart_49Answer
    September 1, 2021

    Just to close with success on this, in case someone else has difficulty with the Synology NAS connection to Sonos as I surely did. There was in fact an additional setting that enables NTMLv1 on Synology (in addition to SMB setting). Thanks Airgetlam for that, I just couldn’t find it anywhere in Synology settings until I got on the phone with Sonos support and they were able to show me where the NTMLv1 enable is. Also, on the Mac at least, the path that worked for Sonos excluded the “Volume 1” qualifier, since that threw an error when I tried to include it.

    View in thread

    35 replies

    Show previous replies
    John B
    June 16, 2022

    Just another Sonos fanboy here, but out of curiosity... 

    I have never seen anyone report on here, or on reddit, or anywhere else, that they have actually had a security breach as a result of this.  Anybody else seen anything?  I am not saying that means it cannot happen, I’m just curious.

    This is never going to change, IMO, whether that’s right or wrong, or can’t or won’t.  I suspect it is can’t not won’t, but I don’t have the technical expertise to form an opinion.  I just don’t know why Sonos would not have done this if they could, and if they really believed it was critical.  Out of their own selfish interest, if for no other reason.

      Outburst
      Enthusiast II
      June 16, 2022

      It simply isn’t gonna happen, it’s S1, it’s “dead”.

      You’re probably correct… “liars gonna’ lie” as they say.  The voting patterns here suggest this forum has a majority population of Sonos supporters, and I’ll guess you’re one. That’s fine - I used to be one. I think the biggest difference between us on this subject is that I won’t continue to pay Sonos for abuse. I can’t control Sonos, but I do control who I spend $ with, and what I tell others about “the Sonos experience”  :)

      I’m not a supporter, I’m simply realistic. It happens all the time that tech gets dropped and for these old devices I can’t even blame anyone. I mean the players still work as they did on day one (with loads of added features over time) so I don’t see any abuse or whatever here. You just don’t get new features which I think is ok as long as the players continue to work. 

        Stanley_4
        Stanley_4
        Grand Maestro
        June 16, 2022

         

        Sonos has at least two options to correct this misbehavior. One of them is without expense - the “No cost to Sonos option”. The other one is to update their software and firmware like an honest and responsible business should do.

        1. Release the firmware - post it on GitHub (etc), under the same license terms as they got for the Linux kernel they used. (That they haven’t done this years ago may be a violation of their license for the kernel code).
        2. Fix this insecure software. Sonos could yet salvage some of their reputation as a fair and honest company.

        Sonos has released a lot of their software as is required by the GPL License it carries. You can download it from their open source pages.

        If you can get the kernel to compile, with SMB 3 support active, and fit the memory footprint of the S1 devices, I’m sure they would be willing to pay you well for a copy of your code.

        FamousSeamus
        Lyricist II
        June 17, 2022

         

        Sonos has at least two options to correct this misbehavior. One of them is without expense - the “No cost to Sonos option”. The other one is to update their software and firmware like an honest and responsible business should do.

        1. Release the firmware - post it on GitHub (etc), under the same license terms as they got for the Linux kernel they used. (That they haven’t done this years ago may be a violation of their license for the kernel code).
        2. Fix this insecure software. Sonos could yet salvage some of their reputation as a fair and honest company.

        Sonos has released a lot of their software as is required by the GPL License it carries. You can download it from their open source pages.

        If you can get the kernel to compile, with SMB 3 support active, and fit the memory footprint of the S1 devices, I’m sure they would be willing to pay you well for a copy of your code.

        Ha ha ha… you’re “sure”… Just how sure are you?

         

        beynym
        World-Class Superstar
        June 17, 2022

        Ha ha ha… you’re “sure”… Just how sure are you?

         

        I'm pretty sure that for some it's hard to accept reality.

        Terms & ConditionsAccessibility statement