4th one in a row- can't connect to 2.4

[rudolphna]

Okay, I'm really getting ready to say screw it and be done. This is no joke, the 4th one I've had this EXACT SAME problem with in a row.

Including 3 from newegg, and one from Best Buy.

The very first one had this problem from day 1. Wired and 5Ghz work perfectly fine. 2.4Ghz unable to connect with any kind of security enabled. All channels, changed everything you can think of. With open network, you can connect, but latency is terrible, and bad packet loss, ie completely unusable. This is with 5 different devices. Laptops, desktop, smartphone. That one was immediately RMA'd.

The second one worked for about 2 weeks before the EXACT SAME problem developed. 3rd one lasted about a week. Then this most recent one, I bought from Best Buy. It's been absolutely perfect for almost 3 months. And this morning when I get up to go to work, everyone is complaining "The internet doesn't work!" Well I'll be damned, wired works. 5Ghz works. 2.4Ghz unable to connect. #&!@#&*!@#

I do not understand. I've tried flashing to the most recent firmware. I've tried EVERYTHING. 2.4Ghz just does not work. Windows computers do the "Windows was unable to connect to the network" android smartphones try to connect, and retry, and retry, in infinite cycle. If I change the SSID it briefly connects, and looks normal, but when you actually try to surf, it hangs, and then disconnects, and won't let you reconnect. Again, 5Ghz and wired both work perfectly.

This in the system log when this is happening. Terran is my laptop with Intel Centrino N-6230

