Archer C6 2.4G band stops working, disable then enable restores
Recently purchased Archer C6 Router running the latest firmware. On 4 occasions the 2.4G WiFi band has stopped working, devices can connect to it but get no network access. Disabling and enabling the 2.4G band on the admin interface restores the connectivity, the 5G band is not affected, a device connected to it is used to reset the 2.4G band.
I used the chat support service to discuss the issue and the suggestion was to change from automatic to a fixed channel for the 2.4G band, this appeared to resolve the issue but it has happened again today, a phone which only works on 2.4G was showing the WIFI as access denied.
is there anything else I can do to resolve this issue.
StuartP
- Copy Link
- Subscribe
- Bookmark
- Report Inappropriate Content
I cant recommend 1.3.0, it has the fixed channel bug. When you reboot it comes up with a fixed 2.4 GHz channel,, not the one which you have saved.
What happens, when you set fix 20mhz, wpa2, aes and channel on 2.4 GHz ?
1.3.4 is not available per download, it was removed. But i find it very good.
1.3.5 can also be used.
Also try to set it to factory default and reconfigure it per hand.
- Copy Link
- Report Inappropriate Content
I tried your recommendation setings, which didn't solve the problem:
When I bought C6 I suppose there was 1.3.4 and it worked OK, then I upgraded it to 1.3.5 which caused 2.4 GHz problem and remained with 1.3.5.
Does anybody has 1.3.4 version firmware for C6 V2 EU to download?
- Copy Link
- Report Inappropriate Content
The only viable solution to this problem is to get yourself an Asus or Netgear Router because unlike these incompetent morons at TP-Link, Netgear and Asus atleast has decent customer support to atleast try and fix the issue for you. Not to mention, I used Netgear router for years and lots of firmware updates but never had a single problem like this.
- Copy Link
- Report Inappropriate Content
@Kubas The problem may be there in the size of flash memory, when they implemented the functions One Mesh, Alexa Support, WPA3 Protocol Support and UPNP Lookback Function Support, must have compromised the equipment system, the American summer is with firmware 1.1.5 build 20191112 and working normally here for me, only the European version that presents this problem of the 2.4g network.
- Copy Link
- Report Inappropriate Content
@Kevin_Z If possible I wanted to exchange my router Archer C6 v2.0 (EN), for a same version (US), because all users of the version with flash memory of 8MB just as I'm having problems on the 2.4g network.
- Copy Link
- Report Inappropriate Content
Here, if you want it from me...
But i see your chromebook gets connection but no dataflow ?
Or is it disconnecting right after connect ?
ok, i see you have upnp enabled ? Do you need it ? I`ve also disabled this...
- Copy Link
- Report Inappropriate Content
Thank you for 1.3.4, but unfortunately 2.4 GHz still doesn't work. I also disabled upnp but still nothing.
Yes, Chromebook is seen by router for some seconds - "Received packets"=0 (Wireless Statistics) and then disappears from list.
I would like to test also older official firmwares if somebody has it.
- Copy Link
- Report Inappropriate Content
Ok, just want to help.
To go below 1.3.x you have to go the OpenWRT way. You cant flash 1.2.1 thru the webpage if you have 1.3.x on the router.
And there is a nice chance to brick your C6 and i can`t help you this way.
I´ve posted BETA 1.3.1 a few pages back, it has reverted the wireless changes made to 1.3.0, if you want test this.
- Copy Link
- Report Inappropriate Content
Lucasm wrote
@Kubas The problem may be there in the size of flash memory, when they implemented the functions One Mesh, Alexa Support, WPA3 Protocol Support and UPNP Lookback Function Support, must have compromised the equipment system, the American summer is with firmware 1.1.5 build 20191112 and working normally here for me, only the European version that presents this problem of the 2.4g network.
Please, read this thread from the very first post. The router had this problem from the initial firmware release - long time before those functions were introduced. The bug is related to encryption and some specific circumstance that they are trying to trace right now.
- Copy Link
- Report Inappropriate Content
@Wetterhahn No, the problem appeared in 1.3.x. Prior firmwares were ok. I have been using this router intensively 5 months before the 1.3.x distaster.
- Copy Link
- Report Inappropriate Content
Information
Helpful: 5
Views: 122968
Replies: 580