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?
We’ll need some details. Describe your network for us (include model numbers). Which SONOS models do you own? Which controllers are you using? Are the SONOS units wired to the network? What error messages?
Sorry- Sonos are not wired. The online only gives the option to add to a new system, not to set up a new system. When the Sonos is wired to either the Tmobile router directly or to eros, the product can never be located
In addition to the Tmobile router you have an Eero mesh system?
Either Eero or T-Mobile must be “Bridged”. Otherwise you’ll have two routers fighting for control — the user loses.
+6Either Eero or T-Mobile must be “Bridged”. Otherwise you’ll have two routers fighting for control — the user loses.
Last I checked, T-Mobile doesn’t support bridge mode consumers. Small business customers get a different gateway that offers more options, including a bridge mode. Have things changed?
I’m not a T-mobile user. 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.
+6I’m not a T-mobile user. 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.
Yes, and as you said make sure to put the Eero into access point mode.
You want the Eero that is wired to T-Mobil to be in router mode. Don’t Bridge Eero.
+6You 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.
If you are concerned about double NAT you’ll need to bridge Eero.
+6If 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.
As long as SONOS and the controllers are on the same subnet, the SONOS system should work.
+14As long as SONOS and the controllers are on the same subnet, the SONOS system should work.
Totally correct
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.
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.