NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
RBR850 / RBS850 Firmware Version 3.2.15.32 - Hot Fix-Firmware Update
Addresses security issues-get it here: https://kb.netgear.com/000062077/RBR850-RBS850-Firmware-Version-3-2-15-32-Hot-Fix FURRYe38
Yes, I had to reset it because it was causing my Skype video to lag. Used chrome, Firefox, and edge same result.
Very odd. Is the system working ok?
Only thing I can think of is to downgrade back to v11, then re-up-load the v32 file again. I would besure to download the v32 file again from NG download page.
Somenthing that i'm posting to let users know that NG now recommends using the default CTS value of 64 on Orbi AX. I was informed by NG that orbi AX that there are settings and or drivers in the FW that are effected by any CTS changes and they feel that 2347 may cause problems for some. I can attest to this as my 3rd gen NEST would not keep connected to Orbi AX if I set the CTS value to 2347 which does work on other AC model routers. After changing back to 64, the NEST has been connected with out any problems. Over all my Orbi AX on v32 has been up and online and stable with the default CTS value.
So seems the Orbi AX maybe different from all the others in regards to CTS value and usage so even though 2347 works for most other system, Orbi AX seems to be the odd one out for this setting.
I recommend that users first try the default CTS value. If you run into problems first try a factory reset if one hasn't been performed. You can try 2347 and use it if seems to help. Though I would suggest that users having problems with CTS value of 64 please report your problem to NG and let them know so they can review and make changes if they can.
Hope this helps.
I am changing mine from 2347 to 64 -- even though I have had no issues with my AX6000 and attached devices... but want to see if I can observe any differences in overall behavior.
Anything in particular I should keep an eye out for?
Thanks for heads up.
Other than this, no. v32 seems stable while using CTS defaults. I just changed to 40Mhz only channel width as well today and NEST is still connected. No other problems seen thus far.
FURRYe38 wrote:Somenthing that i'm posting to let users know that NG now recommends using the default CTS value of 64 on Orbi AX. I was informed by NG that orbi AX that there are settings and or drivers in the FW that are effected by any CTS changes and they feel that 2347 may cause problems for some. I can attest to this as my 3rd gen NEST would not keep connected to Orbi AX if I set the CTS value to 2347 which does work on other AC model routers. After changing back to 64, the NEST has been connected with out any problems. Over all my Orbi AX on v32 has been up and online and stable with the default CTS value.
So seems the Orbi AX maybe different from all the others in regards to CTS value and usage so even though 2347 works for most other system, Orbi AX seems to be the odd one out for this setting.
I recommend that users first try the default CTS value. If you run into problems first try a factory reset if one hasn't been performed. You can try 2347 and use it if seems to help. Though I would suggest that users having problems with CTS value of 64 please report your problem to NG and let them know so they can review and make changes if they can.
Hope this helps.
I was a value of 500 which seemed to be working fine but then noticed I couldn't get the kids' school supplied Chromebooks (Lenovo) to connect to the Wi-Fi. A quick search yielded this post:
When I changed my CTS value from 500 to 2347, the Chromebooks were able to connect fine, so I left it at 2347.
So what now? Do I change it to 64 because NG says it's the optimal setting for AX?
So do the chrome books not connect with CTS set to 64?
Something to let NG know if about they don't.
dtay wrote:
I was a value of 500 which seemed to be working fine but then noticed I couldn't get the kids' school supplied Chromebooks (Lenovo) to connect to the Wi-Fi. A quick search yielded this post:When I changed my CTS value from 500 to 2347, the Chromebooks were able to connect fine, so I left it at 2347.
So what now? Do I change it to 64 because NG says it's the optimal setting for AX?
