NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
RBK20/22 Owners - Do not upgrade to V2.3.0.28
Firmware V2.3.0.28 has issue with connecting devices to sattelite. All devices will stay connected to the router. Had to revert back to firmware V2.2.1.210.
UPDATE:
Moving the 2.4GHZ from busy channel 1 to channel 11 resolved the issue, now I have half of my 18 devices connecting via the satellite as it use to before. I never bother to do a factory reset but if I did in this case, it will probably auto chose the less busy channel and the problem will also be solved.
Sounds like you found the problem. Yes busy surroudings can cause problems. Why manual channel selection is good as well.
Try setting manual channel 1, 6 or 11 on 2.4Ghz and any unused channel on 5Ghz.
Glad it's not the FW.
Enjoy. :smileywink:
RGOLD wrote:
UPDATE:
Moving the 2.4GHZ from busy channel 1 to channel 11 resolved the issue, now I have half of my 18 devices connecting via the satellite as it use to before. I never bother to do a factory reset but if I did in this case, it will probably auto chose the less busy channel and the problem will also be solved.
Just to say my 43 when manually updated to this firmware had a number of settings reset. Firstly for WIFI my previous manually set 2.4 channel was reset to auto and secondly fast roaming was reset to off. Daisy chain was also reset to on.
This choice (undocumented) to reset certain saved parameters will no doubt causes a number of these type of issues across the less tech savvy part of the installed base.
I would do a factory reset on the entire system after the update. Setup from scratch. After it's all set up, do a save config to file under Advanced Tab/Advanced Settings/Backup. Keep this save config file for future use.
Bullyterrier wrote:
Just to say my 43 when manually updated to this firmware had a number of settings reset. Firstly for WIFI my previous manually set 2.4 channel was reset to auto and secondly fast roaming was reset to off. Daisy chain was also reset to on.
This choice (undocumented) to reset certain saved parameters will no doubt causes a number of these type of issues across the less tech savvy part of the installed base.