Delay If No Response for DHCP Renew/Discover

A DHCP client may experience a delay obtaining an IP address from a DHCP server.

When a client boots, it tries a renew process for the address that it previously owned. If the client does not receive a response to its request for a renewal, the DHCP client waits five minutes before attempting to renew the address. However, the discover process is not affected by the new registry key described later in this article.

Windows NT Server or Workstation 4.0

To resolve this problem, obtain the latest service pack for Windows NT 4.0 or the individual software update. For information on obtaining the latest service pack, please go to:

• http://www.microsoft.com/downloads/details.aspx?familyid=E396D059-E402-46EF-B095-A74399E25737&displaylang=en/ (http://www.microsoft.com/Windows/ServicePacks/) -or-
  
  
• 152734  (http://support.microsoft.com/kb/152734/EN-US/ ) how to obtain the latest windows nt 4.0 service pack

For information on obtaining the individual software update, contact Microsoft Product Support Services. For a complete list of Microsoft Product Support Services phone numbers and information on support costs, please go to the following address on the World Wide Web:
WARNING: If you use Registry Editor incorrectly, you may cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that you can solve problems that result from using Registry Editor incorrectly. Use Registry Editor at your own risk.

A new registry parameter has been added so that the client does not wait for five minutes before attempting to discover a new address. The process for obtaining an address is clearly stated in RFC 1541.

1. Start Registry Editor (Regedt32.exe).
2. Locate the following key in the registry:
   HKEY_LOCAL_Machine\System\CurrentControlSet\Services\Dhcp\Parameters
3. On the Edit menu, click Add Value, and then add the following registry value:
   Value Name: DhcpUseLargeNumberOfRequests
   Data Type: REG_DWORD
   Value: 1 (default is 0)
4. Quit Registry Editor.

Windows NT Server 4.0, Terminal Server Edition

To resolve this problem, obtain the latest service pack for 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:

To work around this issue, run the following commands from the command prompt:

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 Server 4.0 Service Pack 6 and Windows NT Server 4.0, Terminal Server Edition Service Pack 6.