Skip to main content
welshmanofsteel
Contributor I
March 5, 2021

The dinosaur SONOS refuses to connect to cutting edge NAS

  • March 5, 2021
  • 18 replies
  • 961 views

I have  searched the various  posts gogin back to 2017. 

Current SONOS app is unable to connect to True NAS.

Steps taken to remove the problem

  1. Set up dedicated user on TrueNas for sonos
  2. enabled SMB1 CIF server on WIndows 10
  3. Removed SMB2/3 on freeNas (and then reinstated)
  4. Given full permissions on the  mount pint (Plex) via True NAS ACL

Steps I will not be taking

  1. Reinstalling windows
  2. Creating a “sonos” user on windows

If anyone has experienced similar issues and has a working solution based on the facts above  I would be glad to hear it. 

Please do not ask a plethroa of “fact finding” questions  about other services /users connecting to the TrueNAs mount point /datapool - they can. This is a SONOS specific issue which the tech guys consider is beneath their attention.

 

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.

18 replies

Show previous replies
Stanley_4
Stanley_4
Grand Maestro
March 15, 2021

There is a lot of good discussion on why not a newer SMB in some of the older topics, I believe that was even a bit from one of the Samba developers.

Short answer the newer Samba is bigger, the newer Samba needs a newer Linux kernel that is bigger, the S1 generation of Sonos gear is out of memory and they have to remove features to add anything new/bigger.

amun
March 15, 2021

There is a lot of good discussion on why not a newer SMB in some of the older topics, I believe that was even a bit from one of the Samba developers.

Short answer the newer Samba is bigger, the newer Samba needs a newer Linux kernel that is bigger, the S1 generation of Sonos gear is out of memory and they have to remove features to add anything new/bigger.

And their excuse for not fixing it (and the 64k and store limits) in S2 is?…...

Stanley_4
Stanley_4
Grand Maestro
March 16, 2021

Time, money, skilled Linux kernel programmers and customer interest in the fix. All coming back to profit of course.

Why would Sonos spend a big chunk of money and developer time fixing something that users that really care can fix for under $50 and 30 minutes of their time?

I don’t even think Sonos could break even offering a Boost looking device (to save case design costs) that would either provide a SMB v1 NAS capability or a gateway to a NAS running other more secure protocols. That based on unofficial chats with Sonos folks when discussing the idea.

I even looked into offering such a device myself and I just couldn’t see enough market for it to be worth the effort.

You might consider that if you think it would sell. Grab a Pi Zero W (wireless) Pi 3 (wired) or a Pi 3b+ or 4 for both. Get a 8 GB SD card, a quality power supply and just follow my directions for a Gateway. Add an external USB port for a hard drive if you want the NAS version. Plenty of Sonos forums and other sites out there to sell on. You could even get someone to post a customer review of it here (but not sell it) for publicity.

Kumar
March 16, 2021

@Stanley_4 :But what would be the advantage to @amun by doing all this over what he has in place today for listening to his owned music on Sonos?

amun
March 16, 2021

@Stanley_4 :But what would be the advantage to @amun by doing all this over what he has in place today for listening to his owned music on Sonos?

Exactly - if I was going to change anything, it would be to the casting approach, which also solves the 65k limit, the store limit and restrictions on file type (e.g. hi-res files played natively). It would also mean that my reliance on my aging ZP90 would be eliminated, as my AV receiver has Chromecast built in.

As I said, for my purposes Sonos is looking distinctly lacking these days...

Stanley_4
Stanley_4
Grand Maestro
March 16, 2021

I do not want the SMB v1 security issues on my main NAS! Using a secondary NAS or NAS to SMBv1 gateway eliminates that need and risk.

Been years since I messed with Plex and I preferred the Sonos music library option back then, haven’t looked lately.

amun
March 16, 2021

I do not want the SMB v1 security issues on my main NAS! Using a secondary NAS or NAS to SMBv1 gateway eliminates that need and risk.

Quite… That’s why I use a sacrificial NAS for Sonos. My main NAS doesn’t have SMB1 enabled.

    mrjk
    Lyricist I
    April 15, 2021

    If anyone has experienced similar issues and has a working solution based on the facts above  I would be glad to hear it. 

    There are plenty of examples on here of reducing to SMB1, repurposing raspberry pis/ having a second NAS or operating one as a bridge, but they weren’t appealing to me either.

    I have exposed my music dataset to a jail on my Truenas box (read-only) and configured the jail with a SMB1 share for the exclusive use of the sonos user. It’s a 10 minute one-time fix and having it in the same box feels like less hassle to me than maintaining another rpi.

      Terms & ConditionsAccessibility statement