When the server with the active scope is unavailable, the DHCP server with the deactivated scope will assume the responsibilities for the DHCP clients of that scope. More informationĪdministrators find that configuring two DHCP servers for the same scope then disabling one is an easy way to provide limited fault tolerance. This problem was first corrected in Windows NT Server version 4.0, Terminal Server Edition Service Pack 6. Microsoft has confirmed that it's a problem in the Microsoft products that are listed at the beginning of this article. To resolve this problem, obtain the latest service pack for Windows NT Server 4.0, Terminal Server Edition. Windows NT Server 4.0, Terminal Server Edition To resolve this problem, obtain the latest service pack for Windows NT 4.0 or the individual software update.įor information on obtaining the individual software update, contact Microsoft Product Support Services. It applies to Windows NT 4.0 Service Pack 5 as well. After releasing all the addresses, the DHCPLeases.txt file is also cleared. The user can also release the leases received from the server, either one by one (by IP address) or all of them at once. All DHCP leases obtained from the server are saved in the DHCPLeases.txt file, which is automatically generated by the program. Previous to Windows NT 4.0 Service Pack 4, this behavior wasn't present. For the DHCP client simulator mode, assuming there is an active DHCP server on the network, the user can choose to simulate any number of DHCP clients.

It will also increase network traffic and cause the client to needlessly fall back to an Initializing state. If the client is running Windows NT Server or Workstation, the DHCPNAK would cause an event to be logged to the Windows NT System Event log. In the case where there are two or more DHCP servers on the network configured to service this segment, and a DHCP server has the scope for this segment disabled, the client may receive a negative acknowledgment (DHCPNAK) from the DHCP server with the disabled scope. Or in the case of the client never having an address, it will try to obtain a lease for an IP address for its scope (Initializing state). When you start a Dynamic Host Configuration Protocol (DHCP) client, it tries to renew its lease on an existing IP address for its scope (Requesting state).

This article provides a solution to an issue when you start a Dynamic Host Configuration Protocol (DHCP) client.Īpplies to: Windows Server 2012 R2 Original KB number: 228597 Symptoms DHCP Server with Deactivated Scope sends a DHCPNAK to clients

Dhcp client simulator software