A client computer that is connected to a Windows Server 2003-based DHCP server loses network connectivity when the client computer tries to renew its IP address

Consider the following scenario:

• You change an exclusion range on a Microsoft Windows Server 2003-based Dynamic Host Configuration Protocol (DHCP) server. Or, you disable a scope in the Microsoft Management Console (MMC) of the DHCP server.
• A client computer that is connected to the DHCP server tries to renew its IP address by sending a DHCP request packet to the DHCP server.

In this scenario, the client computer loses network connectivity.

The DHCP server replies to the DHCP request packet by sending a broadcast DHCP negative acknowledgement (NAK) packet instead of by sending a unicast DHCP NAK packet. If the client computer and the DHCP server are located on different IP subnets, the broadcast DHCP NAK packet does not reach the client computer. Therefore, the client computer loses network connectivity.

Service pack information

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

Hotfix information

A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.

If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix.

Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site: Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.

Prerequisites

To install this hotfix, you must have Windows Server 2003 Service Pack 1 (SP1) installed on your computer.

Restart requirement

You do not have to restart your computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace any other hotfixes.

File information

The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel.

Windows Server 2003, Itanium-based versions

Windows Server 2003, x64-based versions

Windows Server 2003, x86-based versions

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section. This problem was first corrected in Windows Server 2003 Service Pack 2.

For more information, click the following article number to view the article in the Microsoft Knowledge Base: