Discussion Locked

DHCP issue

0 helpful
6 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
Currently I am running a DHCP server on a subnet with 2 ranges of Class C IP addresses with a subnet of triple 255. I am running NT 4 servers w/mostly NT 4 workstations. The first range of addresses is used exclusively for servers and network equipment(this range is not managed by the DHCP server). The second range is located on the DHCP server, and uses Global scopes for the DNS, WINS, and Router options. This range is for the workstations only. I only have approx. 100 workstations using the DHCP server. The problem I am having is with the workstations losing the lease for the addresses. The lease was originally set for unlimited duration. I changed it to a limited duration of 2 days. The workstations are still losing the addresses. It is a unique problem that I have run into. Even though the workstation lost the address, I can reboot(several times) and receive the same address as before. I can execute ipconfig /renew at the command prompt and receive the error, unable to renew, several times but eventually after about the fifth time it renews. If anyone can shed some light on this subject, it will be greatly appreciated.

6 replies

by tjmitch

Verify your service pack levels as different builds could cause problem with TCP. Move the lease times to 7 days which is a good default. Are you able to do ping/tracert by IP and by name to the dhcp server? the workstations will reuse their old lease address when possible. When your clients are able to get an IP address is everything else working properly? What else is your DHCP server doing? What about bandwidth utilization? Do you have a chatty NIC that is clogging up hub cycles? Is this in a switched environment? What is the protocol binding order? Make sure TCP is first. Sorry to ask so many questions by that's what troubleshooting is isn't it. Good luck

by lemmonr

The DHCP is located in a switched environment. I have checked for a chatty NIC and could not find one. I also checked bandwidth utilization and everything seems OK. When the client finally receives an IP address the workstation runs everything OK. The workstations have a binding order of TCPIP then IPX/SPX. I have changed the lease time to 2weeks (14 days) with the same problems. Thanks for your answer. Maybe with these answers to your questions you might be able to help more.

by estebandelatorre

DHCP scope could be full. Check under dhcp manager in order to release some licenses
It also happens to me when I changed the duration, some machines retains the permanant lease and the 2 day?s lease, two address per pc. I had to delete all the scope, and move dhcp server to other pc (with the new definitions) and after a few days, delete the service and rebuild the scope in the original one.

This discussion is closed to new replies.