NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
RBR50 - 2.7.2.104 firmware - Issues?
To whom it may concern, FURRYe38:
After upgrading my firmware to 2.7.2.104, I have been having issues. Devices successfully connect to the Orbi, but have no internet. If I reboot the Orbi and satellite, the devices may or may not successfully connect to the Orbi and have internet access.
Should I consider dropping the firmware back to 2.5.1.16 to potentially eliminate these issues?
125 Replies
Did you power OFF the ISP modem and RBR after the FW update?
How about a factory reset as last resort before going back?
Furrye38,
Hello again:).
Similar problem to OP. Updated firmware (.104) a few days ago and have had issues with wired or wireless getting to the internet. Logs don't provide any clues. This am, rebooted modem and no change. rebooted orbi and all is well (for now).
Any tools or suggestions an what to capture in order to determine the root cause? I hate just rebooting to fix a problem.
Please continue to post over in your original post:
https://community.netgear.com/t5/Orbi/RBK50/td-p/2070845/jump-to/first-unread-message
Thank you.
Jroach wrote:Furrye38,
Hello again:).
Similar problem to OP. Updated firmware (.104) a few days ago and have had issues with wired or wireless getting to the internet. Logs don't provide any clues. This am, rebooted modem and no change. rebooted orbi and all is well (for now).
Any tools or suggestions an what to capture in order to determine the root cause? I hate just rebooting to fix a problem.
Lets try the power OFF of the modem and RBR for 1 minute first then back ON.
BillYoung wrote:Hi FURRYe38:
To answer your questions:
Did you power OFF the ISP modem and RBR after the FW update? No.
How about a factory reset as last resort before going back? Would a factory reset really help if the firmware is the issue? I'll do it if you truly believe it would help.
Same exact issue after upgrading. At first it was just slow speed on my phone but then after that issue basically all devices in my home keep reporting no internet or internet unavailable. The only thing that seemed to alleviate the issue was putting my devices on static IP's with the gateway as DNS1 and a setting up google as DNS2. This fixed the issue but this never happened before the upgrade.
I'm going to reset it today and try again.
Also check your NTP settings. Seeing more posts regarding this since the time change this passed weekend. Try changing from NG server to time.nist.gov or something else and test.
Let us know how the reset goes. Someome posted the reset helped them.
CaptainPing wrote:Same exact issue after upgrading. At first it was just slow speed on my phone but then after that issue basically all devices in my home keep reporting no internet or internet unavailable. The only thing that seemed to alleviate the issue was putting my devices on static IP's with the gateway as DNS1 and a setting up google as DNS2. This fixed the issue but this never happened before the upgrade.
I'm going to reset it today and try again.
Why didn't I think of that! Freaking daylight savings, curse you! I'll check that setting a in a minute.
CaptainPing wrote:Same exact issue after upgrading. At first it was just slow speed on my phone but then after that issue basically all devices in my home keep reporting no internet or internet unavailable. The only thing that seemed to alleviate the issue was putting my devices on static IP's with the gateway as DNS1 and a setting up google as DNS2. This fixed the issue but this never happened before the upgrade.
I'm going to reset it today and try again.
Thanks
Let us know how your reset works.
Since i first purchased this router and satellites, it has been nothing but trouble. Every firmware update comes out half baked and causes me to lose hours of troubleshooting time. Same thing with .104. Internet is dropped within 5 minutes of a reboot. Zoom certificates aren't trusted. Common websites say their certificates are bad. Back to 2.6.1.40. And starting to look for a new wifi system...not from netgear.
Same here. Same issues with 2.7.2.104 and countless problems over the year. Never buying from Netgear again.
Try this then:
Works for me and others.
Good Luck
VanillaIcee wrote:Same here. Same issues with 2.7.2.104 and countless problems over the year. Never buying from Netgear again.
After spending an inordinate amount of time trying to go back to the former firmware, I was eventually unable to log on either with my password or with default "password". Could not access password recovery because it said my correct answers were wrong.
In this state, it worked for some devices not others. (Android worked, Apple devices not at all. Yes, rebooted everything.)
Finally did a factory reset -- unplugged base unit for 5 minutes, powered off modem, powered up the base unit while holding the "reset" button until it went from red-orange to green back to red-orange. Powered up modem. And went to the ORBI app and did a new set up using the same networks and passwords -- and eveyrthing reconnected (at least everything I've checked so far, which is lots but not all). I HAD to update to the latest. much discussed firmware so we'll see over the next few days. (Everything was fine when I first updated and then the trouble started, big time, a day later.
Worth a try.
Try using a wired PC or laptop and web browser to configure the RBR from a factory setup instead of the Orbi app. Be sure to not enable Traffic Meter as well.
WillRogersM wrote:After spending an inordinate amount of time trying to go back to the former firmware, I was eventually unable to log on either with my password or with default "password". Could not access password recovery because it said my correct answers were wrong.
In this state, it worked for some devices not others. (Android worked, Apple devices not at all. Yes, rebooted everything.)
Finally did a factory reset -- unplugged base unit for 5 minutes, powered off modem, powered up the base unit while holding the "reset" button until it went from red-orange to green back to red-orange. Powered up modem. And went to the ORBI app and did a new set up using the same networks and passwords -- and eveyrthing reconnected (at least everything I've checked so far, which is lots but not all). I HAD to update to the latest. much discussed firmware so we'll see over the next few days. (Everything was fine when I first updated and then the trouble started, big time, a day later.
Worth a try.
I had the same issue with the passowrd and secuirty questions not working. Instead of a reset, I tried again and this time I left the security answers blank and clicked ok and then I was able to log into my ORBI Operating system and adjust the settings. Go figure!
Interesting. I didn't know you could leave the questions blank. Well if it works for you then, why not.
BAM2019 wrote:I had the same issue with the passowrd and secuirty questions not working. Instead of a reset, I tried again and this time I left the security answers blank and clicked ok and then I was able to log into my ORBI Operating system and adjust the settings. Go figure!
Just chiming in that I think I'm having the same issue -- started the past week (...after DST) where the router is dropping selected devices... not everything; for example the wired Roku never looses connection, nor does my work laptop (wifi+VPN), but most other laptops / cell phones are losing their connection. It comes back after I reboot, but that only lasts for a few hours to half-a-day before I have to restart the router again.
I'm trying the DST/NTP sever update now, and will disable traffic meter and hope that works.
And in the meantime the firmware is still available for download without any comments on known issues.
It seams that things like this is outside the normal service procedures and therefore ignored. The problem, as customer, is that moving to another company makes no difference as the other company will have similar processes in place.
Gebla wrote:And in the meantime the firmware is still available for download without any comments on known issues.
It seams that things like this is outside the normal service procedures and therefore ignored. The problem, as customer, is that moving to another company makes no difference as the other company will have similar processes in place.
The root of the problem is that most people interpret 'available' to mean 'must have'
sad
Do try the factory reset as I described it. Make sure to use the same network settings (name and password). For me, EVERYTHING connected flawlessly.
I too had tried just a reset (or reboot really) with results similiar to yours. The factory reset seems to have done the trick.
The latest firmware (which, as I noted, I HAD to install) is working just fine now.
Wish you well.
SidewinderX wrote:Just chiming in that I think I'm having the same issue -- started the past week (...after DST) where the router is dropping selected devices... not everything; for example the wired Roku never looses connection, nor does my work laptop (wifi+VPN), but most other laptops / cell phones are losing their connection. It comes back after I reboot, but that only lasts for a few hours to half-a-day before I have to restart the router again.
I'm trying the DST/NTP sever update now, and will disable traffic meter and hope that works.
I think I'll have to do the factory reset. The updated NTP settings doesn't seem to solved it for me. Still getting regular disconnects. :(
Glad to have found this thread. I actually downgraded to 2.7.2.102 and then found this thread.
I had turned on Traffic Meter last week. I didn't put together the DNS Relay issue and my turning on Traffic Meter. I have now shut off Traffic Meter and my network is stable again.
This was a real pain because I set as many of the devices on my network as I could to switch to directly access the Google DNS Server instead of Comcast which I thought was the original issue. Things like my Honeywell smart thermostat couldn't phone home and was not able to be managed with the app or web. All is well again.
I guess I echo other posters and see what comes in 2.8 some day.
Thank you!
David
I upgraded from V2.5.2.4 directly to V2.7.2.104 and had no issues after the update. I did not touch the timeserver or the traffic meter settings (which I've never changed) and did not power off the router. The update was uneventful, the two satellites connected and all 25 devices have connected properly. I am using the Orbi in AP mode with no inputs on it used except the Etherent into it from my router. I don't know if the FW is bad or not but this is my experience.
Ursa99 wrote:I upgraded from V2.5.2.4 directly to V2.7.2.104 and had no issues after the update. I did not touch the timeserver or the traffic meter settings (which I've never changed) and did not power off the router. The update was uneventful, the two satellites connected and all 25 devices have connected properly. I am using the Orbi in AP mode with no inputs on it used except the Etherent into it from my router. I don't know if the FW is bad or not but this is my experience.
How long has it been?
8 Hours...
I had similar network connectivity issues as others after upgrading the firmware. Some devices would connect fine, others would not. My daughter resolved a Nintendo Switch connectivity issue by entering a DNS server address on her Nintendo Switch. My mobile phone and Dell laptop would not connect but my Roku stick never had a problem. Also the Orbi app would indicate no internet access but the web orbilogin access would indicate there was internet access, or vice versa. After reading some of this thread I disabled the traffic meter, which could only be done via the web interface, and that seems to have resolved the connectivity issues, at least so far after several hours of use.
Same issue here
https://community.netgear.com/t5/Orbi/LBR20-internet-signal-loss/m-p/2078542
a full reset didnt solve my issue
Disabled the traffic meter and changed the NTP just now, i'll report on how that works
Having had this issue for a few days now and reading reddit and the NTP/Traffic Meter might be the cause of the issues I've gone the disable Traffic meter route this morning.
