Select the product you need help with
- Internet Explorer
- Windows Phone
- More products
DHCP Client May Fail with WinNT 4.0 SP2 Multinetted DHCP Server
Article ID: 163055 - View products that this article applies to.
This article was previously published under Q163055
A DHCP client may fail to obtain a DHCP lease if multiple logical subnets exist and there is a Windows NT 4.0 Service Pack 2 (SP2) DHCP server on the network. Also, you may receive the following error message when you run the IPCONFIG /RENEW command:
Prior to Service Pack 2, when multiple logical subnets existed, the DHCP client was able to receive the DHCPOFFER and send a DHCPREQUEST to the offering DHCP server. After applying Service Pack 2, the DHCP servers on other logical subnets issue a DHCPNACK, which forces the client to release the address and perform a DHCPDISCOVER again.
Access Denied - Renewing Adapter "xxxx"
In addition to the above error message, you may receive the following event log messages:
On the Client
Event ID: 1006 Source: Dhcp Type: Warning Category: None Description: DHCP service is shutting down. The following error occurred: Access is denied.
On the Server
Event ID: 1011 Source: DhcpServer Type: Warning Category: None Description: The DHCP server issued a NACK to the client (MAC Address of the Requesting Client) for the address (Requested IP Address) request.
Windows NT 4.0 SP2 DHCP servers issue a DHCPNACK to any DHCPREQUEST that does not appear to be valid for the subnet. This problem occurs when you are using multiple logical IP subnets (multinetting) and two DHCP servers on the same physical network are serving two different logical subnets.
For example, a client broadcasts DHCPREQUEST and receives ACK from server A and NACK from server B. Because there is no communication between server B and server A, server B is not aware of the existence of server A. If it does not send a NACK, then a client who has just moved to this network will never know that its old address is invalid.
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 the Microsoft Knowledge Base:
(http://support.microsoft.com/kb/152734/EN-US/ )How to Obtain the Latest Windows NT 4.0 Service Pack
To workaround this issue, use one of the following:
TITLE : Using DHCP "Superscopes" to Serve Multiple Logical Subnets
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.