Skip to main content

Still cannot build the local music library. It always times out with an error that the share (which it has been working on for the previous 45 minutes) is suddenly no longer available, or that it may have been moved or powered off, which of course is not true. 

Tier-1 help desk suggested that I have a double NAT issue. I have a Verizon router with two extenders, and by design, the extenders broadcast the same SSID as the router, and the tech said that was the problem. 

My understanding of a double NAT is that you have two or more devices providing network address translation for outgoing requests, and one way to detect it was through traceroute:

traceroute google.com
traceroute to google.com (142.251.40.238), 64 hops max, 40 byte packets
 1  cr1000a (192.168.1.1)  3.594 ms  3.011 ms  2.882 ms
 2  lo0-100.washdc-vfttp-366.verizon-gni.net (71.178.216.1)  17.840 ms  9.364 ms  19.354 ms
 3  * * *

A double NAT would show a private IP as the first two hops, but here there is clearly only one. 

Could duplicate SSID names cause a problem? And why would SSIDs or double NATs cause a local music library rebuild to fail? 

 

Extenders or Mesh APs? Big difference.

Sonos is really picky about one network / LAN segment, and not having stuff they are using filtered out.

Maybe wire the NAS to the root router and connect a Controller directly to it?

Extenders or Mesh APs? Big difference.

Sonos is really picky about one network / LAN segment, and not having stuff they are using filtered out.

Maybe wire the NAS to the root router and connect a Controller directly to it?

Extenders, from Verizon. But the extenders are in a different part of the house, in the basement and on the first floor, and they themselves are wired in. 

As for wiring in the NAS … I tried that -- it’s not a NAS but an older MacBook with all the music files, and it was hard-wired by ethernet to the router. Same nonsense. I don’t see any evidence of the MacBook trying to ping the extenders when the router is sitting about four feet away. 

When the music library update is running, what address space does that run in? I assume it’s on one of the Sonos devices, right? 

 

One of the Sonos, I think the code is smart enough to move it to one of the more capable / higher memory devices.

Maybe shut a few things off to simplify your situation and see what works?

Long Ethernet is cheap, I have several 50’ and a 100’ handy so when I get fed up I can hardwire stuff. Recently that hasn’t been my Sonos, but my solar power system. Still handy to have and an easy work-around to solving (known issue, not cheap to fix) the problem.

Get rid of the extenders (Sonos officially do not support them) and get a real mesh system. Sonos isn’t going to be happy with random SSIDs/subnets scattered through your IP space.

Thanks for the replies everyone. 

I was able to solve this problem over the weekend -- well, no so much “solve” as “make it go away.” I long suspected the issue to be some kind of timeout while trying to digest my music library. I had a couple of folders that had 600-700 music files in them, with a scattering of different albums. 

When I split it up on the basis of album, the scan completed. The largest folder has no more than 60 members. Sonos is happy. 

In the end, it had nothing to do with ethernet vs. wifi, extenders, double NATs, duplicate SSIDs, or anything like that. I am constrained in how much I can tinker with the home network so thankfully I didn’t need to redo any of that. 

Thanks to everyone who replied. 

Reply


Terms & ConditionsCookie settings