Clients Do Not Update DHCP Scope Options on Lease Renewal

ID: Q224175

The information in this article applies to:

SYMPTOMS

When your Windows-based Dynamic Host Configuration Protocol (DHCP) client computer renews the lease on an Internet Protocol (IP) address, your computer may not update changes to DHCP scope options.


RESOLUTION

To work around this problem, release your IP address and start a new lease. Note that you may need to restart your computer after you release your IP address.

Another possible resolution is to configure Windows to release the IP address at each restart. For information about how to do this, please see the following article in the Microsoft Knowledge Base:

Q164228 IP Address Not Released by DHCP at Shutdown
This will make sure that the client releases its IP address and gains a new IP address during a reboot.


STATUS

Microsoft has confirmed this to be a problem in the Microsoft products listed at the beginning of this article.


MORE INFORMATION

The following example demonstrates how the Windows 98 IP stack does not accept DHCP scope option updates through the normal renewal process like Microsoft Windows NT does. Most of the scope options that can be altered or changed are not reflected on a Windows 98 client computer unless the client lease is released and then renewed. It is normally expected that DHCP scope option updates are received and processed during the renewal phase without having to release the client IP address. When clients are shut down, they do not release their IP addresses. This means a Windows 98-based computer could be restarted many times or left on for many days, and as long as it was only renewing the existing lease (not obtaining a new one), the new DHCP options would never be updated without "manually" releasing the IP lease from the client. This can be administratively challenging in many environments.

To set up this example:

Set up a DHCP server with a scope (no options) with a lease time of 10 minutes. Start the Windows-based client computer. This client should obtain an IP address from the DHCP server.

Add the following scope options to the DHCP server: 


router (3)
dns server (6)
domain name (15)
wins server (44)
node type (46)<BR/>
netbios scope id (47)
When the Windows-based client computer renews the lease, it displays the following new options: 

dns server (6)
domain name (15)
No other options will appear or be used by Windows. The next step is to perform a release/renew in an attempt to get additional options. When you do the release/renew, the following options will appear: 

router (3)
dns server (6)
domain name (15)
wins server (44)
node type (46)
The only way to get the NETBIOS scope ID to take effect is to restart your computer. This problem is documented for Windows 95 in the following article in the Microsoft Knowledge Base:
Q145980 Node Type And Scope ID Not Updated Upon Lease Renewal
This article also states that the node type does not change until you restart your computer, but in Windows it appears to only take a release action or renew action to accept the information. To change it after this first initialization however, you must restart your computer.

Once this information has been accepted by the Windows client computer, you can test how well Windows removes options when they have been removed from the DHCP server scope.

Changing the DNS server option takes effect on a renewal, changing domain name, WINS server, or router options require a release or renew action, and changing the node type or scope ID requires you restart your computer.

NOTE: The NetBios Scope Id is a legacy option. The references to the NetBios Scope ID above are mentioned in this article for completeness only. If you are not using Scope IDs you do not need this option.

Additional query words: 


Keywords          : kbnetwork kbui win98 
Version           : WINDOWS:95
Platform          : WINDOWS 
Issue type        : kbprb

Last Reviewed: July 6, 1999