Jan 13 22:03:33 miniupnpd[601]: HTTP listening on port 54400
Jan 13 22:03:33 miniupnpd[601]: Listening for NAT-PMP traffic on port 5351
Jan 13 22:03:34 kernel: eth1: received packet with own address as source address
Jan 13 22:03:36 dnsmasq-dhcp[505]: DHCPINFORM(br0) 192.168.1.99 54:04:a6:32:ce:53
Jan 13 22:03:36 dnsmasq-dhcp[505]: DHCPACK(br0) 192.168.1.99 54:04:a6:32:ce:53 ARCHON
Jan 13 22:03:38 dnsmasq-dhcp[505]: DHCPREQUEST(br0) 192.168.1.13 88:53:2e:c9:ea:ff
Jan 13 22:03:38 dnsmasq-dhcp[505]: DHCPACK(br0) 192.168.1.13 88:53:2e:c9:ea:ff Terran
Jan 13 22:03:45 dnsmasq-dhcp[505]: DHCPREQUEST(br0) 192.168.1.13 88:53:2e:c9:ea:ff
Jan 13 22:03:45 dnsmasq-dhcp[505]: DHCPACK(br0) 192.168.1.13 88:53:2e:c9:ea:ff Terran
Jan 13 22:04:00 dnsmasq-dhcp[505]: DHCPREQUEST(br0) 192.168.1.13 88:53:2e:c9:ea:ff
Jan 13 22:04:00 dnsmasq-dhcp[505]: DHCPACK(br0) 192.168.1.13 88:53:2e:c9:ea:ff Terran
Jan 13 22:04:04 dnsmasq-dhcp[505]: DHCPREQUEST(br0) 192.168.1.13 88:53:2e:c9:ea:ff
Jan 13 22:04:04 dnsmasq-dhcp[505]: DHCPACK(br0) 192.168.1.13 88:53:2e:c9:ea:ff Terran
Jan 13 22:04:12 dnsmasq-dhcp[505]: DHCPREQUEST(br0) 192.168.1.13 88:53:2e:c9:ea:ff
Jan 13 22:04:12 dnsmasq-dhcp[505]: DHCPACK(br0) 192.168.1.13 88:53:2e:c9:ea:ff Terran
Jan 13 22:04:37 dnsmasq-dhcp[505]: DHCPDISCOVER(br0) 192.168.1.13 88:53:2e:c9:ea:ff
Jan 13 22:04:37 dnsmasq-dhcp[505]: DHCPOFFER(br0) 192.168.1.13 88:53:2e:c9:ea:ff
Jan 13 22:04:37 dnsmasq-dhcp[505]: DHCPREQUEST(br0) 192.168.1.13 88:53:2e:c9:ea:ff
Jan 13 22:04:37 dnsmasq-dhcp[505]: DHCPACK(br0) 192.168.1.13 88:53:2e:c9:ea:ff Terran
Jan 13 22:04:43 dnsmasq-dhcp[505]: DHCPINFORM(br0) 192.168.1.13 88:53:2e:c9:ea:ff
Jan 13 22:04:43 dnsmasq-dhcp[505]: DHCPACK(br0) 192.168.1.13 88:53:2e:c9:ea:ff Terran
Jan 13 22:04:46 dnsmasq-dhcp[505]: DHCPINFORM(br0) 192.168.1.13 88:53:2e:c9:ea:ff
Jan 13 22:04:46 dnsmasq-dhcp[505]: DHCPACK(br0) 192.168.1.13 88:53:2e:c9:ea:ff Terran
Jan 13 22:05:44 notify_rc : restart_wireless
Jan 13 22:05:45 kernel: Ebtables v2.0 registered
Jan 13 22:05:45 kernel: device eth1 left promiscuous mode
Jan 13 22:05:45 kernel: br0: port 2(eth1) entering disabled state
Jan 13 22:05:45 kernel: device eth2 left promiscuous mode
Jan 13 22:05:45 kernel: br0: port 3(eth2) entering disabled state
Jan 13 22:05:46 kernel: wl_module_init: passivemode set to 0x0
Jan 13 22:05:46 kernel: eth1: Broadcom BCM4331 802.11 Wireless Controller 5.100.138.20
Jan 13 22:05:46 kernel: eth2: Broadcom BCM4331 802.11 Wireless Controller 5.100.138.20
Jan 13 22:05:46 kernel: device eth1 entered promiscuous mode
Jan 13 22:05:46 kernel: br0: port 2(eth1) entering listening state
Jan 13 22:05:46 kernel: br0: port 2(eth1) entering learning state
Jan 13 22:05:46 kernel: br0: topology change detected, propagating
Jan 13 22:05:46 kernel: br0: port 2(eth1) entering forwarding state
Jan 13 22:05:47 kernel: device eth2 entered promiscuous mode
Jan 13 22:05:47 kernel: br0: port 3(eth2) entering listening state
Jan 13 22:05:48 kernel: br0: port 3(eth2) entering learning state
Jan 13 22:05:48 kernel: br0: topology change detected, propagating
Jan 13 22:05:48 kernel: br0: port 3(eth2) entering forwarding state
Jan 13 22:05:49 dnsmasq-dhcp[505]: DHCPREQUEST(br0) 192.168.1.13 88:53:2e:c9:ea:ff
Jan 13 22:05:49 dnsmasq-dhcp[505]: DHCPACK(br0) 192.168.1.13 88:53:2e:c9:ea:ff Terran
Jan 13 22:05:52 notify_rc : restart_wireless


So something is happening here, and it keeps resetting the wireless apparently after connection attempts. How do I fix this? do I have to exchange it AGAIN? I mean, I don't understand, I don't mistreat it, it's up on the stand in a cool room.

Does anyone have any clue as to what is going on?

 

[SoCalReviews]

It's probably from 2.4Ghz band interference in your area from other routers your neighbors are using or there could be other devices using that band. There could also be a conflict with one or more of the devices you are using with the 2.4Ghz radio that are not compatible with your Asus wireless radio. Make sure you are using the latest firmware from Asus. Set your 2.4Ghz radio to an uncrowded fixed channel (as opposed to auto channel). Try setting your wireless to 20mhz only instead of 20/40 or 40. Use the default of AES encryption.

