NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Firmware update V2.6.2.104 - Internet Freeze, No Internet, Buffering, OFFLINE Status on App
I am having issues since the New Router firmware update. Hardware Version RBR20 Firmware Version V2.6.2.104 GUI Language Version V1.0.0.375 Operation Mode ...
Stevo533 wrote:I am having the same problem. Continuously cuts in and out and am unable to connect.
Perhaps you should revert your firmware
I too am having wi fi connection issues since upgrading the firmware to V2.6.2.104
The RBK 20 is connected to an EE router in AP mode and has run happily for over a year with three RBS20 satellites.
Since upgrading the firmware a couple of weeks ago one of the satellites appears occasionally to be fighting the other two so that anything in its vicinity gets no Internet. Moving away from it and nearer to a different satellite enables a good wifi/Internet connection to be made. Switching off the offending satellite when it's doing this also enables a solid connection to be made to wifi/Internet.
The fault is intermittent but once it's on it continues until the satellite is power cycled. Sometimes it will run OK for several days then it happens again.
As a radio engineer (without a 5GHz spectrum analyser of my own!) it feels as if the RF channel it's selecting might be interfering with the wanted one.
Nothing else has changed in the system, just the firware upgrade.
Any advice gratefull receieved. Thank you for reading.
What is the distance between the router and satellite(s)? 30 feet or more is recommended in between RBR and RBS to begin with
What channels are you using? Auto? Try setting manual channel 1, 6 or 11 on 2.4Ghz and any unused channel on 5Ghz.
Any Wifi Neighbors near by? If so, how many?
Is Daisy Chain enabled on the RBR?Has a power off for 1 minute then back ON with the ISP modem and Orbi system been performed since last update? A full on reset maybe needed as last resort.
One User Experience/Configuration:
https://community.netgear.com/t5/Orbi/Most-Stable-Orbi-Configuration/m-p/1941087/highlight/true#M97026
Thornemat wrote:I too am having wi fi connection issues since upgrading the firmware to V2.6.2.104
The RBK 20 is connected to an EE router in AP mode and has run happily for over a year with three RBS20 satellites.
Since upgrading the firmware a couple of weeks ago one of the satellites appears occasionally to be fighting the other two so that anything in its vicinity gets no Internet. Moving away from it and nearer to a different satellite enables a good wifi/Internet connection to be made. Switching off the offending satellite when it's doing this also enables a solid connection to be made to wifi/Internet.
The fault is intermittent but once it's on it continues until the satellite is power cycled. Sometimes it will run OK for several days then it happens again.
As a radio engineer (without a 5GHz spectrum analyser of my own!) it feels as if the RF channel it's selecting might be interfering with the wanted one.
Nothing else has changed in the system, just the firware upgrade.
Any advice gratefull receieved. Thank you for reading.
Updated my firmware as well just last week. When connecting to my Orbi RBR20 it's saying INTERNET NOT AVAILABLE when my Frontier Modem is actually working. Is there a solve to this? I've never had issue if firmware upgrade for years until this one. So frustrating.
What is the Mfr and model# of the Internet Service Providers modem/ONT the NG router is connected too?
Has a power off for 1 minute then back ON with the ISP modem and Orbi system been performed since last update?
mcvela007 wrote:Updated my firmware as well just last week. When connecting to my Orbi RBR20 it's saying INTERNET NOT AVAILABLE when my Frontier Modem is actually working. Is there a solve to this? I've never had issue if firmware upgrade for years until this one. So frustrating.
I'm having the same trouble as everyone else - RBR20 with two satellites, all was fairly stable, and then I upgraded to V2.6.2.104 a few days ago and it's been super flakey since then where devices report that they have a WiFi LAN connection but no internet. When it happens though, not all devices are unable to connect to the Internet usually - I can be working just fine on my laptop but my phone right next to me will suddenly start saying "no internet" even though it has an excellent wifi connection. And it's not just wifi devices - I see my wired Synology SAN which is absolutely rock solid also just reported that it's offline. I think there was some instability with the route/satellites though even prior to the firmware upgrade, for whatever that's worth.
Since the firmware update, I've disconnected both the router and the satellites from power and turned them each back on multiple times. I've done the same with the cable modem (MOTOROLA SB6141 SURFboard DOCSIS 3.0) and have had the cable company reset it remotely twice too for good measure. The problems persist.
I have just tried to disable the Traffic Meter since a) so many people here seem to be saying that is helping and b) the traffic meter results were all 0's anyway so it wasn't even working. Quick single data point result: my phone was saying no internet before I disabled Traffic Meter and currently is back online, so maybe that's the issue after all.
To the people who are saying you shouldn't upgrade your firmware, I say that's not an acceptable security situation. All that Netgear told us about this firmware update is that it "Fixes security vulnerability issues". Our routers are also primary network security defense mechanism and it's simply unreasonable to not be able to accept the latest firmware when it's released by a manufacturer - it's Netgear's responsbility to make sure it actually works before releasing it, and to be proactive in figuring out problems once they're announced by all these users. It seems like NG is saying they know it's a Traffic Meter problem, so why not just say that instead of telling people to waste their time factory resetting and reconfiguring their devices, or worse, rolling back to firmware version that is known to have whatever vulnerabilities were just patched.
