NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
SW_
Mar 22, 2019Prodigy
New Orbi RBR50/RBS50 Firmware Version 2.3.1.44
Netgear is pushing out yet another a new Orbi firmware update.
Hopefully it's better than the last version v32.
Please share your experience.
Firmware Update
...
SBell
Apr 09, 2019Guide
FURRYe38 wrote:
Try a factory reset and setup from scratch. I've had zero issues with wifi dropping with v44 loaded. Others as well. Just need a factory reset and setup from scratch is all.
What is the size of your home? Sq Ft?
What is the distance between the router and satellite(s)? 30 feet is recommended in between them to begin with depending upon building materials when wirelessly connected.
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?
Try enabling Beamforming and MIMO and WMM. Under Advanced Tab/Advanced Settings/Wireless Settings
SBell wrote:
I've been having non stop wifi dropouts since this firmware update was pushed out. I have to restart the RBR50 and two RBS50 sattelites every 20-30 minutes just to get it to work for a little while. I've owned the Orbi for 1.5 years and have gone through multiple periods of huge dropout issues related to firmware updates. I dont have the time or patience to spend half a day trying to revert back to an earlier firmware version or trying to troubleshoot Netgear's shoddy hardware and software engineering. The only reason I've kept it this long is because it cost so much I wanted to at least get some use out of it before tossing it in the dumpster. Going to start looking for an alternative this time. It's not worth the constant hassle to keep the Orbi. Will definitely never buy a Netgear product again!
Sorry, but none of this is helpful. "Just need a factory reset and setup from scratch is all." I've been down that road each of the multiple times the Orbi has failed over the last year and a half and I'm done wasting time on it. Would you be fine with having to wipe and restore your phone each time it's updated? How about wiping and restoring your computer each time it's updated? Or any of your other electronics? It shouldn't require hours or days of troubleshooting to try and restore a working wifi setup everytime Netgear pushes a firmware update.
And as far as "What size is your home? What's the distance...? How many neighbors...? etc." None of that changed, so it's completely irrelevant. The Orbi had been stable for a few months with no drop outs. The only thing that changed is that Netgear pushed a defective firmware update out, automatically updated my router, and made a mess of my wifi network. The issue is their firmware and not my set up.
I'm not going to waste an hour or two trying a reset that may or may or may not work. I'm going to use that hour or two to research and buy a new router from a company with better quality products and better customer service.
FURRYe38
Apr 09, 2019Guru - Experienced User
Good Luck then. v44 IS working well for others.
- lukpacApr 09, 2019Apprentice
FURRYe38 wrote:
Good Luck then. v44 IS working well for others.
I can't say I disagree with the previous comment. Can you imagine Microsoft telling people to reimage their PCs every time there was a Windows update?
2.3.1.44 may be working fine for some people, but that doesn't mean it doesn't have inherent issues. Not everyone has the same configurations or the same clients. Heck, I've noticed no issues on my iPhone for as long as we've had Orbi, but my wife often complains that her Android phone keeps disconnecting. It's not helpful to suggest that because some people aren't having issues that if people do have issues it's somehow their fault.
- FURRYe38Apr 09, 2019Guru - Experienced User
Its also not help when questions are asked and the questions are not answered or marked as irrelevant. Questions presented ARE relevant. This only helps us and users narrow down some things where there are inherent issues in FW. In some cases there are user mis-configurations and in FW. Again, Were only here to help users try and get there systems working. If users don't want to let us help them, then they can get ahold of official NG support. :smileyvery-happy:
- lukpacApr 09, 2019Apprentice
FURRYe38 wrote:
Its also not help when questions are asked and the questions are not answered or marked as irrelevant. Questions presented ARE relevant. This only helps us and users narrow down some things where there are inherent issues in FW. In some cases there are user mis-configurations and in FW. Again, Were only here to help users try and get there systems working. If users don't want to let us help them, then they can get ahold of official NG support. :smileyvery-happy:
Who is "us"? And "inherent issues in FW"? What inherent issues are you talking about?
Also, it's not clear why the settings in question aren't enabled by default if they supposedly fix the problems. Or why they can be changed at all.
- michaelkenwardApr 09, 2019Guru - Experienced User
lukpac wrote:I can't say I disagree with the previous comment. Can you imagine Microsoft telling people to reimage their PCs every time there was a Windows update?
You compare a reset with reimaging a PC?
Blimey. You have a low hassle threshold. It is an unfortunate fact if life that all router makers sometimes inflict this on users. Mostly it is not needed, but just occasionally stuff happens.
I suspect that the real culprits are the chipset makers.
Commercial routers may not suffer from this disease, but at a cost.
Last week I was sitting in the driving seat of a Jaguar iPace when the "firmware" was updating. That has two banks of memory. It loads new software into one back, leaving the old version in the other bank. It can be done, but at a price.
- FURRYe38Apr 09, 2019Guru - Experienced User
Updaing FW while the car was in motions? I hope not. That would be scary if the FW failed or caused a problem during montion upon reboot. LOL. Whoa.
michaelkenward wrote:
Last week I was sitting in the driving seat of a Jaguar iPace when the "firmware" was updating. That has two banks of memory. It loads new software into one back, leaving the old version in the other bank. It can be done, but at a price.