Article ID: 177357 - Last Review: November 1, 2006 - Revision: 2.2

DHCP Client Does Not Immediately Renew Address

View products that this article applies to.

This article was previously published under Q177357

SYMPTOMS

Dynamic host configuration protocol (DHCP) clients may lose their IP address information for up to five minutes after their DHCP lease has expired.

Back to the top

RESOLUTION

To resolve this problem, obtain the latest service pack for Windows NT 4.0. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:

152734 (http://support.microsoft.com/kb/152734/EN-US/ ) How to Obtain the Latest Windows NT 4.0 Service Pack

Back to the top

STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article.

Back to the top

MORE INFORMATION

The following is a small section of RFC 1541 that governs lease expiration behavior:

4.4.4 Reacquisition and expiration ...

   In both RENEWING and REBINDING state, if the client receives no
   response to its DHCPREQUEST message, the client should wait one-half
   the remaining time until the expiration of T1 (in RENEWING state) and
   T2 (in REBINDING state) down to a minimum of 60 seconds, before
   retransmitting the DHCPREQUEST message.

   If the lease expires before the client receives a DHCPACK, the client
   moves to INIT state, MUST immediately stop any other network
   processing and requests network initialization parameters as if the
   client were uninitialized. If the client then receives a DHCPACK
   allocating that client its previous network address, the client SHOULD
   continue network processing. If the client is given a new network
   address, it MUST NOT continue using the previous network address and
   SHOULD notify the local users of the problem.

Back to the top