This article was previously published under Q193436
This article has been archived. It is offered "as is" and will no longer be updated.
Your Windows NT 4.0 client may fail to get an IP address from a DynamicHost Configuration Protocol (DHCP) Server. Sending a Ipconfig.exe /Renewcommand from a command prompt will also be unsuccessful. The client willnot try to lease a new address from the DHCP server until the client hasbeen restarted.
A Windows NT 4.0 Service Pack 3 DHCP client issues a gratuitous ARP afterreceiving a lease from a DHCP server. If another computer responds, that IPaddress is already in use on the network by the other computer. The clientwill not bind the IP address but will instead send a DHCP DECLINE to theDHCP server from which it obtained the lease and the DHCP server will markthe address as bad. The client will then proceed again with the DHCPDISCOVER process.
After a second address conflict, however, the client sends a second DHCPDECLINE, leaves the init state, and no loner attempts to obtain a addressfrom DHCP.
To resolve this problem, obtain the latest service pack for Windows NT 4.0 or Windows NT Server 4.0, Terminal Server Edition. For additional information, click the following article number to view the article in theMicrosoft Knowledge Base:
152734 How to Obtain the Latest Windows NT 4.0 Service Pack
Microsoft has confirmed that this is a problem in Windows NT 4.0 and Windows NT Server 4.0, Terminal Server Edition. This problem was first corrected in Windows NT 4.0 Service Pack 4.0 and Windows NT Server 4.0, Terminal Server Edition Service Pack 4.
Microsoft Windows NT Server 4.0, Terminal Server Edition, Microsoft Windows NT Server 4.0 Standard Edition, Microsoft Windows NT Workstation 4.0 Developer Edition, Microsoft Windows NT Server 4.0 Enterprise Edition