4 replies
by bfilmfan
After a Dynamic Host Configuration Protocol (DHCP) client lease expires, it is not immediately scavenged from the database. A grace period of four hours is added to the end of the lease to prevent against clock drift between the DHCP client and server. On a Windows 2000-based DHCP server, leases are scavenged from the database if they meet the criteria of (ExpirationTime + 4 hours, but this generally is about a day).
It appears that your server is handing out addresses that have already been assigned to clients.
Have you only the one DHCP server?
Did you check the integrity of the DHCP database after the crash?
by sgt_shultz
by aquias20009
I think BFilm has the right idea, look at the DHCP for corruption. If push came to shove, I'd say rebuild the server, reapply the service packs and then re-enable it on your network (What, you think weekends are for IT people to do anything personal????)
I'd give a warning about going to static (especially in large scale networks), it is more of a headache than a blessing in many ways. It adds a great deal of administrative overhead for you and the network staff to deal with.
by astewart
Try deleting/moving the DHCP database and getting DHCP to create a new one. This is covered in the details of KB article 173396. Don't forget to stop the DHCP service 1st.
Alan
This discussion is closed to new replies.
Trending Windows Forum posts
Sort by Trending