A Windows Vista-based DHCP client computer may lose its IP address after the computer resumes from sleep or from hibernation

After you resume a Windows Vista-based DHCP client computer from sleep or from hibernation, the computer may lose its IP address. This problem may occur if there is more than one network interface on the computer, such as a real network interface and a virtual private network (VPN) interface.

For example, consider the following scenario:

• On a Windows Vista-based DHCP client computer, you establish a Secure Sockets Layer (SSL) VPN connection to a remote VPN server.
• You disconnect the SSL VPN connection.
• You put the computer to sleep or into hibernation.
• You resume the computer from sleep or from hibernation.

In this scenario, the computer loses the IP address that was assigned to it by the DHCP server. Instead, an Automatic Private IP Addressing (APIPA) address, such as 169.254.0.1, is assigned to the client computer. Therefore, you cannot access some network resources.

Service pack information for Windows Vista

To resolve this problem, obtain the latest service pack for Windows Vista. 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.

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, submit a request to 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 apply this hotfix, you must have Windows Vista installed.

Restart requirement

You must restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace any other previously released hotfixes.

Registry information

To use this hotfix, you do not have to make any changes to the registry.

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 item in Control Panel.

Windows Vista and Windows Server 2008 file information notes

• The files that apply to a specific product, milestone (RTM, SPn), and service branch (LDR, GDR) can be identified by examining the file version numbers as shown in the following table:
  Collapse this tableExpand this table

  Version	Product	Milestone	Service branch
  6.0.600 0 . 20 xxx	Windows	RTM	LDR

• The MANIFEST files (.manifest) and MUM files (.mum) installed for each environment are listed separately . MUM and MANIFEST files, and the associated security catalog (.cat) files, are critical to maintaining the state of the updated component. The security catalog files (attributes not listed) are signed with a Microsoft digital signature.

For all supported x86-based versions of Windows Vista

For all supported x64-based versions of Windows Server 2008 and of Windows Vista

Additional file information for Windows Vista

Additional files for all supported x86-based versions of Windows Vista

Additional files for all supported x64-based versions of Windows Vista

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

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