NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
Orbi RBK753 has chucked my Airplay speakers off the network after firmware update
Orbi AX4200 WiFi 6 High-Performance Router (RBR750). (It doesn't fill me with confidence that this community forum doesn't have my Orbi model available in the selection field above. But heh ho.) ...
The speakers connected to the AVM once it was changed to the same SSID and password as the Orbi, and then would not connect to the Orbi. Nice try 🙂
So I printed off every single setting and did a full factory reset of the Orbi network. I then reconfigured it just as I had done before, and found myself saying "A-HA!"
Now I don't know exactly when I changed Orbi to WPA3? Was it a day before or after the firmware update? Not more than that surely. Seemed harmless, or the right thing to do in fact, but could this be the culprit rather than the firmware update?
So I got everything back exactly as before but with WPA2, crossed my fingers, and before I went to check the speakers I heard their little chime indicated wi-fi connection was established! 🎉
I went to check KEF.com and found they do not recommend open networks or WEP (no surprise there!) And they add: "The WPA2 security protocol is recommended." Note, KEF does not say: "The speakers are not compatible with more recent security protocols such as the three years old WPA3."
But if the effect is indeed related to the cause here, it would seem that KEF should indeed include that sentence in its documentation, or even better, get their kit compatible with WPA3. I will point them to this thread.
Thanks Mikey94025 and thank you FURRYe38, and thank you [at]netgear on Twitter.
psheld wrote:
I found the RTS / CTS page via the menu as you describe, but I cannot see a way to change the associated numbers. See the screenshot here.
You can change the RTS/CTS numbers by typing in the text box to the right of the screenshot you posted and then press the Apply button at the very top. Try using a desktop browser with orbilogin.com or put your phone in landscape mode.
Thanks Mikey94025. It seems my mobile browser didn't offer me a horizontal scrollbar 😂
Saying that, you'd think in this day and age that the webpage served by the router would be responsive. But let's get back to fixing my faulty Orbi ...
I applied the change of CTS/RTS from 64 to 2347 as you can see here:
Unfortunately, this has made no difference. I still cannot rejoin my speakers to the network the AirPlay way or the KEF way ☹️
Still, I appear to have attracted Netgear's attention via Twitter, so hopefully we'll have their input here soon enough. I'm out of ideas (not that I had many to begin with! 😆) If neither Netgear nor the community here can find a fix this week, I'm returning the system under warranty as not fit for purpose. Fingers crossed it won't come to that.
Thanks again, Philip.
You don't happen to have a separate or prior wifi router hanging around do you?
The AVM modem I listed earlier in this thread is also a wifi router.
I suspect FURRYe38 that you may want me to try adding the speakers to it, and I can confirm already that this works no problem with both methods — the AirPlay way and the KEF app way.
To state the obvious, but for the record, that's not an ongoing / workable solution here because the speakers are not normally in range of the AVM, hence our investment in the Orbi. And our smartphones (through which we interact with the speakers) are on the Orbi network.Can you set up the other wifi router for same SSID name and password that's on the Orbi system, long enough to get the speaker devices connected to it. Once the speakers are fully connected, turn OFF the 2nd router and see if the speakers migrated and connect to the Orbi wifi...
