Skip to main content
PiperKev
Contributor I
March 4, 2024
Answered

Unable to access samba share after SONOS update

  • March 4, 2024
  • 15 replies
  • 961 views

My Music Library is shared both from my wife’s Win 10 laptop and my Linux laptop (running Linux Mint 21.3), which shares my Music folder via samba.  After the SONOS update to 16.0, my system doesn’t recognize the Music folder on my Linux laptop, and I can’t re-add it to the library.  Nothing was changed on my laptop, only the SONOS software update.  I can see the Music folder on my laptop using File Manager on my wife’s laptop, so I know it’s sharing properly on our home network. I’ve added these lines to smb.conf as I’ve read in various SONOS support threads, but no joy:

[global]

server min protocol = NT1
unix extensions = no
ntlm auth = yes

Has anyone else experienced this issue after updating?  And has anyone found a solution?

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 Corry P

Hi @PiperKev 

I think the update was probably more correlation than causation - otherwise, we’d be seeing a lot more reports of it going wrong for others too, including me.

Did you restart the Samba service after changing the smb.conf file? The service would need to be restarted for the changes to take effect. Given that the Linux share worked with Sonos before, however, I’m thinking that the configuration of the server isn’t where things are going wrong.

If you haven’t tried already, I recommend rebooting all devices that are involved - the Linux server, your speakers (and Boost) and your router (power off the router for at least 30 seconds). It’s a little bit of a long-shot, but always worth trying.

Do you get any error numbers in the app? If not, there will be errors being logged nonetheless - I recommend you get in touch with our technical support team who have tools at their disposal that will allow them to give you advice specific to your Sonos system and what it reports, if all else fails.

I hope this helps.

 

15 replies

Show previous replies
PiperKevAuthor
Contributor I
March 5, 2024

Thanks, @Corry P , but I’m about ready to give up at this point.  I tried adding my laptop to the Music Library with my internal IP address, but I get the same result as when I try using my hostname.  I guess I’ll have to live with half of a library from now on...  

PiperKevAuthor
Contributor I
March 6, 2024

My router is my own Linksys EA6350, but the modem is Spectrum provided.  I actually replaced the modem today, but nothing changed.

controlav
controlav
Lead Maestro
March 6, 2024

You could always upload your collection to iBroadcast.com - they have a decent Sonos integration and basic version is free.

Author of the leading independent Sonos apps for Android, MacOS, iOS, Windows and Xbox.
    PiperKevAuthor
    Contributor I
    March 6, 2024

    You could always upload your collection to iBroadcast.com - they have a decent Sonos integration and basic version is free.

    That's a GREAT workaround, @controlav!  Thank you for the tip!!

    Stanley_4
    Stanley_4
    Grand Maestro
    March 6, 2024

    For now best to avoid possibly conflicting network names, .home.arpa is the RFC suggested option for now but there is hope that .internal will clear the processes and become available too.

     

    So my computer is hp-800.home.arpa which seems to avoid my ISP’s “evil” ministrations.

    Terms & ConditionsAccessibility statement