Sonos Connect 'Not Registered' and Not Joining System

Will the unit join the system if wired to your network?

Or is it possible this particular CONNECT was set up as a different Sx (S1 or S2) when it was set up at the other house, and subsequently reset? 

I have Quantum Fiber here but I do not use their pods, I also do not use there poor  imitation (rd6) version of native IPv6 that is problematical for several things I do. Their ipv4 connection, with my router, works well with Sonos. 

My first thing to try would be verifying the Quantum rd6 is disabled, you likely don't need it and will be happier with it off. If it was on,power down all Sonos, then all the pods. Power the pods back up, wait 2 minutes, power up your Sonos. This will,flush the old rd6 networking information.

As rd6 is an uncommon connection option today, an old 2007 hack, never really intended for anything other than early deployment playing/testing, pending a native IPv6 connection.

Sonos support needs to be warned if it is present as it often presents difficulties their tools may have problems diagnosing. Performance is also time dependent, the Quantum rd6 gateway gets swamped at busy times.

Basics.

https://networklessons.com/ipv6/ipv6-6rd-rapid-deployment

More details than you want.

https://datatracker.ietf.org/doc/html/rfc5569

https://datatracker.ietf.org/doc/rfc5969/

Will the unit join the system if wired to your network?

Thanks for the response. At this point, the unit will not join even if wired. The behavior appears identical to Wi-Fi. To muddy the waters further, I actually have not had success getting any of my Sonos products to connect to the system via ethernet. 

Or is it possible this particular CONNECT was set up as a different Sx (S1 or S2) when it was set up at the other house, and subsequently reset? 

I’m not 100% sure I follow. In both cases the systems were running the S2 app (mine, on which the Connect formerly worked, and my in-laws, the one on which it worked this week).

I have Quantum Fiber here but I do not use their pods, I also do not use there poor  imitation (rd6) version of native IPv6 that is problematical for several things I do. Their ipv4 connection, with my router, works well with Sonos. 

My first thing to try would be verifying the Quantum rd6 is disabled, you likely don't need it and will be happier with it off. If it was on,power down all Sonos, then all the pods. Power the pods back up, wait 2 minutes, power up your Sonos. This will,flush the old rd6 networking information.

As rd6 is an uncommon connection option today, an old 2007 hack, never really intended for anything other than early deployment playing/testing, pending a native IPv6 connection.

Sonos support needs to be warned if it is present as it often presents difficulties their tools may have problems diagnosing. Performance is also time dependent, the Quantum rd6 gateway gets swamped at busy times.

Basics.

https://networklessons.com/ipv6/ipv6-6rd-rapid-deployment

More details than you want.

https://datatracker.ietf.org/doc/html/rfc5569

https://datatracker.ietf.org/doc/rfc5969/

Thanks, Stanley! I will confirm that rd6 is disabled and report back. (I have also wondered whether replacing the pods with a third-party router might resolve this. Generally have had fine experience with Quantum, but with Sonos, even the app struggles to connect when I’m farther from the pods that the products are connected to.)

I already had my router and wifi setup when I switched to Quantum and a quick look at their documentation and on-line forums convinced me not to go that route. Skipped the pods, set my fiber box to transparent and let it reboot, plugged in my router and everything (but ipv6) worked perfectly once rebooted.

There are a lot of good routers, or for large/difficult homes mesh systems that work well with Sonos. 

Here’s what finally worked for me last month (same Quantum Fiber pods mess):

1. Plugged the Connect straight into the main 360 modem/router with Ethernet.
2. Fully signed out of the Sonos app on my phone, force-quit, toggled Wi-Fi off/on, signed back in.
3. Added the Connect while still wired — registered instantly.
4. Unplugged the cable and it’s been rock-solid on Wi-Fi ever since.

The pods were quietly blocking the registration traffic. Once it registers on the “real” router, it stays happy.

Give that a shot — 5 minutes and you’re probably done. Fingers crossed!

I already had my router and wifi setup when I switched to Quantum and a quick look at their documentation and on-line forums convinced me not to go that route. Skipped the pods, set my fiber box to transparent and let it reboot, plugged in my router and everything (but ipv6) worked perfectly once rebooted.

There are a lot of good routers, or for large/difficult homes mesh systems that work well with Sonos. 

Thanks, Stanley. I confirmed that rd6 was disabled, so that must not be the culprit this time. I may very well try this same approach as you if I can’t crack the code on the Connect. 

Here’s what finally worked for me last month (same Quantum Fiber pods mess):

1. Plugged the Connect straight into the main 360 modem/router with Ethernet.
2. Fully signed out of the Sonos app on my phone, force-quit, toggled Wi-Fi off/on, signed back in.
3. Added the Connect while still wired — registered instantly.
4. Unplugged the cable and it’s been rock-solid on Wi-Fi ever since.

The pods were quietly blocking the registration traffic. Once it registers on the “real” router, it stays happy.

Give that a shot — 5 minutes and you’re probably done. Fingers crossed!

Thanks very much, Avalynn! Unfortunately, these steps didn’t do the trick for me, but I really appreciate the advice. I have unplugged the pods that aren’t the primary router to simplify the troubleshooting. 

A few things I noticed while trying the above steps and then a few others:

• Unsuccessful in adding the Connect to the system via wired ethernet. The message at the end was “We are unable to find your Connect on your network. If your Connect is wired, make sure it’s plugged into your router correctly.” and “The connection to your Connect was lost. Make sure the Connect is powered on.”
• Successfully added the Connect to the system via Wi-Fi, but then started to run into the same Not Registered, “There was a problem checking for updates.”, and “There was a problem setting up your Connect. Our Customer Care team is ready to help.”
• In trying a few different things, I noticed that when I connect the Play:5 via ethernet, I can see it in the system on my laptop controller, but it shows as Not Connected in my iPhone app. These little bizarre discrepancies have made it challenging to keep track of what exactly is happening!

Thanks, all, for the help thus far!