NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
NCJeepMan
Sep 25, 2014Aspirant
R7000 5ghz Disappearing
Seems to be a lot of independent questions/discussions on or this topic or similar topics... Looking for someone to give me a definitive answer, so here's the question:
- My R7000 periodically and randomly drops the 5ghz band and all devices connected to it lose connection - the 5ghz network SSID is not broadcasting.
- When looking at the router admin page, it SAYS the 5ghz is running and normal.
- Requires complete unplugging and reboot before 5ghz shows back up again.
This is an expensive router so I am not happy that it is flaky and requires this kind of baby sitting. Anyone have a suggestion?
- My R7000 periodically and randomly drops the 5ghz band and all devices connected to it lose connection - the 5ghz network SSID is not broadcasting.
- When looking at the router admin page, it SAYS the 5ghz is running and normal.
- Requires complete unplugging and reboot before 5ghz shows back up again.
This is an expensive router so I am not happy that it is flaky and requires this kind of baby sitting. Anyone have a suggestion?
I've been running Firmware Version V1.0.6.28_1.1.83 for a few months now without any 5GHz dropping. The big tip that helped me, was after doing the firmware update, I did a factory reset to reset all of the settings to default, and it also forces the router to get new internal drivers for itself. Before I did this, I was always losing my 5GHz.
63 Replies
- rpoffenVirtuoso
ScottieK wrote: @Babylon5/Andy - I am having the same issues; started today. I lost 2.5 and 5; I have used every device that connects via wifi with both bands.
I am having a similar issue. I lose both 2.5 and 5Ghz, all connected devices disconnect. They come back after about 30 seconds. I see nothing in the router logs. I don't think it is a full reboot of the router since it is only 30 seconds or so. This happens several times a day at random intervals.
I have not been able to get to the router quick enough to see what the LED's on the router are showing.
I am using 1.0.4.18 FW.
Once I tried a reset to defaults, than restored settings from backup, as was suggested in another thread and it seemed to have helped for a while, but it is now back.
I will upgrade to the latest 1.0.4.68 FW using the full factory reset procedure and see if that helps. - Babylon5NETGEAR Employee Retiredbjl95mustang, have you exchanged yet, if not what firmware version are you running?
ScottieK, what is your firmware version please?
rpoffen, please let us know how you get on with the new firmware. - bjl95mustangNovice
I have exchanged it. But I was running 1.1.64. I had been having problems with it since I got it new in Dec of 14. I just got my replacement Thursday morning all hooked up and flashed with 1.1.64. It's been 100% with no issues. My previous one would drop 5ghz after 1-2 days and it would not return unless I rebooted it. I also noticed I am getting a better signal through my house with the replacement. It appears to have been a hardware issue like tech support said. We'll see if she holds up for the long run.Babylon5 wrote: bjl95mustang, have you exchanged yet, if not what firmware version are you running? - RogerSCVirtuosoWhat's version 1.1.64? Are you sure? What router do you have? There's no version 1.1.64 for the R7000 that I see anywhere?
- bjl95mustangNoviceSorry should say 1.0.4.28. I just grabbed the last 4 digits from the status page. Firmware Version V1.0.4.28_1.1.64
- rpoffenVirtuoso
Babylon5 wrote: bjl95mustang, have you exchanged yet, if not what firmware version are you running?
rpoffen, please let us know how you get on with the new firmware.
The other day I upgraded to the latest V1.0.4.28_1.1.64 firmware. When upgrading, I first reset back to factory defaults, configured it enough to allow me to upload the new firmware, then I reset to factory defaults, and re-configured my settings. So far, it has not dropped since (keeping my fingers crossed).
One thing I did not like during the process was that the initial setup genie tries to be too smart for its own good. The first thing it says is that it detected another router on my network (which is not really true, the DSL modem that my provider uses appears to have a limited amount of smarts by default, but not truly a router), so the Genie setup limited how I could configure it. It would not take properly if I tried to manually say to set it up as a router instead of an access point, but if I left it as an AP, then I could not properly get DHCP to work as the DSL modem does not give out more than 5 IP's.
I ended up restoring a saved config backup and it worked after that.
The only other setting I changed was to force channel 6 on the 2.4G wireless rather than auto (this was something I picked up on another forum). I noticed that when I changed the channel, and clicked apply, the wireless networks went down for about 30 seconds, hmm, same amount of down time that my dropouts were taking. I wonder if when left to auto, and the router decided to change channels, this explained my dropouts? Maybe just coincidence? As I stated before, my dropouts were not as long as a full router reboot takes. But the channel change dropout appears about right. - theoakLuminaryOne thing that may help at least from a 2.4G perspective ... select channel 1.
I had a tough time getting some wireless IP cameras around my home to stay connected. I naturally selected channel 11 because doing a scan using inSSIDer revealed that it was the channel with no one on it. My cameras can only use 2.4G.
For three weeks nothing but grief to keep these cameras connected. I then remembered something back in my DD-WRT days where someone stated to the effect that they could get things to work only on channel 1 with a problem they had. Out of desperation I thought why not.
For the past 5 days or so my cameras have been solid.
Now, it could be the fault of the cameras; however, it works for me. I may prefer the clear channel 11, but right now channel 1 is the ticket. Give 1 a whirl. - rpoffenVirtuosoI am remote enough (closest neighbors are about 1/4mi away) that there is no congestion on the channels, it just seemed suspicious that the recovery time after changing the channel in the router setup was the same as my dropouts were, which is far shorter than a router reboot. Forcing a fixed channel would prevent the router from changing channels for any reason.
The only other devices that might cause interference are a Microwave and cordless phone. - theoakLuminaryI am not saying forcing to channel 1 makes sense, it just is working.
- Babylon5NETGEAR Employee RetiredRpoffen, why do you suggest that your modem is ‘not truly a router’? Most DSL modems are in fact fully blown routers performing NAT, and it’s NAT that will often cause unexpected issues with another connected router.
In your situation, with no nearby neighbours, I would also use a fixed channel, there would be little advantage to leaving that option to the router, and some client devices are not too good at tracking the AP channel changes.