NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
V2.3.5.30 Upgrade Has Been A Disaster
I have an Orbi router with three satellites all connected with Backhaul status "Good". Our experience has been touch and go with the Orbi with Satellites and device connections dropping intermittentl...
ar9 wrote:Everyone told me to upgrade the firmware so I finally upgraded each device to the latest firmware V2.3.5.30 (that was a nighmare by itself) and now our internet access has become a disaster.
...not everyone. You might try to backstep/revert your FW to the previous version. Why (besides THEY told you too) did you upgrade the FW?
After working fine for many months, devices that connected via the satellites were getting invalid certificate errors and couldn't access any https sites. Devices that connected directly to the router were ok. I contacted Netgear and spoke with several people who started with factory resets etc. but eventually "everyone" of them told me to upgrade to the latest firmware and that would fix the problem. It just made it worse in that now even connecting via the router fails, and furthermore I can't access the satellites' web pages which I had used to upgrade them and would use to downgrade them. The actual Orbi router web interface is working and shows all three Satellites connected and servicing devices.
Has a factory reset and setup from scratch been performed since upgrading to v30? I would do this for the RBR. Leave off the RBS for now. Get the RBR setup and re-configrued. Test wtih jsut the RBR with a wired PC and some wireless devices. Check for internet and secure web site access here. IF you can get to this point, then start with 1 RBS and factory reset it. Press the sync button on the back of the RBR and RBS and let it sync. Then check internet connection with a wireless device connected to the RBS.
What is the Mfr and model# of the ISP modem the NG router is connected too?
By the way - thank you to all who posted suggestions.
I definitely know the drill - I did this when the problem first started before the firmware upgrade but I only got to the point where the Orbi itself was working - I reset each Satellite and added it but the Orbi only eventually accepted two of the three, and devices connected to those two Satellites had the certificate problem.
I will do a reset on the Orbi and try getting it to function alone and then try resetting and adding Satellites one at a time and see how far it gets.
Here's some more info that may be revealing - to me it was just frustrating. Well before the upgrade when devices started failing to connect to the internet, I noticed that when I was on a device connected via a Satellite I would ping an external url it would resolve to the ip address of the satellite itself rather than the external ip address (devices connected directly to the Orbi could ping out just fine). I found this really strange because for the longest time I had no problem with pinging from devices connected via Satellites. I remember enabling the particular Satellite's telnet via the debug web page (it was working at that time) and telnetting in and when I randomly restarted some networking services the pinging started behaving but only for a short while and then the pinging bizaarness returned.
ar9 wrote:By the way - thank you to all who posted suggestions.
I definitely know the drill - I did this when the problem first started before the firmware upgrade but I only got to the point where the Orbi itself was working - I reset each Satellite and added it but the Orbi only eventually accepted two of the three, and devices connected to those two Satellites had the certificate problem.
I will do a reset on the Orbi and try getting it to function alone and then try resetting and adding Satellites one at a time and see how far it gets.
Here's some more info that may be revealing - to me it was just frustrating. Well before the upgrade when devices started failing to connect to the internet, I noticed that when I was on a device connected via a Satellite I would ping an external url it would resolve to the ip address of the satellite itself rather than the external ip address (devices connected directly to the Orbi could ping out just fine). I found this really strange because for the longest time I had no problem with pinging from devices connected via Satellites. I remember enabling the particular Satellite's telnet via the debug web page (it was working at that time) and telnetting in and when I randomly restarted some networking services the pinging started behaving but only for a short while and then the pinging bizaarness returned.
Good luck. Sounds like you may be on the road to recovery. I find your discussion and efforts concerning pinging and telent a bit interesting from the standpoint that you didn't note you had a modem/router combo (??).
Once things settle down I would get the Orbi and Sats at the proper distance as Furry mentioned and away you go.
ar9 wrote:........... but eventually "everyone" of them told me to upgrade to the latest firmware and that would fix the problem. It just made it worse in that now even connecting via the router fails, and furthermore I can't access the satellites' web pages which I had used to upgrade them and would use to downgrade them. The actual Orbi router web interface is working and shows all three Satellites connected and servicing devices.
i don't know why the default recommendation is to update the FW. Normally this should work IF it can be confirmed that the next step up FW is proved to be near error free, and I'm not sure that will ever happen after listening to the way some folks run there networks. It all seems to be about providing WIFI to your entire house (good) and your neighbos (what??) at the fastest and faster speed. Read the box the Orbi came in and see how much square feet it covers..
In this community all one needs to do is scan/search and read the posts to realize there is a problem with any particular FW. The only safe bet is once you get back to ground zero (no problems) leave the FW updates alone. When NG has a FW with what they call 'major revisions' they will push it to all. IF that breaks your network, well at lease you can blame them and not yourself.
