NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
RBS50 issues with Firware V2.7.3.22 - Firmware incorrect
I have had an RBR50 +1 RBS50 satelite that had been working nearly flawlessly for some time,,,,until Firware V2.7.2.104. Devices being blocked from the internet when connected to the satelite, like ...
Factory reset the RBR and setup from scratch then. Wire connect a PC to the router and factory reset the router using the back push pin button. Hold it in for 15 seconds then let go. Power OFF the ISP modem for 30 seconds than back on. Wait for the WHITE led to slowly pulsate on top of the RBR, then log in to orbilogin.com using a web browser and walk thru the setup wizard. This time write down all important information for safe keeping later on.
I recommend the following as well afterwards:
e sure to save off a back up configuration to file for safe keeping. Saves time if a reset is needed.
https://kb.netgear.com/000062080/How-do-I-back-up-the-configuration-settings-on-my-Orbi-WiFi-System
ChuckieCheese wrote:I understand, but the issue is that NG LOCKED ME OUT when it did auto-firmware update. My password no longer works... not even the security questions or the default password
This is an example why auto-firmware update can be bad - for whatever reason, it messed up the authentication or something that I no longer can access the admin page.
Yes, I know about hard reset to factory, etc.
My point is the same: the auto-firmware update caused issue where the user is locked out from accessing the router.
It's NG decision to do auto-firmware update, but at least do it right and not cause issue like locking user out. And as a user, now I have to spend time doing reset, restore firmware, etc.? Does not sound user friendly at all.
Did you happen to turn OFF the RBR for 1 minute then back ON after you noticed the unit was updated?
Also tried a different web browser to access the RBR after you couldn't get back in? Be sure to clear out all caches as well.Historically, users have seen problems after auto update has happened. Sometimes a power OFF then back ON is all thats needed. Sometimes a reset is needed for others.
I agree, I don't really care much for auto update anything. I prefer to manually update myself.
ChuckieCheese wrote:Yes, I know about hard reset to factory, etc.
My point is the same: the auto-firmware update caused issue where the user is locked out from accessing the router.
It's NG decision to do auto-firmware update, but at least do it right and not cause issue like locking user out. And as a user, now I have to spend time doing reset, restore firmware, etc.? Does not sound user friendly at all.
FURRYe38 wrote:
Did you happen to turn OFF the RBR for 1 minute then back ON after you noticed the unit was updated?
Also tried a different web browser to access the RBR after you couldn't get back in? Be sure to clear out all caches as well.Yeah, I did the standard troubleshooting:
1. Power cycle, wait for a while, power back on
2. Use different browsers with cleared cache
3. Use different devices (Mac, iPad, etc.)
FURRYe38 wrote:
Historically, users have seen problems after auto update has happened. Sometimes a power OFF then back ON is all thats needed. Sometimes a reset is needed for others.
So it IS a known problem, but yet Netgear still FORCE the firmware auto-update? Even if I hard reset, there is no guarantee future auto-firmware update will NOT cause the same issue.
PS: I am not blaming you, I am blaming Netgear for doing crap like this that cause headache to user.
Ok, just checking.
Factory reset and if you have, load a back up config.TOTALLY understand man. Totally. I've never been a fan of NGs auto update on Orbi systems. I know there non Orbi routers provide an option for users to disable that on those models. Why NG does this on Orbi is beyond understanding. Orbi AX systems is same way. Also removed telnet on those models as well.
I also feel that NG needs to allow more pre-release beta testing for a few field users to help weed out issues like this prior to going full on public push release. Would have avoid some of this mess if we had a chance to beta test it first. Something I'll be pointing out to NG soon.
ChuckieCheese wrote:FURRYe38 wrote:
Did you happen to turn OFF the RBR for 1 minute then back ON after you noticed the unit was updated?
Also tried a different web browser to access the RBR after you couldn't get back in? Be sure to clear out all caches as well.Yeah, I did the standard troubleshooting:
1. Power cycle, wait for a while, power back on
2. Use different browsers with cleared cache
3. Use different devices (Mac, iPad, etc.)
FURRYe38 wrote:
Historically, users have seen problems after auto update has happened. Sometimes a power OFF then back ON is all thats needed. Sometimes a reset is needed for others.
So it IS a known problem, but yet Netgear still FORCE the firmware auto-update? Even if I hard reset, there is no guarantee future auto-firmware update will NOT cause the same issue.
PS: I am not blaming you, I am blaming Netgear for doing crap like this that cause headache to user.