Jump to content

'dhcps Lease host name not found' issue 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]Send OFFER with ip 192.168.0.103.
52 WARNING 0days, 00:01:55, [dhcps]Lease host name not found.
53 INFO 0days, 00:01:55, [dhcps]Send ACK to 192.168.0.103.
54 WARNING 0days, 00:34:46, [dhcps]Lease host name not found.
55 INFO 0days, 00:34:46, [dhcps]Send OFFER with ip 192.168.0.103.
56 WARNING 0days, 00:34:47, [dhcps]Lease host name not found.
57 INFO 0days, 00:34:47, [dhcps]Send ACK to 192.168.0.103.
58 WARNING 0days, 01:00:15, [dhcps]Lease host name not found.
59 INFO 0days, 01:25:18, [dhcps]Send OFFER with ip 192.168.0.100.
60 INFO 0days, 01:25:19, [dhcps]Send ACK to 192.168.0.100.
61 WARNING 0days, 01:34:48, [dhcps]Lease host name not found.
62 INFO 0days, 01:58:26, [dhcps]Send OFFER with ip 192.168.0.100.
63 INFO 0days, 01:58:27, [dhcps]Send ACK to 192.168.0.100.
64 WARNING 0days, 02:00:15, [dhcps]Lease host name not found.
65 WARNING 0days, 02:34:49, [dhcps]Lease host name not found.
66 WARNING 0days, 03:00:17, [dhcps]Lease host name not found.
67 WARNING 0days, 03:34:49, [dhcps]Lease host name not found.
68 INFO 0days, 03:55:20, [dhcps]Send OFFER with ip 192.168.0.100.
69 INFO 0days, 03:55:20, [dhcps]Send ACK to 192.168.0.100.
70 WARNING 0days, 04:00:17, [dhcps]Lease host name not found.
71 WARNING 0days, 04:34:50, [dhcps]Lease host name not found.
72 WARNING 0days, 05:00:18, [dhcps]Lease host name not found.

 

 

[Full System Logs Attached below]

 

My System Log is flooded with this message : [dhcps]Lease host name not found. It's happening with all the devices connected to the router. I've also noticed when it happens with an IP, the device with that IP looses internet connection for a short period of time like 30 seconds or sometimes even looses the WiFi signal. My DHCP setting is pretty basic without any modification to the defaults [image attached below]

 

IMG_20211005_002545.jpg.1c762ba1bf082af2067fcf0b33cbd5ff.jpg

 

Most of the time there's 5 to 6 devices connected. Sometimes there's 1 to 2. I have a computer which is connected via Ethernet. I'm not sure if the computer is effected by this. I've tried factory resetting the router and configuring it from scratch. But to no avail, The problem returned after some time later. I've also tried mailing TP LINK and they are yet to respond. Posted it on their forum and no replies so far.

 

My educated guess is the problem lies within the firmware or might be a bug. The problem is really really problematic when you need a stable connection. Please help me how to solve it if the problem is from my end.

 

 

Thanks in advance

 

 

syslog.txt syslog 2nd.txt

Link to comment
Share on other sites

Link to post
Share on other sites

4 minutes ago, Thriliya said:

My DHCP setting is pretty basic without any modification to the defaults [image attached below]

Not seeing any image.

Link to comment
Share on other sites

Link to post
Share on other sites

Just now, Falcon1986 said:

Not seeing any image.

Sorry about that. Just fixed it

Link to comment
Share on other sites

Link to post
Share on other sites

9 minutes ago, Thriliya said:

Sorry about that. Just fixed it

What ISP device is the C24 connected to?

Link to comment
Share on other sites

Link to post
Share on other sites

I'm not sure about that. But I guess it's a DSL modem as my connection type is PPPoE.

 

IMG_20211006_015436.thumb.jpg.f2efe9736bd1c8457f8a05d508717ca1.jpg

 

Link to comment
Share on other sites

Link to post
Share on other sites

47 minutes ago, Thriliya said:

Please help me how to solve it if the problem is from my end.

I see you've been posting the same problem on several other forums.

  • Is the problem occurring if you set a static LAN IP on the client device? Make sure it's outside of the DHCP pool.
  • What if you increase the lease time to 1 day (1440 minutes)?
  • Try reverting to a previous firmware prior to the latest if the router allows.
  • Set the primary and secondary DNS to Google's (8.8.8.8, 8.8.4.4).

I don't see any 3rd-party compatible firmware from DD-WRT or OpenWRT so there's likely no hope in fixing if it is a firmware problem. The only solution would be to get a new router.

Link to comment
Share on other sites

Link to post
Share on other sites

11 minutes ago, Falcon1986 said:

I see you've been posting the same problem on several other forums.

Yes. I am in the hope of finding a solution.

 

11 minutes ago, Falcon1986 said:
  • Is the problem occurring if you set a static LAN IP on the client device? Make sure it's outside of the DHCP pool.
  • What if you increase the lease time to 1 day (1440 minutes)?
  • Try reverting to a previous firmware prior to the latest if the router allows.
  • Set the primary and secondary DNS to Google's (8.8.8.8, 8.8.4.4).

I've yet to try 1,2,3. but I've tried the number 4 before and it didn't work. Thank you. I'll post the update after trying 1-3

 

11 minutes ago, Falcon1986 said:

I don't see any 3rd-party compatible firmware from DD-WRT or OpenWRT so there's likely no hope in fixing if it is a firmware problem. The only solution would be to get a new router.

Unfortunately I've no other option than to buy a new router or hope the company will fix the bug and release a new firmware.

 

 

Thanks again for the help. I'll post update

Link to comment
Share on other sites

Link to post
Share on other sites

9 minutes ago, Thriliya said:

or hope the company will fix the bug and release a new firmware.

Good luck with this one. I wouldn't hold my breath.

 

The Archer C24 is a AC750 class wireless router in TP-Link's budget line. It's unlikely to get fixed with an update. They'll most likely recommend that you buy another router as a "fix".

Link to comment
Share on other sites

Link to post
Share on other sites

On 10/6/2021 at 7:16 PM, Thriliya said:

Is the problem occurring if you set a static LAN IP on the client device? Make sure it's outside of the DHCP pool.

I've set all the LAN devices to static. And it seems to fix the issue temporarily at least for now.

 

On 10/6/2021 at 7:16 PM, Thriliya said:

What if you increase the lease time to 1 day (1440 minutes)?

Will go okay for about 12 hours and then the issue will appear with the respective IP.

 

On 10/6/2021 at 7:30 PM, Falcon1986 said:

They'll most likely recommend that you buy another router as a "fix".

Seems like the only option I have. 😞

Their after sale service is the worst

 

Thanks again for the help

Link to comment
Share on other sites

Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

×