Error message appears when accessing the lease host name on Archer C24.
Error message appears when accessing the lease host name on Archer C24.
Model: TP-Link Archer C24 Hardware Version: V1 (US) Firmware Version: 1.4.3 Build 201022 Rel.55840n(5553) 51 INFO 0days, 00:01:55, [dhcps]Transmit offer to 192.168.0.103. 52 WARNING 0days, 00:01:55, [dhcps]Host name lease not detected. 53 INFO 0days, 00:01:55, [dhcps]Reply to 192.168.0.103. 54 WARNING 0days, 00:34:46, [dhcps]Host name lease not found again. 55 INFO 0days, 00:34:46, [dhcps]Send ACK to 192.168.0.103. 56 WARNING 0days, 00:34:47, [dhcps]Lease host name still missing. 57 INFO 0days, 00:34:47, [dhcps]Transmit offer to 192.168.0.100. 58 WARNING 0days, 01:00:15, Host name lease not found again. 59 INFO 0days, 01:25:18, Offer sent to 192.168.0.100. 60 INFO 0days, 01:25:19, ACK dispatched to 192.168.0.100. 61 WARNING 0days, 01:34:48, Host name lease not found once more. 62 INFO 0days, 01:58:26, Offer sent to 192.168.0.100. 63 INFO 0days, 01:58:27, ACK delivered to 192.168.0.100. 64 WARNING 0days, 02:00:15, Host name lease missing. 65 WARNING 0days, 02:34:49, Host name lease missing. 66 WARNING 0days, 03:00:17, Host name lease missing. 67 WARNING 0days, 03:34:49, Host name lease missing. 68 INFO 0days, 03:55:20, Offer sent to 192.168.0.100. 69 INFO 0days, 03:55:20, ACK sent to 192.168.0.100. 70 WARNING 0days, 04:00:17, Host name lease missing. 71 WARNING 0days, 04:34:50, Host name lease missing. 72 WARNING 0days, 05:00:18, Host name lease missing. Full system logs attached below] My system logs are overflowing with this alert: [dhcps]Lease host name not found. It occurs across all devices linked to the router. When using a specific IP, the connected device temporarily loses internet access for about 30 seconds or even drops its Wi-Fi signal. My DHCP configuration is quite basic and hasn’t been changed from defaults [image attached]. Most connections sit between five and six devices. Occasionally it’s just one or two. I own a computer linked via Ethernet; I’m uncertain if it’s affected. I attempted a factory reset and set it up anew, but the issue persists after some time. I’ve also reached out to TP-Link support via email, but they haven’t replied. Posted my case on their forum without receiving any answers. My suspicion is that the issue may stem from the firmware or could be a bug. It’s a serious concern when stability is essential. Please assist if the problem originates from your side. Thanks for your help. syslog.txt syslog 2nd.txt"
I configured all LAN devices as static, which appears to resolve the problem temporarily. It should last around 12 hours before the issue reappears with the assigned IP. This seems to be the only solution available. Their post-sale support is quite poor—thank you for your assistance.