NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
R7000 2.4ghz not working but 5ghz is fine
Firmware 1.0.4.30 and 1.0.4.28 tried for weeks at a time.
Wireless devices connected to 5ghz band are all working perfectly and have been since i purchased this router at the beginning of June 2015.
As of 1.5 months ago, 2.4ghz band has been very intermittent, and at this point i was already using firmware 1.0.4.30. Rebooting the router did not do anything. I do not have any settings on the router except the ssid, password and channels.
I tried going back to firmware 1.0.4.28 and that only worked for maybe 2 days, then the disconnects started again. i have been using Wifi Analyzer app on my tablet just to see if there is a transmission signal from the router. 5ghz band has a constant transmission signal however the 2.4ghz band has an off to on time of maybe 3:1 at the best of times. This allows me to SOMETIMES connect to the router while on 2.4ghz band, but usually it will not connect. I have been forced to connect my desktop via a really long ethernet cable and older devices no longer have internet connections. I am currently still monitoring the off to on time and the worst as of yet is about 10:1. Basically the 2.4 ghz band is completely dead minus random spikes of it showing up.
I've seen a few posts with the 5ghz band issue similarly but no fix either. I used to have a wndr3700 and that worked fine until the range on the router out of nowhere and permanently dropped by about 25% causing me to buy a repeater to get coverage. Using the repeater solved the distance issue but then i had issues with connection speed (not huge but noticeable). I figured buying an R7000 would be a no brainer since its a top of the line unit and priced as such. I am very disappointed as i haven't been able to find a fix anywhere for this.
Any help would be greatly appreciated
Good news! We now have a production version of firmware that should resolve the 2.4 GHz issue, v1.0.5.64. You may download this firmware from our R7000 page here: http://downloadcenter.netgear.com/en/product/R7000#searchResults
As IrvSp correctly notes, this version of firmware fixes the 2.4 GHz issue and reinstates the new features, such as Kwilt, Smart Connect, and WiFI Transmit Power Control. It does not support Arlo. We hope to have a beta version that supports Arlo in the next two weeks.
We welcome any feedback you provide on this new firmware, and appreciate your patience as we resolved these issues. Thank you all for supporting the R7000 and NETGEAR!
425 Replies
Hi Everyone, if you have guest network enabled, disable and reboot and see if that works.
Please, go to MyNetgear and log an online support ticket to officiall log and document the incidents as tickets have to be tracked, resolved, and closed within their resolution tracking system and if enough are logged for the same issue and same impact it triggers a problem incident that then takes on a life of its own and will result in actual changes.
btw, my guest network is always disabled and I had the problem anyway...
- I tried guest 2.4 and 5ghz on and off and password/no password - always resulted in 2.4ghz crashing. Rolled back to 1.0.4.28_1.1.64 firmware two days ago. So far, reliable.
When I loaded firmware 1.0.6.23_1.1.83 on my Nighthawk R7000, it automatically enabled ARLO on my network. I don't own any ARLO devices and will never use it, but this firmware created a brand new SSID on my router that broadcast on the SAME CHANNEL as my 2.4 Ghz network. For a networking company, this really makes me question the technical knowledge of the engineers at Netgear.
When the ARLO SSID popped up on my network, it totally killed my 2.4Ghz network because it was on the same channel. The interference made my connection to my normal SSID drop out every couple of seconds. It wasn't until I opened up a Wifi scanner that I noticed the new SSID. When I updated the firmware, I did not see any alerts that the new SSID would be set up and enabled. Looking at the Genie settings, I was unable to find the ARLO setting to turn it off. It wasn't until I logged in to the web interface of the router (isn't the Genie software supposed to make it so we don't have to do this?) that I saw the setting to turn off ARLO.
Why in the world would a networking company do something so asinine? This is making me question my purchase of this router.
And, I just noticed that the firmware update also enabled Genie Media Server, again without my input. So I have to go look for the setting to disable this as well. How about when new features like these are added, we are given a choice as to whether we want them enabled?
With regard to sharing the 2.4 GHz channel by the ARLO SSID and your regular SSID, there's nothing asinine about it. The guest network, when enabled, operates in the same manner, and it certainly doesn't kill the channel. There certainly could be a bug, but in the absence of this, the channel should not be significantly affected by the ARLO SSID.
You can certainly question the benefit of enabling a new feature by default, but I will point out that it is well established that features are almost never used when they are disabled by default.
I do apologize for posting my complaint in multiple threads, I just wanted to be sure that anyone else searching for the same issue would be able to see it in a few different places.
Here are some logs I got from a Linux laptop, not sure if relevant (I don't use the router as my main unit anymore, so I wasn't using the laptop at that specific moment), but...
[24787.047715] wlan0: authenticate with c4:04:15:5b:ad:ec [24787.065736] wlan0: send auth to c4:04:15:5b:ad:ec (try 1/3) [24787.070892] wlan0: authenticated [24787.071609] wlan0: associate with c4:04:15:5b:ad:ec (try 1/3) [24787.090121] wlan0: RX AssocResp from c4:04:15:5b:ad:ec (capab=0x1411 status=0 aid=3) [24787.090222] wlan0: associated [26595.067399] wlan0: AP c4:04:15:5b:ad:ec changed bandwidth, new config is 2437 MHz, width 1 (2437/0 MHz) [26595.067407] wlan0: AP c4:04:15:5b:ad:ec changed bandwidth in a way we can't support - disconnect [26596.171009] wlan0: authenticate with c4:04:15:5b:ad:ec [26596.187849] wlan0: send auth to c4:04:15:5b:ad:ec (try 1/3) [26596.191355] wlan0: authenticated [26596.192287] wlan0: associate with c4:04:15:5b:ad:ec (try 1/3) [26596.299421] wlan0: associate with c4:04:15:5b:ad:ec (try 2/3) [26596.401514] wlan0: associate with c4:04:15:5b:ad:ec (try 3/3) [26596.532624] wlan0: association with c4:04:15:5b:ad:ec timed out
Once I got the bandwidth change, it struggled to connect back for a while, with a ton of this kind of entries:
[38978.203911] wlan0: authenticated [38978.205258] wlan0: associate with c4:04:15:5b:ad:ec (try 1/3) [38979.018988] wlan0: associate with c4:04:15:5b:ad:ec (try 2/3) [38979.597474] wlan0: associate with c4:04:15:5b:ad:ec (try 3/3) [38979.931728] wlan0: association with c4:04:15:5b:ad:ec timed out [38987.901790] wlan0: authenticate with c4:04:15:5b:ad:ec [38987.916788] wlan0: send auth to c4:04:15:5b:ad:ec (try 1/3) [38988.584247] wlan0: authenticated [38988.584990] wlan0: associate with c4:04:15:5b:ad:ec (try 1/3) [38988.744159] wlan0: associate with c4:04:15:5b:ad:ec (try 2/3) [38988.874270] wlan0: associate with c4:04:15:5b:ad:ec (try 3/3) [38989.030395] wlan0: association with c4:04:15:5b:ad:ec timed out [39000.005472] wlan0: authenticate with c4:04:15:5b:ad:ec [39000.023958] wlan0: send auth to c4:04:15:5b:ad:ec (try 1/3) [39000.057593] wlan0: authenticated [39000.058608] wlan0: associate with c4:04:15:5b:ad:ec (try 1/3) [39000.621133] wlan0: associate with c4:04:15:5b:ad:ec (try 2/3) [39000.957932] wlan0: associate with c4:04:15:5b:ad:ec (try 3/3) [39001.147543] wlan0: association with c4:04:15:5b:ad:ec timed out [39019.021418] wlan0: authenticate with c4:04:15:5b:ad:ec [39019.039874] wlan0: send auth to c4:04:15:5b:ad:ec (try 1/3) [39019.092735] wlan0: authenticated [39019.093598] wlan0: associate with c4:04:15:5b:ad:ec (try 1/3) [39019.631177] wlan0: associate with c4:04:15:5b:ad:ec (try 2/3) [39019.841233] wlan0: associate with c4:04:15:5b:ad:ec (try 3/3) [39020.125504] wlan0: association with c4:04:15:5b:ad:ec timed out
Kernald wrote:Here are some logs I got from a Linux laptop, not sure if relevant (I don't use the router as my main unit anymore, so I wasn't using the laptop at that specific moment), but...
[24787.047715] wlan0: authenticate with c4:04:15:5b:ad:ec [24787.065736] wlan0: send auth to c4:04:15:5b:ad:ec (try 1/3) [24787.070892] wlan0: authenticated [24787.071609] wlan0: associate with c4:04:15:5b:ad:ec (try 1/3) [24787.090121] wlan0: RX AssocResp from c4:04:15:5b:ad:ec (capab=0x1411 status=0 aid=3) [24787.090222] wlan0: associated [26595.067399] wlan0: AP c4:04:15:5b:ad:ec changed bandwidth, new config is 2437 MHz, width 1 (2437/0 MHz) [26595.067407] wlan0: AP c4:04:15:5b:ad:ec changed bandwidth in a way we can't support - disconnect [26596.171009] wlan0: authenticate with c4:04:15:5b:ad:ec [26596.187849] wlan0: send auth to c4:04:15:5b:ad:ec (try 1/3) [26596.191355] wlan0: authenticated [26596.192287] wlan0: associate with c4:04:15:5b:ad:ec (try 1/3) [26596.299421] wlan0: associate with c4:04:15:5b:ad:ec (try 2/3) [26596.401514] wlan0: associate with c4:04:15:5b:ad:ec (try 3/3) [26596.532624] wlan0: association with c4:04:15:5b:ad:ec timed out
Once I got the bandwidth change, it struggled to connect back for a while, with a ton of this kind of entries:
[38978.203911] wlan0: authenticated [38978.205258] wlan0: associate with c4:04:15:5b:ad:ec (try 1/3) [38979.018988] wlan0: associate with c4:04:15:5b:ad:ec (try 2/3) [38979.597474] wlan0: associate with c4:04:15:5b:ad:ec (try 3/3) [38979.931728] wlan0: association with c4:04:15:5b:ad:ec timed out [38987.901790] wlan0: authenticate with c4:04:15:5b:ad:ec [38987.916788] wlan0: send auth to c4:04:15:5b:ad:ec (try 1/3) [38988.584247] wlan0: authenticated [38988.584990] wlan0: associate with c4:04:15:5b:ad:ec (try 1/3) [38988.744159] wlan0: associate with c4:04:15:5b:ad:ec (try 2/3) [38988.874270] wlan0: associate with c4:04:15:5b:ad:ec (try 3/3) [38989.030395] wlan0: association with c4:04:15:5b:ad:ec timed out [39000.005472] wlan0: authenticate with c4:04:15:5b:ad:ec [39000.023958] wlan0: send auth to c4:04:15:5b:ad:ec (try 1/3) [39000.057593] wlan0: authenticated [39000.058608] wlan0: associate with c4:04:15:5b:ad:ec (try 1/3) [39000.621133] wlan0: associate with c4:04:15:5b:ad:ec (try 2/3) [39000.957932] wlan0: associate with c4:04:15:5b:ad:ec (try 3/3) [39001.147543] wlan0: association with c4:04:15:5b:ad:ec timed out [39019.021418] wlan0: authenticate with c4:04:15:5b:ad:ec [39019.039874] wlan0: send auth to c4:04:15:5b:ad:ec (try 1/3) [39019.092735] wlan0: authenticated [39019.093598] wlan0: associate with c4:04:15:5b:ad:ec (try 1/3) [39019.631177] wlan0: associate with c4:04:15:5b:ad:ec (try 2/3) [39019.841233] wlan0: associate with c4:04:15:5b:ad:ec (try 3/3) [39020.125504] wlan0: association with c4:04:15:5b:ad:ec timed out
I found a few threads on the Internet that suggest that this could be a Linux problem with handling changes between 40 MHz and 20 MHz channels. It's pretty much impossible to use 40 MHz at 2.4 GHz whenever other Wi-Fi networks are active. You can force the R7000 to use 20 MHz channels by changing the wireless mode from Up to 600 Mbps to Up to 289 Mbps. This might avoid the Linux issue.
- I rolled back to 1.0.4.28_1.1.64 firmware three days ago. I have between four different devices connected 2.4ghz all the time and two more that connect periodically. I have up to five devices connected to 5ghz and 12 devices connected via Ethernet. Has worked without issue for three days now.
- I rolled back to 1.0.4.28_1.1.64 firmware three days ago. I have between four different devices connected 2.4ghz all the time and two more that connect periodically. I have up to five devices connected to 5ghz and 12 devices connected via Ethernet. Has worked without issue for three days now.
This morning I rolled back from
V1.0.6.28_1.1.83
to
V1.0.4.30_1.1.67
(rather than 4.28)
Let's see what happens...
- Stuckincube - I tested 4.30 thoroughly and it failed in exactly the same way as all later versions. I rolled back to 4.28 four days ago and, so far, rock solid.
KazzMANIA wrote:
Stuckincube - I tested 4.30 thoroughly and it failed in exactly the same way as all later versions. I rolled back to 4.28 four days ago and, so far, rock solid.ok, since I already flashed it and set everything up again I'll let it run to see how long it goes before failing and post an update; but I guess I will expect to set everything up AGAIN. Netgear better get their s|-|it together soon... arg.
For me, I tried all of the previous suggestions, none of which worked. After resetting my configuration to default, and resetting up, I noticed that my 2ghz channel was set to Auto, changed it to 11, and everything started working.
- Dnacool1 - are you sure you updated to 4.28?
- Also - please run 5 speed tests using speedtest.net. Run it from a device connected to Ethernet. How long has your router been stable? What firmware version?
I have had this same problem with a router I bought 9 months ago and one I bought just a few days ago. I have rolled back the firmware to V1.0.5.48_1.1.79 and both seem to be working for a couple of days. I too hope that it is a firmware problem that can be addressed easily. I tried the other suggestions of reset to factory and it worked only one day before the problem appeared again. I have checked for any other problems such as interference using a WiFi app for my smart phone and have found no problems.
