- 1 Vapor IO Brings OpenDCRE to General Availability
- 2 VMware Takes the Wraps Off vRealize Automation and vRealize Business
- 3 Microsoft Previews Hyper-V Containers for Windows Server 2016
- 4 Mirantis Led FUEL Project Gets Installed Under OpenStack Big Tent
- 5 Red Hat Enterprise Linux 7.2 Adds Security, DR Features
In The Trenches: DHCP Clients Fail to Renew their IP Addresses
Sometimes DHCP clients just don't get it. You turn them on and they don't renew their IP addressing information the way they should when their lease runs out. Or perhaps you're starting up a RIS client that needs to obtain its IP addressing information from a DHCP Server before starting the OS installation.Sometimes DHCP clients just dont get it. You turn them on and they dont renew their IP addressing information the way they should when their lease runs out. Or perhaps youre starting up a RIS client that needs to obtain its IP addressing information from a DHCP Server before starting the OS installation.
When you run into this problem, you are likely check the usual suspects:
Is there a network connectivity issue preventing the client from communicating with the server?
Is the DHCP Server online?
Does the DHCP Server have a default gateway defined? (an issue with the RIS client).
Are there any IP addresses left in the scope?
But what do you do when the usual suspects fail to cough up the evidence?
The Spanning Tree Connection
The problem might be related to what type of network device the DHCP client is connected to. If the client is connected to a switch that performs a spanning tree calculation during port initialization, then the port the client is connected to may not be available for 10-15 seconds. This is long enough to prevent the DHCP client from renewing or obtaining IP addressing information, and thus preventing the TCP/IP stack from initializing.
This is not a problem on all switches that perform spanning tree calculations. Some devices will perform the calculations in the background, and thus the port becomes available immediately. Also, this type of functionality is only required on ports that are connected to other switching devices. Therefore you don't really need it enabled on ports that have clients directly connected to them.
Microsoft recommends a few fixes for this problem:
Turn off the spanning tree calculations on the ports directly connected to DHCP clients
Assign static IP addresses to clients directly connected to the switch
Place an unintelligent hub between the switch and the DHCP client(s).
Like many problems we encounter, the fixes are easy to implement. It's making the right diagnosis that makes the difference between ulcers and nirvana!
For More Information
For more information on how spanning tree calculations on the switch can affect your DHCP clients, check this article out at TechNet.
For deep details on DHCP in Windows 2000, check out our Managing Windows 2000 Network Services book.