NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Wifi goes OFF everytime I reboot the router
When i reboot my router the wifi network goes off (see the attached screenhot). Also network password is a 10 digit password mix of alphabets, numbers and special characters but the admin screen onl...
I would say your firmware was not updated properly in the first place. You have a broken config and the lower firmware is just masking it. You should update all over again taking care to update satellites first and then the Router after with the proper firmware for each device.
If it's still broken you need to reset to factory defaults and re-setup everything.
I have the same exact issue...I have spent over 2 hours with Netgear Support.
- Factory Reset both Router/Satellites - Firmware v2.1.1.16
- Went through the whole process of setting it up - But once you make any changes - Bam Wifi stops
- Factory Reset both Router/Satellites - Firmware v2.1.1.12 (hard wired)
- Went through the whole process of setting it up - Again make one change - Bam wifi stops
- Factory Reset both Router/Satelllites - Upgrade back to current v2.1.1.16 (hard wired)
- Then support had me go in to Advance Setup - Wireless Setup and uncheck both - Enable Wireless SSID (2.4/5Ghz) - Apply and Close current page.
- Wait 2 mins - Go back into Advance Setup - Wireless Setup and re-check both SSID options again
- Still showing Warning no wifi even though SSID is enabled.
Still working with Support but will update if I get any further.
-------
UPDATE: There have been several others have
FYI - update:
There have been other reports of firmware not working and causing wifi to not work (SSID). Got this booted up to Level2 support which we were able to recreate the issue. I have downgraded back to 2.0.0.74 but Satellite will not show connected even though I am able to connect to it via IP address on my network.
It's just a Big F-ing headache and I am asking for full refund/return of the device since the firmware bricked my device.
Mudds
Yes very sad that a firmware which is not fit for mass deployment has been rolled out !
Mudds wrote:FYI - update:
There have been other reports of firmware not working and causing wifi to not work (SSID). Got this booted up to Level2 support which we were able to recreate the issue. I have downgraded back to 2.0.0.74 but Satellite will not show connected even though I am able to connect to it via IP address on my network.
It's just a Big F-ing headache and I am asking for full refund/return of the device since the firmware bricked my device.
If you go to the html page for the satellite you will see the radios aren't coming on, same issue of a too short key/password being seen by the device. Do a reset and maybe a couple of reboots and the radios on the satellite will eventually come on and keep coming on after power cycle if successfully downgraded to 2.0 firmware. If you are able to get an IP on the satellite then you are close, took me forever to get to that point.
On 2.0 now and all is fine but the simple solution for this 2.1 bug is to use a wireless password/key that displays correctly after being applied.
IT_fooly wrote:If you go to the html page for the satellite you will see the radios aren't coming on, same issue of a too short key/password being seen by the device. Do a reset and maybe a couple of reboots and the radios on the satellite will eventually come on and keep coming on after power cycle if successfully downgraded to 2.0 firmware. If you are able to get an IP on the satellite then you are close, took me forever to get to that point.
On 2.0 now and all is fine but the simple solution for this 2.1 bug is to use a wireless password/key that displays correctly after being applied.
Yea - After the upgrade of 2.1 firmware, I did notice my password was missing some characters or was shorter but I thought that was just the "display bug" they are calling it. I didn't try to update it to my original password. I was just done with 2.1, contant resetting back to factory and trying different methods to get it working, let alone stable.
In this post - https://community.netgear.com/t5/Orbi/Very-Sad-Orbi-RB50-experience/m-p/1481139#M20533 I basically, downgraded back to 2.0.0.76 beta (KRACK Fix) and disabled auto firmware update on both the router/satellite. Just done. Everything seems to be stable but I have notice some lag on the satellite with devices connected. I am running logs for that and assume 2.0.0.74 would be more stable than .76 but we will see.
My concern would be if a random disconnect/reboot or even a planned reboot of the router/satellite would they reconnect to each other consistently? So, far from my experience and testing the answer is no. It just seems 2.1 is not working as planned and causing a lot of issues.