There are mobile smart phone radio channel scan tools for Android (I like Wifi Analyzer for Android because it's really quick and simple to use) and iPhone that can help scan the channels for the best choice. Remember that Bluetooth devices...headsets...mice and keyboards, cordless phones, wireless alarm door...window...and motion sensors, and many other devices use the open 2.4Ghz band. Leakage from electronics...motherboards, electronic equipment, power supplies, power strips, power lines, microwave ovens, USB 3.0 devices, etc... can cause 2.4Ghz interference if your wireless router is in proximity to those devices. If changing to fixed channel doesn't help then try physically moving your router to a different location and/or mounting up higher (at least four to five feet from the floor)...wall mount the router if possible. You may find a location that doesn't have as much interference even if you don't know what nearby devices might be causing the problem. I prefer sideways wall mounting with antennas pointing sideways right or left as opposed to the standard mounting with the antennas pointing upward.

I have three RT-N66Us and all of them work perfectly on 2.4Ghz radio band. I did run into some nagging conflicts at one location due to interference on the 2.4Ghz band (I live in an area crowded with 2.4Ghz signals) but I solved the problems with the settings changes in the firmware settings and radio location changes I described above.

 

[rudolphna]

Yes, I have set to different channels. The problem is I doubt it's interference. Why? Because it has worked completely flawlessly for 3 months. And then all of a sudden, the 2.4Ghz band no longer works. Nothing has changed, same headset, same comptuers, same phone, same everything. That's why I'm so frustrated. 3 months of perfection, and then this happens. And I did downoload the latest firmware, reset to factory defaults, did a 30/30/30 reset, no change. The 2.4Ghz is completely unusable. I'm going to get Best buy to do a replacement under manufacturer warranty, but this whole thing is ridiculous, I shouldn't have to do it.

 

[mikeg]

You should PM CL-Jeremy from Asus who is a member here. One thing you could try is to look at this setting under Wireless - 3.4 GHz - Professional . Enhanced interference management . disable / enable.

Okay, I'm really getting ready to say screw it and be done. This is no joke, the 4th one I've had this EXACT SAME problem with in a row.

Including 3 from newegg, and one from Best Buy.

The very first one had this problem from day 1. Wired and 5Ghz work perfectly fine. 2.4Ghz unable to connect with any kind of security enabled. All channels, changed everything you can think of. With open network, you can connect, but latency is terrible, and bad packet loss, ie completely unusable. This is with 5 different devices. Laptops, desktop, smartphone. That one was immediately RMA'd.

The second one worked for about 2 weeks before the EXACT SAME problem developed. 3rd one lasted about a week. Then this most recent one, I bought from Best Buy. It's been absolutely perfect for almost 3 months. And this morning when I get up to go to work, everyone is complaining "The internet doesn't work!" Well I'll be damned, wired works. 5Ghz works. 2.4Ghz unable to connect. #&!@#&*!@#

I do not understand. I've tried flashing to the most recent firmware. I've tried EVERYTHING. 2.4Ghz just does not work. Windows computers do the "Windows was unable to connect to the network" android smartphones try to connect, and retry, and retry, in infinite cycle. If I change the SSID it briefly connects, and looks normal, but when you actually try to surf, it hangs, and then disconnects, and won't let you reconnect. Again, 5Ghz and wired both work perfectly.

This in the system log when this is happening. Terran is my laptop with Intel Centrino N-6230

Jan 13 22:03:33 miniupnpd[601]: HTTP listening on port 54400
Jan 13 22:03:33 miniupnpd[601]: Listening for NAT-PMP traffic on port 5351
Jan 13 22:03:34 kernel: eth1: received packet with own address as source address
Jan 13 22:03:36 dnsmasq-dhcp[505]: DHCPINFORM(br0) 192.168.1.99 54:04:a6:32:ce:53
Jan 13 22:03:36 dnsmasq-dhcp[505]: DHCPACK(br0) 192.168.1.99 54:04:a6:32:ce:53 ARCHON
Jan 13 22:03:38 dnsmasq-dhcp[505]: DHCPREQUEST(br0) 192.168.1.13 88:53:2e:c9:ea:ff
Jan 13 22:03:38 dnsmasq-dhcp[505]: DHCPACK(br0) 192.168.1.13 88:53:2e:c9:ea:ff Terran
Jan 13 22:03:45 dnsmasq-dhcp[505]: DHCPREQUEST(br0) 192.168.1.13 88:53:2e:c9:ea:ff
Jan 13 22:03:45 dnsmasq-dhcp[505]: DHCPACK(br0) 192.168.1.13 88:53:2e:c9:ea:ff Terran
Jan 13 22:04:00 dnsmasq-dhcp[505]: DHCPREQUEST(br0) 192.168.1.13 88:53:2e:c9:ea:ff
Jan 13 22:04:00 dnsmasq-dhcp[505]: DHCPACK(br0) 192.168.1.13 88:53:2e:c9:ea:ff Terran
Jan 13 22:04:04 dnsmasq-dhcp[505]: DHCPREQUEST(br0) 192.168.1.13 88:53:2e:c9:ea:ff
Jan 13 22:04:04 dnsmasq-dhcp[505]: DHCPACK(br0) 192.168.1.13 88:53:2e:c9:ea:ff Terran
Jan 13 22:04:12 dnsmasq-dhcp[505]: DHCPREQUEST(br0) 192.168.1.13 88:53:2e:c9:ea:ff
Jan 13 22:04:12 dnsmasq-dhcp[505]: DHCPACK(br0) 192.168.1.13 88:53:2e:c9:ea:ff Terran
Jan 13 22:04:37 dnsmasq-dhcp[505]: DHCPDISCOVER(br0) 192.168.1.13 88:53:2e:c9:ea:ff
Jan 13 22:04:37 dnsmasq-dhcp[505]: DHCPOFFER(br0) 192.168.1.13 88:53:2e:c9:ea:ff
Jan 13 22:04:37 dnsmasq-dhcp[505]: DHCPREQUEST(br0) 192.168.1.13 88:53:2e:c9:ea:ff
Jan 13 22:04:37 dnsmasq-dhcp[505]: DHCPACK(br0) 192.168.1.13 88:53:2e:c9:ea:ff Terran
Jan 13 22:04:43 dnsmasq-dhcp[505]: DHCPINFORM(br0) 192.168.1.13 88:53:2e:c9:ea:ff
Jan 13 22:04:43 dnsmasq-dhcp[505]: DHCPACK(br0) 192.168.1.13 88:53:2e:c9:ea:ff Terran
Jan 13 22:04:46 dnsmasq-dhcp[505]: DHCPINFORM(br0) 192.168.1.13 88:53:2e:c9:ea:ff
Jan 13 22:04:46 dnsmasq-dhcp[505]: DHCPACK(br0) 192.168.1.13 88:53:2e:c9:ea:ff Terran
Jan 13 22:05:44 notify_rc : restart_wireless
Jan 13 22:05:45 kernel: Ebtables v2.0 registered
Jan 13 22:05:45 kernel: device eth1 left promiscuous mode
Jan 13 22:05:45 kernel: br0: port 2(eth1) entering disabled state
Jan 13 22:05:45 kernel: device eth2 left promiscuous mode
Jan 13 22:05:45 kernel: br0: port 3(eth2) entering disabled state
Jan 13 22:05:46 kernel: wl_module_init: passivemode set to 0x0
Jan 13 22:05:46 kernel: eth1: Broadcom BCM4331 802.11 Wireless Controller 5.100.138.20
Jan 13 22:05:46 kernel: eth2: Broadcom BCM4331 802.11 Wireless Controller 5.100.138.20
Jan 13 22:05:46 kernel: device eth1 entered promiscuous mode
Jan 13 22:05:46 kernel: br0: port 2(eth1) entering listening state
Jan 13 22:05:46 kernel: br0: port 2(eth1) entering learning state
Jan 13 22:05:46 kernel: br0: topology change detected, propagating
Jan 13 22:05:46 kernel: br0: port 2(eth1) entering forwarding state
Jan 13 22:05:47 kernel: device eth2 entered promiscuous mode
Jan 13 22:05:47 kernel: br0: port 3(eth2) entering listening state
Jan 13 22:05:48 kernel: br0: port 3(eth2) entering learning state
Jan 13 22:05:48 kernel: br0: topology change detected, propagating
Jan 13 22:05:48 kernel: br0: port 3(eth2) entering forwarding state
Jan 13 22:05:49 dnsmasq-dhcp[505]: DHCPREQUEST(br0) 192.168.1.13 88:53:2e:c9:ea:ff
Jan 13 22:05:49 dnsmasq-dhcp[505]: DHCPACK(br0) 192.168.1.13 88:53:2e:c9:ea:ff Terran
Jan 13 22:05:52 notify_rc : restart_wireless


So something is happening here, and it keeps resetting the wireless apparently after connection attempts. How do I fix this? do I have to exchange it AGAIN? I mean, I don't understand, I don't mistreat it, it's up on the stand in a cool room.

Does anyone have any clue as to what is going on?

 

[SoCalReviews]

Yes, I have set to different channels. The problem is I doubt it's interference. Why? Because it has worked completely flawlessly for 3 months. And then all of a sudden, the 2.4Ghz band no longer works. Nothing has changed, same headset, same comptuers, same phone, same everything. That's why I'm so frustrated. 3 months of perfection, and then this happens. And I did download the latest firmware, reset to factory defaults, did a 30/30/30 reset, no change. The 2.4Ghz is completely unusable. I'm going to get Best buy to do a replacement under manufacturer warranty, but this whole thing is ridiculous, I shouldn't have to do it.

After reading your explanation about having the same problem occur with four different radios....Interference on the 2.4Ghz band is just what makes sense to me. I have three RT-N66Us and I could have taken any one of those three and without making the right changes to the settings...channel choice and minor changes to the location...mounting the router high on the wall...I could have duplicated the same 2.4Ghz interference problems I experienced with any one of those three routers. The interference I experienced also wasn't consistent. I could go for a week or a month or more while working perfectly and then I could suddenly experience problems. I knew the problem I was dealing with and I simply kept trying different fixed channels (in my case it was channel 1 that worked in my area) until I found the one that worked right. I am currently using the official Asus 3.0.0.4.260 firmware.

I believe part of the problem was due to my neighbor's routers automatically changing their channels into the 2.4Ghz band on or next to the same channel my router was set to...and it interfered with my router's broadcast...and then my router would auto change to a more crowded channel in the 2.4Ghz band. I know this happened because I could see my neighbor's router broadcasts with my Android Wifi Analyzer app. When I set the routers to a fixed channel that alone didn't solve the problem...I had to set it to the best fixed channel for my area or those same interference problems would show up again. For the last six months after I made those changes I have had practically zero problems on the 2.4Ghz band from interference.

This is why I would tell you that changing out the router to a new one would be the last thing I would recommend you do. While it's a possibility that you got four routers with broken 2.4Ghz radios there is a far greater possibility that you are simply dealing with interference issues from your environment, problems generated from an incompatible device or just wireless settings problems. Have you tried flashing with the latest Asus-Merlin firmware for the RT-N66U to see if that helps? The other option would be to try another brand/model router or the RT-AC66U and see if that works better in your location.

 

[RogerSC]

Have you used a tool like inSSIDer to look at who's doing what where on the 2.4 GHz. wireless band around you? It's a very helpful tool, shows all the wireless routers that might be interfering with yours, their relative signal strength, and the channel that they're using. You could try to find the least used channel (focus on 1,6, or 11), and see if that's better.

Just a thought, in case you hadn't already looked at the interference that you're up against. Of course, this doesn't show microwave ovens, cordless phones, baby monitors, etc., just neighboring wireless use.

 

[jsmiddleton4]

How are your 2.4 ghz radios setup in the clients?

In advanced settings.......

 

[ancan]

I registered to say that I have the *exact* same problem, except it's my first N66U. My Android devices keep "Connecting" forever without succeeding, and Windows give the same message that OP had. 5GHz works perfect, but 2.4GHz stopped working after about a week.

I live on the countryside, and have no neighbors within WiFi-range, so interference from them can be ruled out.

Have tried Merlin's latest firmware, and also the latest ASUS that was released yesterday, but same problem.

 

[TonyH]

Hi,
Are you sure the client side is A-OK. What is the WiFi card there?

 

[ancan]

Hi,
Are you sure the client side is A-OK. What is the WiFi card there?

several clients started to fail simultaneously. w7, Debian linux, android, iOS. I think that can be ruled out.

 

[SoCalReviews]

I registered to say that I have the *exact* same problem, except it's my first N66U. My Android devices keep "Connecting" forever without succeeding, and Windows give the same message that OP had. 5GHz works perfect, but 2.4GHz stopped working after about a week.

I live on the countryside, and have no neighbors within WiFi-range, so interference from them can be ruled out.

Have tried Merlin's latest firmware, and also the latest ASUS that was released yesterday, but same problem.

I have three RT-N66Us I purchased at different times from different vendors last year. They run are running official .270 firmware at the moment. They have been running 24/7 for about 7-8 months. Never have to reboot these routers except for settings changes and firmware updates. I haven't rebooted at all in a month and a half. I live in a very high traffic area for the 2.4Ghz band....at least twelve other broadcasts. Two of my RT-N66Us have had up to thirty clients...of all types iPhone, iPads, Android pads and phones, Windows PC notebooks, etc... connected at at 2.4Ghz... at the same time...along with PS3 gaming and multiple HD streams, Slingbox, etc... on a 100Mbps down internet connection. No problems.

These are the most stable, solid and best performing wireless routers I have used since my WRT-54G routers were running. On Amazon this router has a hundreds of 5 star ratings...with the average rating at 4.5. I just don't get all these selective reported problems with customers returning them once, twice and more as if the router is absolutely at fault every time. I am not saying that these are not real problems that are occurring. I am just questioning that the router is always the problem. Unless there was a really bad manufacturing run that hits the same customers then it makes no sense at all. Signal interference and compatibility issues with one or more client wireless devices are what I would look at. If you have to set the RT-N66U to wireless g only mode and 20mhz bandwidth, AES encryption only and fix it to an open 2.4Ghz channel (don't use auto channel) to ensure compatibility with the clients then that's what I would recommend.

 

