Discussion Locked

Unable to obtain DHCP lease renewal

0 helpful
5 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

One of my remote lans issues IP addresses via DHCP. Periodically, one or more of the PCs will lose network connection because their leases have expired. How long after you issue a ipconfig/renew should a new lease be acquired ... better yet, how can I prevent leases from expiring? This does not seem to be a problem on 2 other lans with DHCP servers. If I do nothing for a day or two, the problem resolves itself but in the meanwhile the users do not have access to some of the shared network resources (ie printers).
As a secondary question, how long after you add a new PC to the LAN(consists of about 30-40 PCs) should you typically expect to see it on the network neighborhood?

5 replies

by tehonea

Check the policies on the DHCP server. The DHCP leases should have a duration/expiration set. There is also a default of reserving the expired lease, usually for 24 hours. Depending on the OS version of the DHCP server, you should be able to alter the expiration to suit your needs.

Assuming you are on a Micorsoft network, see the help files in DHCP Manager for more info. Also see Microsoft TechNet.

If you are using LINUX or another OS for your DHCP server, you will need to check the specific settings and help files for that OS.

-Trent

by lmayeda

We are using a Win2K server and had already increased the duration of the leases. The PCs are running WinNT, W2K and XP Pro ... I know i've seen the problem on several WinNT but have not been able to determine if it is limited to the NTs. Most of the NTs are at least SP5. There is a MS article 163383 re: this problem on WinNT Sp2, but I have not attempted to change the registry. Thanks for your response

by yoram

DHCP clients try to renew their lease after 50% of the lease time expired. Failing that they try after 75% again. This is done against the original server, and fails if the server does not respond, which might happen intermittently in a VPN environment. Failing twice, the client will try again using DHCP Discover broadcast, but since you have no server on that segment - will fail. Based on that, try to have your lease renewals away from the heavy traffic time slots.
When you renew manually using an IPConfig your timeout is normally less than a minute before it says server unreachable. Preventing a LEASE from expiring is impossible. To do away with expiration you need to give up DHCP and use static addresses. Not sure this helps at all. I would concentrate on the VPN link to see if you might not have a bottleneck there. Anyway - good luck!

by lmayeda

My apologies ... the problem with this particular PC has been resolved and the issue was not with the DHCP server but rather with the NT which had recently had the hard drive replaced (and subsequently the Operating system). MS KB noted a problem if you install a recent service pack before setting up the network services. The solution was to re-install the service pack and voila all IP issues disappeared. Thanks for your input. I still have an axe to grind with PCs (XP included) who 'zone out' and can't access shared resources without first "finding the computer" ... Hello, Hello are you there? Huh? you want something?

This discussion is closed to new replies.