DHCPS Lease hostname not found
This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
SysLog:
1 WARNING 0days, 03:03:52, [dhcps]Lease host name not found.
2 WARNING 0days, 03:22:45, [dhcps]Lease host name not found.
3 WARNING 0days, 05:09:20, [dhcps]Lease host name not found.
4 WARNING 0days, 05:12:23, [dhcps]Lease host name not found.
5 WARNING 0days, 05:35:19, [dhcps]Lease host name not found.
6 WARNING 0days, 05:53:15, [dhcps]Lease host name not found.
7 WARNING 0days, 06:03:52, [dhcps]Lease host name not found.
8 INFO 0days, 06:24:38, [dhcps]Send OFFER with ip 192.168.0.2.
9 INFO 0days, 06:24:38, [dhcps]Send ACK to 192.168.0.2.
10 WARNING 0days, 07:37:09, [dhcps]Lease host name not found.
11 WARNING 0days, 07:48:09, [dhcps]Lease host name not found.
12 WARNING 0days, 08:14:29, [dhcps]Lease host name not found.
13 INFO 0days, 08:14:29, [dhcps]Send OFFER with ip 192.168.0.3.
14 WARNING 0days, 08:14:30, [dhcps]Lease host name not found.
15 INFO 0days, 08:14:30, [dhcps]Send ACK to 192.168.0.3.
16 WARNING 0days, 09:03:53, [dhcps]Lease host name not found.
17 WARNING 0days, 10:45:38, [dhcps]Lease host name not found.
18 WARNING 0days, 11:15:06, [dhcps]Lease host name not found.
19 WARNING 0days, 11:15:07, [dhcps]Lease host name not found.
20 WARNING 0days, 12:03:53, [dhcps]Lease host name not found.
21 WARNING 0days, 13:25:29, [dhcps]Lease host name not found.
22 WARNING 0days, 14:47:29, [dhcps]Lease host name not found.
23 WARNING 0days, 14:59:32, [dhcps]Lease host name not found.
24 WARNING 0days, 15:03:54, [dhcps]Lease host name not found.
25 WARNING 0days, 15:16:03, [dhcps]Lease host name not found.
26 WARNING 0days, 15:42:32, [dhcps]Lease host name not found.
27 WARNING 0days, 15:59:40, [dhcps]192.168.0.2 belongs to someone, reserving it for 3600 seconds.
28 WARNING 0days, 15:59:40, [dhcps]Lease host name not found.
29 INFO 0days, 15:59:40, [dhcps]Send OFFER with ip 192.168.0.3.
30 WARNING 0days, 15:59:41, [dhcps]Lease host name not found.
31 INFO 0days, 15:59:41, [dhcps]Send ACK to 192.168.0.3.
32 INFO 0days, 16:24:27, [dhcps]Send OFFER with ip 192.168.0.111.
33 INFO 0days, 16:24:27, [dhcps]Send OFFER with ip 192.168.0.111.
34 WARNING 0days, 16:24:28, [dhcps]Lease host name not found.
35 INFO 0days, 16:24:28, [dhcps]Send ACK to 192.168.0.111.
36 WARNING 0days, 16:24:28, [dhcps]Lease host name not found.
37 INFO 0days, 16:24:28, [dhcps]Send ACK to 192.168.0.111.
38 INFO 0days, 17:33:32, [dhcps]Send OFFER with ip 192.168.0.100.
39 INFO 0days, 17:33:33, [dhcps]Send ACK to 192.168.0.100.
40 WARNING 0days, 18:03:55, [dhcps]Lease host name not found.
41 INFO 0days, 19:13:47, [dhcps]Send OFFER with ip 192.168.0.111.
42 INFO 0days, 19:13:48, [dhcps]Send OFFER with ip 192.168.0.111.
43 WARNING 0days, 19:13:49, [dhcps]Lease host name not found.
44 INFO 0days, 19:13:49, [dhcps]Send ACK to 192.168.0.111.
45 WARNING 0days, 19:13:49, [dhcps]Lease host name not found.
46 INFO 0days, 19:13:49, [dhcps]Send ACK to 192.168.0.111.
47 WARNING 0days, 19:41:31, [dhcps]Lease host name not found.
48 WARNING 0days, 20:52:36, [dhcps]192.168.0.2 belongs to someone, reserving it for 3600 seconds.
49 INFO 0days, 20:52:37, [dhcps]Send OFFER with ip 192.168.0.4.
50 INFO 0days, 20:52:38, [dhcps]Send ACK to 192.168.0.4.
51 WARNING 0days, 21:03:55, [dhcps]Lease host name not found.
52 WARNING 0days, 21:10:04, [dhcps]Lease host name not found.
53 INFO 0days, 21:20:23, [dhcps]Send OFFER with ip 192.168.0.5.
54 INFO 0days, 21:20:24, [dhcps]Send ACK to 192.168.0.5.
55 WARNING 0days, 21:51:56, [dhcps]Lease host name not found.
56 WARNING 0days, 21:56:19, [dhcps]Lease host name not found.
57 INFO 0days, 22:04:50, [dhcps]Send OFFER with ip 192.168.0.5.
58 INFO 0days, 22:04:51, [dhcps]Send ACK to 192.168.0.5.
59 INFO 0days, 22:07:43, [dhcps]Send OFFER with ip 192.168.0.5.
60 INFO 0days, 22:07:44, [dhcps]Send ACK to 192.168.0.5.
61 INFO 0days, 22:32:14, [dhcps]Send OFFER with ip 192.168.0.4.
62 INFO 0days, 22:32:15, [dhcps]Send ACK to 192.168.0.4.
100 is my PC. 111 is my Phone. Both are permanent. 5, 3 and 4 are other devices like Chromebooks and phones, these are not permanent leases..
On my PC when this happens I lose internet and every packet sent trying to ping the local gateway is lost. On my Android device, every time the router does the OFFER/ACK cycle I lose internet connection or the ability to log in at the router, despite the WiFi connection being intact. For Android, the solution is to disable and enable the WiFi function in order to regain access until the next OFFER/ACK cycle. On PC, I have yet to find a solution.
This problem occurred recently for PC, and while thinking it was the QoS being the culprit, I just went ahead and factory reset the router. Everything was fine for a day or so before the issues started showing up again.
This happens regardless if a device has a static local IP or dynamic. I don't understand why the router is running ACK/OFFER on permanent leased IPs, but it does. I don't understand why the host name isn't found either.
It appears this problem gets worse as time goes by, the router more often runs these commands and over the next 3 weeks I expect to have to factory reset again. I've done a lot of digging but every article/forum post pertaining to these symptoms either has no responses or the solution is to install DD-WRT on the router. Now I really like TP-LINK's GUI, much better than that of DD-WRT. But if that's the only way I can get a reliable DHCP server, then I will install it.
I'm hoping someone here has had a similar issue, or knows what causes these symptoms so that I can continue using this GUI.
@Kevin_Z Yes I have received an email. I've elaborated in a PM.
I received a reply from them, no solution yet. In the last 24 hours I've got 180 error reports/ ACK-OFFER cycles. It did start with about 10 when I factoiry reset 5 days ago. I will attach a syslog for you to compare if you'd like to see if your problem is the same as mine. However I was suggested to set up a manual IP on my LAN port. Regardless, I do think I was asked to do this in order remove the possibility of it being an issue with the Auto address fetcher. I would guess that if your IPv4 auto settings correctly get both your local IP, Gateway and Subnet Mask, manual setup won't do much, as it hasn't in my case.
Please ignore the last 30 lines in the syslog, those are from a WPS connection and don't pertain to this issue.