[TonyH]

Hi,
It is hard to believe 4 routers in a row is giving trouble like that. I would just deal with one client while all others radio is turned off, one at a time to see if it makes any difference.
Also inSSIDer will show what's going on in your neighborhood on that band. Some problems
often defies logic.

 

[ChrisR]

It is a good idea to turn off all devices and test one by one.
Note that I faced similar issue using my bluetooth headset. My laptop was working ok for weeks, after it suddenly could not connect to 2.4 anymore. Using 5 was no problem.
Only when I switched off the bluetooth of my headset, the 2.4 connected immediately.

Therefore, turn off bluetooth for each device, make sure your microwave and home telephone devices are also switched off. None of these devices should be close to your router.

Edit: more tests: turn off all Household devices. Put your router at another place in the house. Last test: take your router/laptop to family/friends and check if problem still exists...

Good luck!

 

[ancan]

It is a good idea to turn off all devices and test one by one.
Note that I faced similar issue using my bluetooth headset. My laptop was working ok for weeks, after it suddenly could not connect to 2.4 anymore. Using 5 was no problem.
Only when I switched off the bluetooth of my headset, the 2.4 connected immediately.

Therefore, turn off bluetooth for each device, make sure your microwave and home telephone devices are also switched off. None of these devices should be close to your router.

