Delay If No Response for DHCP Renew/Discover (238917)


The information in this article applies to:

  • Microsoft Windows NT Server 4.0 Terminal Server Edition
  • Microsoft Windows NT Server 4.0
  • Microsoft Windows NT Server, Enterprise Edition 4.0
  • Microsoft Windows NT Workstation 4.0
This article was previously published under Q238917
IMPORTANT: This article contains information about modifying the registry. Before you modify the registry, make sure to back it up and make sure that you understand how to restore the registry if a problem occurs. For information about how to back up, restore, and edit the registry, click the following article number to view the article in the Microsoft Knowledge Base:

256986 Description of the Microsoft Windows Registry

SYMPTOMS

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

CAUSE

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.

RESOLUTION

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:
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:

http://support.microsoft.com/directory/overview.asp


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:

152734 How to Obtain the Latest Windows NT 4.0 Service Pack


WORKAROUND

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

ipconfig /release

ipconfig /renew

STATUS

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.
Modification Type:MinorLast Reviewed:9/23/2005
Keywords:kbHotfixServer kbQFE kbbug kbfix kbQFE KB238917
©2004 Microsoft Corporation. All rights reserved.