Archer C4000 and C3200 - DHCP Server Fails after using Address Reservation
Archer C4000 and C3200 - DHCP Server Fails after using Address Reservation
Hardware Version :
Firmware Version :
ISP :
I previously had a C3200 and replaced with a C4000. On both units, when I reserve multiple IPs outside of the DHCP pool range for my LAN, DHCP stops working. All DHCP clients can no longer get an IP from the pool. When I disable the address reservations, the DHCP Client List once again floods with clients that have been unable to get an IP. All the sudden, they work again. This is the strangest thing. Toggling the DHCP server and power cycling the router have no effect. The only way to restore DHCP server function is to disable the address reservations for all but 1 client.
IP Pool: 192.168.101 - 192.168.1.199
Gateway: 192.168.1.1
Address Reservations for 192.168.1.2, 192.168.1.3, 192.168.1.5 and 192.168.1.50.
Static IPs are assigned to an iMac, MacBook Pro, a home built FreeBSD server and an IP Camera.
All other clients (27 of them) are assigned via DHCP, ranging from Chromecasts, to echo devices, iPads, kindles, etc..
Knowledge background: I've worked over 10 years at a major telco provider on Layer 2 / Layer 3 access network management (DSLAM/VDSL/PON) and have extensive knowledge of IP.
- Copy Link
- Subscribe
- Bookmark
- Report Inappropriate Content
@archerboy not sure if you are having the same problem, but there is a major design flaw of the Archer software. It will allow you to assign a name to reserved IP's with spaces in them. But the spaces will cause a DCHP error and will stop assigning IPs.
- Copy Link
- Report Inappropriate Content
Hardware Version : V2
Firmware Version : 1.0.3 Build 20180322 rel.2657(5553)
I'm having this *exact* same problem -- when I reserve multiple IPs outside of the DHCP pool range for my LAN, DHCP stops working. All DHCP clients can no longer get an IP from the pool. The only way to recover is to do a hard-reset.
I've contacted TP-Link Tech Support. In the meantime, I installed a DHCP server on my LAN and disabled the DHCP server on my Archer C4000. Pretty sad workaround for a higher-end router.
- Copy Link
- Report Inappropriate Content
The problem was that my Address Reservation hostnames had a space in them. They recommended not having special characters or spaces in the hostnames and then the DHCP server should work normally. It doesn't sound like they will post a revised firmware to do this check in the configuration screen so I'm posting it here in case anyone else has this problem.
- Copy Link
- Report Inappropriate Content
My model is C4000
Model: ArcherC4000 v2.0
Firmware: 1.0.3 Build 20180322 rel.2657
I had the same problem until you shared the tips. It's real shame that it has been months and TPLink hasn't fix it :)
But I am still sold by the Quad Core CPU : )
- Copy Link
- Report Inappropriate Content
Hi @ThePol,
Many thanks for the hint but can you clarify what you mean by "hostnames"? Do you mean client names or SSID? I tried to reserve the addresses with this logic and avoided using spaces/special charracters for client names but after saving/restarting my router was completely factory reset.
In other words all the hours I spent setting it up for the first time was wasted. Perhaps I'm not following what exactly it needs to be done to avoid the DHCP crash,
I'm replacing my old ASUS router with C4000 and so far it's been a complete dissapointment.
Thanks in advance.
Cheers
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
Thanks @TCJ,
Does it mean I should avoid even capital letters?!!!
The reason I'm asking is because the names I set had no space or special charracters but still after saving/restarting the router, everything crashed and the router was factory reset!
Cheers
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
emil4902 wrote
Just brought my AC4000 and was having a hard time getting it setup where no IP address were being given out. Sure enough when I turned off address reservations dhcp started working again. So taking your advice I removed all spaces (ie synology NAS to synologyNAS). I took it one step further and limited the name to 8 characters. DHCP works now. Thanks
Forgot to mention i did that too. no space, no special character, just on word.
Apart from this, I think overwall it's fine. Quad core CPU with this pricing. worth it.
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
Information
Helpful: 0
Views: 5065
Replies: 14
Voters 0
No one has voted for it yet.