NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
RBR750 Shows Offline After FW Update
I just updated the FW on my RBR750, and now I am unable to access the orbi via the app, or by IP (192.168.5.1). I have deleted and re-installed and logged back into the app, still unable to conne...
- NG must have pushed the update to me. I can now access everything via the browser. App just spins when I put in the password in and I assume times out, but I may need to delete and reinstall. But that will be a tomorrow project.
Just excited that I got a win!
TONS of us have this issue. I have read that factory reset works, but can’t confirm. The latest firmware made routers “unfindable” via any route. Netgear is SO BAD!! Imagine they pushed an update that did this to so many and don’t even post a fix. Insanity.
I've seen several threads regarding this issue...but of course only after I did the update 😞
Hopefully Netgear will chime in here soon and provide some insight into what I need to do here....
I certainly do not envy the software engineer who has been told, "stop what you're working on (and miss your deadline) and figure out what the heck is going on with these Orbi routers!" One has to assume that there is a Quality Assurance process before releasing new firmware. If this new version immediately caused every router that loaded it to become unreachable, they could not have even verified that the firmware got loaded, much less perform any sort of QA tests. Finding the common factor may not be simple.
Ah, the "good old days." I remember several years ago when the original RBR50 went whacko at Daylight Saving Time in March and lost DNS capability. No Internet! Took several days for Netgear to discover that a bug in Traffic Meter got triggered and affected DNS. Users who did not have Daylight Saving Time or Traffic Meter enabled were not affected at all. "Problem? I've got no problem!" The fix was to keep Traffic Meter off until April 1, when the problem went away by itself. That gave Netgear until November to produce and test a new firmware release.
OH yikes! I bet that is dreadful for someone on the Orbi/Netgear side!
One of the threads I read said that it only seems to be happening to users who have a non-standard IP Range set for the internal LAN.
