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.
Firmware 2.2.1.210: 6 devices will connect to Sattelite 5 - 10 minutes after reboot. laptop will connect when moving closer to the sattelite.
Firmware 2.3.0.28: Only 1 device will connect to Sattelite 30 minutes after reboot the rest will stay connected to the router. Moving my laptop close to the sattelite will not make any diffrence, it will stay connected to the router eventough the router signal is weaker.
The only reason I decided to upgrade from 2.2.1.210 is the DHCP issue where I get 2 devices with same IP address...
RGOLD wrote:
Firmware 2.2.1.210: 6 devices will connect to Sattelite 5 - 10 minutes after reboot. laptop will connect when moving closer to the sattelite.
Firmware 2.3.0.28: Only 1 device will connect to Sattelite 30 minutes after reboot the rest will stay connected to the router. Moving my laptop close to the sattelite will not make any diffrence, it will stay connected to the router eventough the router signal is weaker.
The only reason I decided to upgrade from 2.2.1.210 is the DHCP issue where I get 2 devices with same IP address...
Do you have the Fast Roaming setting turned on? If not, try enabling it. I have seen my devices switch to the satellites easier with this setting enabled.
Also, I only factory reset if absolutely necessary. There is no reason to do a factory reset with every FW update. Use that as a last resort, in my opinion. Not worth the time to set everything back up from scratch.
One more thing, and this may not be directly related to your current issue, but have you scanned the available channels and set your Orb system to use the most optimal channels (for both 5GHz and 2.4GHz) for your environment? I have noticed that depending where I am standing in my home, there are different channels available/taken because the neighbors on either side and in back are clogging the spectrum. It might be that the channel you have selected is clear for where the router is placed, but is congested where the satelite is located. This could possibly be why your devices are "sticking" to one orbi unit vs another. I don't really know what your setup is, but take a look if this could be something that might need tweaking. I had to play around before I found the right channels.
I some cases factory reset is needed. Especially in with new FW updates when problems are seen. Supposed "data corruption" was seen in recent v210 going from prior version of FW. Some loaded it and had problems. After a reset and setup again, problems were resolved.
FURRYe38 wrote:
I some cases factory reset is needed. Especially in with new FW updates when problems are seen.
That comment was not really necessary. You didn't need to drive home your point because someone disagreed with you.
As I said, it is my opinion. Speaking from my own experience with troubleshooting the many problems that have popped up over the time I have owned the Orbi system, a factory reset is not necessary in almost all cases. Easier troubleshooting can be done by understanding what the settings are, and how they work, as well as how each of the units themselves function. In fact, a product that required a factory reset every time there was an update that had a minor problem would not be a product worth buying. That is bad business practice to make a consumer constantly reset the device. Orbi is not such a product, and there are several different ways to get this system up and running smoothly without a factory reset.
You can continue to give the factory reset advice if you want. No one is stopping you from flooding the forum with the same two or three copy and paste questions and suggestions to all the various problems out there, but you should accept that others have a different opinion on the matter. We also have a desire to help those that may have similar problems to what we have experienced by providing them with our own tips and tricks.
Your behavior on this forum to constantly repost the same questions and advice over and over, and to hijack every post on this community forum, probably prevents those of us who can also help from participating in the discussion. This is one of the reasons why I am now rarely participating these days. It takes way too much time to constantly filter through your posts to get to the actual discussion. I'm sure there are others who feel the same way.
Same here, speaking from my opinion and personal experince is all. Don't take it wrong.
SeaMonkey80 wrote:
...........Also, I only factory reset if absolutely necessary. There is no reason to do a factory reset with every FW update. Use that as a last resort, in my opinion. Not worth the time to set everything back up from scratch.
.........
I agree that Orbi OS is now mature enough that factory resets should not be needed. Data corruption issues that usually require factory resets are not that common any longer.
SeaMonkey80 wrote:
Do you have the Fast Roaming setting turned on? If not, try enabling it. I have seen my devices switch to the satellites easier with this setting enabled.
..........
Fast Roaming (IEEE 802.11r) is more useful and improves roaming time when using WPA2 Enterprise Security (which is not supported in Orbi).
With WPA2 Personal Security (used in Orbi) Fast Roaming improves the process of establishing the new encryption key between the AP that the device is roaming to and the mobile device, which -somewhat- improves the roaming speed for devices supporting Fast Roaming, BUT having Fast Roaming enabled can cause packet drops for old devices that do not support Fast Roaming (IEEE 802.11r).
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.