Edit: more tests: turn off all Household devices. Put your router at another place in the house. Last test: take your router/laptop to family/friends and check if problem still exists...

Good luck!

I found the culprit in my case, and it was kind of obscure. (Note that I am not the OP that had returned four routers for the same problem).

I have managed to connect to the 2.4GHz network now and then, but pinging the router gives a very flaky connection, and response times around 1000-2000ms. Browsing the web on that is not remotely possible.

Turning of equipment all around the house did absolutely nothing, and since the closest neighbor is 300m away the WiFi-space is far from crowded. Strongest other WiFi is at -92dB. Also, my previous 801.11n-routers has worked perfect, but I needed longer range to reach my new guesthouse.

I then moved the router from the closet it's been in, to the living room, and suddenly the 2.4GHz worked again! I put it back in the closet... and it still worked.

Now, I run the router in "AP Mode" since I have a Debian-based router I'm very satisfied with. Since the ports on the N66U falls back to working as a simple switch I took the oppurtunity to plug in the printer besides it, and this turned out to be what caused all the problems. When I plugged in the printer again, the ping latency rocketed to the thousands, and when I unplugged it, it went down to 3-4ms.

The printer is connected via an arcane printer server, so old that it only have 10Mb network (at the side of the RJ45, it even sports a BNC-connector for 10BASE2). For *some reason* plugging this in the ASUS completely crippled the 2.4GHz network, and for some other reason also did nothing bad to the 5GHz-part.
I don't know if it's because it's a 10Mb device, if it's because the print server puts out some nasty noise on the network cable, or if any device plugged in the ports will do the same. It would be interesting to know, but right now I'm too tired to test it. Also, I'm very happy because I wanted to keep this router.