I recently replaced my home router with a Asus RT AX88U router. After setting up my router using the same wifi name and password, I started my Sonos app. All my speakers were recognized and connected. The only component that would not reconnect was the Sonos boost. I tried a factory reset and the boost went through its startup, led flashing white / orange, then changed to a slow flashing green. The boost will on connect and I am at a loss. Thanks in advance for any help.
Andrew
Could the router have some kind of port-based VLANs enabled? It would worth checking. If the segments are on different VLANs this will obviously block traffic between segments.
Worth checking. Thank you sir
Is the router running stock firmware or a third party firmware?
This Asus router does not support any VLANs
One last check. Note the Move’s IP address on 2.4GHz (in Settings/System/About if you can’t get it elsewhere), and the Boost’s IP when accessed from the 5GHz segment. They should match in the first 3 octets, i.e. A.B.C.X and A.B.C.Y.
The only “difference” between the Canadian/US Moves is the power cord it ships with. Otherwise, they’re exactly the same.
Hi
I use Asus routers as well. Although it has nothing to do with the Boost the following may be causing connection issues. Although not recommended you may have to dispense with WPA3 altogether 
WPA3 is the latest standard for Wi-Fi encryption. This is separate from Wi-Fi 6 / 802.11ax, but in practice the same products will often be first or early to implement both.
If some devices experience problems connecting to the Wi-Fi 6 network, the problem may be in missing WPA3 support or the "WPA3/WPA2 mixed mode" feature. Mixed mode is intended to ensure that older clients can still connect, but in practice there are some clients who do not recognize this setting and refuse to connect at all.
Such problems are likely to apply to a number of older products, but reports we have received so far suggest that it applies at least to the following:
As WP3 is much safer than WPA2, we do not recommend downgrading the security of WPA2 to let older clients connect.
* More info on the subject here: https://eyenetworks.no/en/wifi-6-compatibility/
Just to add these Sonos products support WPA3…
Have you tried connecting Sonos to the Asus with a cheap Ethernet switch? I just bought a Netgear Nighthawk and saw my whole Sonos network disappear. I googled the issue and one recommendation was to buy a simple ethernet switch and put it between the Nighthawk and the Bridge.
I got a «Findway 2 Ports Network Switch Splitter Selector Hub 2-in 1-Out or 1-in 2-Out 100M MT-RJ45-2M» for $7 from Amazon, plugged it in and my whole Sonos system came back immediately. I have to add that thirty minutes later it seems to work much better with this more powerful and modern router.
It seems, based on earlier posts, that there is some firewall incompatibility or IP address limitation with some WiFi 6 routers and luckily a workable, very slightly clunky solution. Maybe it works similarly with Asus.
That’s not a Ethernet switch it’s a physical splitter, connecting one or other device at a time. If it solved a Spanning Tree problem caused by wiring two Sonos devices to the Nighthawk it did so by disconnecting one or other Sonos device entirely from the wired network.
Sorry, but it’s a total red herring in terms of the OP’s current problems.
Just to add these Sonos products support WPA3…
Not that it makes a difference in this case, as the OP is trying to make his wired/SonosNet system discoverable.
I still suspect the router of not handling discovery broadcasts correctly.
Have you tried connecting Sonos to the Asus with a cheap Ethernet switch? I just bought a Netgear Nighthawk and saw my whole Sonos network disappear. I googled the issue and one recommendation was to buy a simple ethernet switch and put it between the Nighthawk and the Bridge.
I got a «Findway 2 Ports Network Switch Splitter Selector Hub 2-in 1-Out or 1-in 2-Out 100M MT-RJ45-2M» for $7 from Amazon, plugged it in and my whole Sonos system came back immediately. I have to add that thirty minutes later it seems to work much better with this more powerful and modern router.
It seems, based on earlier posts, that there is some firewall incompatibility or IP address limitation with some WiFi 6 routers and luckily a workable, very slightly clunky solution. Maybe it works similarly with Asus.
That’s not a Ethernet switch it’s a physical splitter, connecting one or other device at a time. If it solved a Spanning Tree problem caused by wiring two Sonos devices to the Nighthawk it did so by disconnecting one or other Sonos device entirely from the wired network.
Sorry, but it’s a total red herring in terms of the OP’s current problems.
That’s not accurate, there is and always was only one Sonos device wired to the network and that’s the Boost. Everything else is wireless and works. I never tried wiring two Sonos products to the Nighthawk.
Have you tried connecting Sonos to the Asus with a cheap Ethernet switch? I just bought a Netgear Nighthawk and saw my whole Sonos network disappear. I googled the issue and one recommendation was to buy a simple ethernet switch and put it between the Nighthawk and the Bridge.
I got a «Findway 2 Ports Network Switch Splitter Selector Hub 2-in 1-Out or 1-in 2-Out 100M MT-RJ45-2M» for $7 from Amazon, plugged it in and my whole Sonos system came back immediately. I have to add that thirty minutes later it seems to work much better with this more powerful and modern router.
It seems, based on earlier posts, that there is some firewall incompatibility or IP address limitation with some WiFi 6 routers and luckily a workable, very slightly clunky solution. Maybe it works similarly with Asus.
That’s not a Ethernet switch it’s a physical splitter, connecting one or other device at a time. If it solved a Spanning Tree problem caused by wiring two Sonos devices to the Nighthawk it did so by disconnecting one or other Sonos device entirely from the wired network.
Sorry, but it’s a total red herring in terms of the OP’s current problems.
That’s not accurate, there is and always was only one Sonos device wired to the network and that’s the Boost. Everything else is wireless and works. I never tried wiring two Sonos products to the Nighthawk.
The fact is that the type of A/B splitter you referenced is a totally passive, straight-through device. I have several. What it isn’t is an Ethernet switch.
I also can’t imagine why your Sonos disconnected when wired to the Nighthawk, unless there was something defective. I have Sonos wired to a Nighthawk R7000 and have done for years.
Have you tried connecting Sonos to the Asus with a cheap Ethernet switch? I just bought a Netgear Nighthawk and saw my whole Sonos network disappear. […]
That’s not a Ethernet switch it’s a physical splitter, connecting one or other device at a time. If it solved a Spanning Tree problem caused by wiring two Sonos devices to the Nighthawk it did so by disconnecting one or other Sonos device entirely from the wired network.
Sorry, but it’s a total red herring in terms of the OP’s current problems.
That’s not accurate, there is and always was only one Sonos device wired to the network and that’s the Boost. Everything else is wireless and works. I never tried wiring two Sonos products to the Nighthawk.
The fact is that the type of A/B splitter you referenced is a totally passive, straight-through device. I have several. What it isn’t is an Ethernet switch.
I also can’t imagine why your Sonos disconnected when wired to the Nighthawk, unless there was something defective. I have Sonos wired to a Nighthawk R7000 and have done for years.
It did not work without the switch, now it does. It might be black magic but I now have my $7 solution. If it breaks down I will report.
Just to add these Sonos products support WPA3…
Not that it makes a difference in this case, as the OP is trying to make his wired/SonosNet system discoverable.
I still suspect the router of not handling discovery broadcasts correctly.
Yes, I think the same too …and either there’s a setting somewhere on the Asus router to allow the multicast broadcast to all segments of the LAN, or it’s something that Asus needs to address with their firmware.
I don’t understand this one either. I have 3 Asus routers setup as an Asus AiMesh with an Ethernet Backhaul. Sonos is on the SonosNet via Boost Module. Sonos has 30 clients including Roam and Move both x 2. No issues.
I didn’t notice and I may have missed it …but has the OP checked for updates for his router?
Good morning everyone.
I thought I would provide an update. This morning I accessed my sonos system with my controller connected to my 5G network. Low and behold, all my components were visible and working! I then thought I would try things on my 2.4 network. Surprisingly all components were visible and working on that network as well.
Unbelievable, this is a first for me in the 3 years I have owned Sonos everything has worked on both networks at the same time. Lets hope these connections are maintained in the days to come.
Thanks again for all the input.
Did your router firmware update itself?
Not that I am aware of. I did do all the updates prior to configuring and turning up of my systems when I started the installation two days ago.
This week my Beam would not connect to my Asus RT-AX88U router.
I have previously tried the enable then disable Airtime Fairness trick on both 2,4 GHz and 5 GHz, but my Beam would still not connect to my router.
What did help was changing the following option under Wirless → Professional, under 2,4 GHz radio. My Modulation Scheme was set to “Up to MCS 11 (NitroQAM/1024-QAM)”, I selected instead “Up to MCS 9 (TurboQAM/256-QAM)”.
Power cycled all my Sonos gear (Beam, Sub and 2 x One), and they connected back to the router and rejoined my surround setup.
Enter your username or e-mail address. We'll send you an e-mail with instructions to reset your password.
