Skip to main content
Contributor I
June 16, 2024
Question

Sonos will not connect to new router

  • June 16, 2024
  • 16 replies
  • 224 views

Sonos recently demonstrated quite the mind of its own, running 2 different tracks on two parts of the system, concurrently, and repeatedly switching from the desired product to another. All annoying but when a new router was required the system would not connect. Even sound professionals have not been able to connect. The average wait time when I call customer service? 84 minutes.

Is anyone having better luck?

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.

16 replies

buzz
Grand Maestro
June 20, 2024

You want the Eero that is wired to T-Mobil to be in router mode. Don’t Bridge Eero.

AlexPermit
Prodigy I
June 20, 2024

You want the Eero that is wired to T-Mobil to be in router mode. Don’t Bridge Eero.

But if the T-mobile router can’t be put in bridge mode, won’t that result in double-nat?

I thought that was your concern when you advised

Either Eero or T-Mobile must be “Bridged”. Otherwise you’ll have two routers fighting for control  — the user loses.

 

buzz
Grand Maestro
June 21, 2024

If you are concerned about double NAT you’ll need to bridge Eero.

AlexPermit
Prodigy I
June 22, 2024

If you are concerned about double NAT you’ll need to bridge Eero.

I would think that would be better.  If you don't bridge the Eero and

Make only one network connection between T-mobile and Eero, then ignore T-mobile’s WiFi. Don’t wire any SONOS units to Eero access points, wire only to the main unit.

Then the Sonos units would be on one Lan (behind the T mobile router) and the wifi (and Sonos app) would be on another Lan (behind the Eero router).  I'm not sure that how that would even work.

buzz
Grand Maestro
June 22, 2024

As long as SONOS and the controllers are on the same subnet, the SONOS system should work.

press250
Prodigy III
June 22, 2024

As long as SONOS and the controllers are on the same subnet, the SONOS system should work.

Totally correct @buzz, tho’ I’ll add a rare exception for the benefit of folks thinking about advanced network topologies.

Sonos uses mDNS for device discovery and that protocol is not routable. If you put a ROUTER (and here I mean a box that performs the technical routing function, not a box like a Wi-Fi router with a switch built in) between network segments, odds are extremely high that mDNS will not work even if the two network segments are the same subnet. And if mDNS does not work, Sonos does not work.

Lest there be any doubt, I speak from (semi-painful) experience on this.