Archer AX55 (v1.3.3) – DHCP Renew Fails Every 10 Minutes
Hi,
I'm facing a serious issue with the Archer AX55 (v1.0) on firmware v1.3.3.
Every 10 minutes, the router fails to renew its DHCP lease, forcing a full re-lease cycle. Here's the technical behavior:
-
Gets IP via DHCP with 600s lease time
-
Sends DHCPREQUEST after 5 mins — no reply
-
Router falls back to DHCPDISCOVER, reconnects
-
During this time, internet briefly drops for all clients
-
PC connected directly to modem works fine — confirms ISP is NOT the issue
Tried:
-
Firmware update
-
MAC clone
-
Cable replacement
-
DNS change
-
Changing DHCP settings
-
Factory reset
Still the issue persists.
This is clearly a firmware DHCP client bug. TP-Link chat support only gives generic replies and won’t escalate. Live agent is never available.
➡️ Is this a known issue?
➡️ Anyone else seeing this?
➡️ TP-Link: Please escalate to engineering or confirm if fix is planned.
Attached: Log excerpts showing renew → timeout → discover cycle.
Thanks.
- Copy Link
- Subscribe
- Bookmark
- Report Inappropriate Content
Hi@Alladyn47,
Thank you for contacting our community.
This firmware version has been released in last year. We haven't received the similar feedback as yours. May I know, did the issue start after you update the firmware?
Did you reset the router via pressing the reset hole until the Power LED blinks to reset the router to its factory default settings?
Try to do Mac clone for your router if your PC doesn't have the issue:How do I configure MAC Address Clone on my TP-Link Archer Router?
Is there any error message? If yes, please take screenshots and send here. Please also take screenshots with DHCP server interface;
- Copy Link
- Report Inappropriate Content
Thank you for your responses. I would like to provide some clarification on these troubleshooting steps and the actual solutions to the issues.
However, your responses suggested the same steps (e.g. cloning the MAC address, resetting the router) that I described in my post, which is a bit unfortunate. The underlying issue lies in the DHCP client implementation in firmware version 1.3.3, as evidenced by the logs showing repeated DHCPREQUEST timeouts and falling back to DHCPDISCOVER.
The issue was finally resolved by manually downloading and reinstalling the firmware (v1.3.3, build 20240628) from the official TP-Link download center
This suggests that the standard update/reset process may not completely resolve some firmware related issues.
Since this error is very concisely related to the DHCP client firmware (albeit rare), I recommend:
Document this case for the next firmware release.
Test the DHCP lease renewal behavior in 1.3.3 under similar conditions.
Conclusion
While I appreciate your efforts, the support replies did not address the technical details of my messages. The solution was a manual firmware reinstall, which your team did not suggest. Hopefully this feedback will help improve future processes, troubleshooting.
- Copy Link
- Report Inappropriate Content
Hi@Alladyn47,
Thank you for contacting our community.
This firmware version has been released in last year. We haven't received the similar feedback as yours. May I know, did the issue start after you update the firmware?
Did you reset the router via pressing the reset hole until the Power LED blinks to reset the router to its factory default settings?
Try to do Mac clone for your router if your PC doesn't have the issue:How do I configure MAC Address Clone on my TP-Link Archer Router?
Is there any error message? If yes, please take screenshots and send here. Please also take screenshots with DHCP server interface;
- Copy Link
- Report Inappropriate Content
i am having the same issue. My Archer AX55 v1 just randomly drops the wan connection and tells me that the wan is not connected or that I am having a bad internet connection. I tried a direct connection from modem to pc and it was working fine all the time. This happened like last month and I tried every solution but nothing helped me out.
2025-06-20 22:50:09 NAT INFORMATION [10464] Initialization succeeded
2025-06-20 22:50:08 NAT INFORMATION [10464] Initialization succeeded
2025-06-20 22:49:59 UPnP INFORMATION [9129] Service start
2025-06-20 22:49:59 UPnP INFORMATION [9129] Service stop
2025-06-20 22:49:56 Fernwartung INFORMATION [8608] Service stop
2025-06-20 22:49:46 QoS INFORMATION [7688] Service start
2025-06-20 22:49:46 QoS INFORMATION [7688] Function disabled
2025-06-20 22:49:46 QoS INFORMATION [7688] Service stop
2025-06-20 22:49:43 NAT INFORMATION [7163] Initialization succeeded
2025-06-20 22:49:42 NAT INFORMATION [7163] Initialization succeeded
2025-06-20 22:49:37 DHCPC INFORMATION [6340] receive ack from server with ip 62.240.xxx.xxx, options(serverid=62.240.xxx.xxx;lease=86400;subnet=255.255.255.252;dns=172.20.168.1 62.240.xxx.xxx 62.240.xxx.xxx;router=62.240.xxx.xxx;)
2025-06-20 22:49:37 DHCPC INFORMATION [6340] send select request with options(cliid=01/3c:64:cf:ae:a3:31:;reqip=62.240.xxx.xxx;serverid=62.240.xxx.xxx;)
2025-06-20 22:49:37 DHCPC INFORMATION [6340] receive offer from server with ip 62.240.xxx.xxx, options(serverid=62.240.xxx.xxx;lease=86400;subnet=255.255.255.252;dns=172.20.168.1 62.240.xxx.xxx 62.240.xxx.xxx;router=62.240.xxx.xxx;)
2025-06-20 22:49:36 NAT INFORMATION [6103] Initialization succeeded
2025-06-20 22:49:35 NAT INFORMATION [6103] Initialization succeeded
2025-06-20 22:49:34 DHCPC INFORMATION [6340] send discover with ip 0.0.0.0 and flags 80
2025-06-20 22:49:34 Trafficstatistiken INFORMATION [13408] stats reset
2025-06-20 22:49:34 Netz INFORMATION [5948] Reload config
2025-06-20 22:49:32 DHCPC WARNUNG [21160] send dhcp release ip 62.240.xxx.xxx
2025-06-20 22:49:32 DHCPC INFORMATION [21160] teardown and release
2025-06-20 22:49:32 Netz INFORMATION [5948] Disconnect interface wan
2025-06-20 22:49:30 Netz INFORMATION [5948] Disconnect interface internet
2025-06-20 22:49:29 Netz INFORMATION [5948] Set WAN protocol to dhcp, operation is write
2025-06-20 22:44:59 UPnP INFORMATION [23357] Service start
2025-06-20 22:44:59 UPnP INFORMATION [23357] Service stop
2025-06-20 22:44:57 Fernwartung INFORMATION [22933] Service stop
2025-06-20 22:44:46 QoS INFORMATION [22142] Service start
2025-06-20 22:44:46 QoS INFORMATION [22142] Function disabled
2025-06-20 22:44:46 QoS INFORMATION [22142] Service stop
2025-06-20 22:44:45 LED-Controller INFORMATION [1111] Start to run WAN1_ON
2025-06-20 22:44:45 LED-Controller INFORMATION [1111] Start to run WAN0_OFF
2025-06-20 22:44:44 LED-Controller INFORMATION [1111] Start to run LAN_ON
2025-06-20 22:44:44 NAT INFORMATION [21597] Initialization succeeded
2025-06-20 22:44:43 NAT INFORMATION [21597] Initialization succeeded
2025-06-20 22:44:39 DHCPC INFORMATION [21160] receive ack from server with ip 62.240.xxx.xxx, options(serverid=62.240.xxx.xxx;lease=86400;subnet=255.255.255.252;dns=172.20.168.1 62.240.xxx.xxx 62.240.xxx.xxx;router=62.240.xxx.xxx;)
2025-06-20 22:44:39 DHCPC INFORMATION [21160] send select request with options(cliid=01/3c:64:cf:ae:a3:31:;reqip=62.240.154.89;serverid=62.240.xxx.xxx;)
2025-06-20 22:44:39 DHCPC INFORMATION [21160] receive offer from server with ip 62.240.xxx.xxx, options(serverid=62.240.xxx.xxx;lease=86400;subnet=255.255.255.252;dns=172.20.168.1 62.240.xxx.xxx 62.240.xxx.xxx;router=62.240.xxx.xxx;)
2025-06-20 22:44:36 DHCPC INFORMATION [21160] send discover with ip 0.0.0.0 and flags 80
2025-06-20 22:44:35 LED-Controller INFORMATION [1111] Start to run WAN1_OFF
2025-06-20 22:44:35 LED-Controller INFORMATION [1111] Start to run WAN0_ON
2025-06-20 22:44:35 LED-Controller INFORMATION [1111] Start to run LAN_ON
2025-06-20 22:44:33 DHCPC INFORMATION [21160] send discover with ip 0.0.0.0 and flags 80
2025-06-20 22:44:31 DHCPC INFORMATION [20564] teardown and release
2025-06-20 22:44:31 DHCPC INFORMATION [20564] send discover with ip 0.0.0.0 and flags 80
2025-06-20 22:44:31 LED-Controller INFORMATION [1111] Start to run WAN1_OFF
2025-06-20 22:44:31 LED-Controller INFORMATION [1111] Start to run WAN0_OFF
2025-06-20 22:44:31 LED-Controller INFORMATION [1111] Start to run LAN_ON
2025-06-20 22:44:29 LED-Controller INFORMATION [1111] Start to run WAN1_ON
2025-06-20 22:44:29 LED-Controller INFORMATION [1111] Start to run WAN0_OFF
2025-06-20 22:44:29 LED-Controller INFORMATION [1111] Start to run LAN_ON
2025-06-20 22:44:29 LED-Controller INFORMATION [1111] Start to run WAN1_OFF
2025-06-20 22:44:29 LED-Controller INFORMATION [1111] Start to run WAN0_ON
2025-06-20 22:44:29 LED-Controller INFORMATION [1111] Start to run LAN_ON
2025-06-20 22:44:28 DHCPC INFORMATION [20564] send discover with ip 0.0.0.0 and flags 80
2025-06-20 22:44:27 NAT INFORMATION [20189] Initialization succeeded
2025-06-20 22:44:27 NAT INFORMATION [20189] Initialization succeeded
2025-06-20 22:44:26 LED-Controller INFORMATION [1111] Start to run WAN1_OFF
2025-06-20 22:44:26 LED-Controller INFORMATION [1111] Start to run WAN0_OFF
2025-06-20 22:44:26 LED-Controller INFORMATION [1111] Start to run LAN_ON
2025-06-20 22:44:25 DHCPC WARNUNG [9809] send dhcp release ip 62.240.xxx.xxx
2025-06-20 22:44:25 DHCPC INFORMATION [9809] teardown and release
- Copy Link
- Report Inappropriate Content
Hi @Selooo,
Welcome to our community.
For your issue, please try the following suggestions:
1) Connect a PC directly to your modem to verify if your ISP's Internet is stable. 2) Ensure the Ethernet cable connecting your modem to the Router is properly connected, and replace old wires with new ones.
3) Change the DNS Server of the Router, log in to the web management interface of the Router, go to Advanced > Network > Internet > Advanced Settings, and change the two DNS Servers to 1.1.1.1 and 8.8.8.8. How to Change the DNS servers on the wireless router and DSL modem router (New UI)?
4) Try the pre-release firmware of Archer AX55_V1: Archer AX55 V1 Supports Extending Guest Network via EasyMesh and Optimizing Performance in AP Mode
- Copy Link
- Report Inappropriate Content
Hi @Jospeh-TH I tried all the possibilities you gave me but I didn’t had any success. My Router is still closing the wan connection constantly. I have to restart my Router like 3-4 times a day to get my Internet back
- Copy Link
- Report Inappropriate Content
Hi@Selooo,
Thank you for getting back to me.
Please help collect the following information and send it to support.forum@tp-link.com, attaching [Forum ID 815400] and the details. We will then assign a dedicated person to assist with analysis and follow-up.
- The date when you bought the router.
- ISP name and connection type.
- Dropping frequency of the clients.
- Can it restore the connection automatically after a few minutes? Or is the restart necessary?
- Save the system log and double-check the network stability of the front-end modem/router.
Please refer to the FAQs below to collect system logs of the router: How to view and save System Log of TP-Link wireless router.
Note: The system log will be cleared if the router is restarted. Therefore, please collect the logs before restarting the router to restore Internet access.
- Copy Link
- Report Inappropriate Content
Thank you for your responses. I would like to provide some clarification on these troubleshooting steps and the actual solutions to the issues.
However, your responses suggested the same steps (e.g. cloning the MAC address, resetting the router) that I described in my post, which is a bit unfortunate. The underlying issue lies in the DHCP client implementation in firmware version 1.3.3, as evidenced by the logs showing repeated DHCPREQUEST timeouts and falling back to DHCPDISCOVER.
The issue was finally resolved by manually downloading and reinstalling the firmware (v1.3.3, build 20240628) from the official TP-Link download center
This suggests that the standard update/reset process may not completely resolve some firmware related issues.
Since this error is very concisely related to the DHCP client firmware (albeit rare), I recommend:
Document this case for the next firmware release.
Test the DHCP lease renewal behavior in 1.3.3 under similar conditions.
Conclusion
While I appreciate your efforts, the support replies did not address the technical details of my messages. The solution was a manual firmware reinstall, which your team did not suggest. Hopefully this feedback will help improve future processes, troubleshooting.
- Copy Link
- Report Inappropriate Content
funny or not, I use the TP-Link TL-ER7206 v1 and on Sept 25, I had to reboot that device as the internet had failed and since then, I have an internet drop every 10 min.
did some digging and it seems that the router requests a new IP via DHCP exactly at that time, every 10 min, first round it always fails and the second request goes, causing a min internet connectivity drop.
i find it interesting that you had that same 10 min interval and the same symptoms.
i have since manually loaded the next firmware version but my troubles remain...
- Copy Link
- Report Inappropriate Content
Information
Helpful: 0
Views: 565
Replies: 7
Voters 0
No one has voted for it yet.