On a computer that is running Windows Vista or Windows Server 2008, some IPv6 network adapters are unexpectedly reinstalled when any of the following events occurs:

• You restart the computer
• You resume the computer from sleep or hibernation
• You restore network connectivity to the computer

Usually, this behavior does not cause significant issues. However, you may experience the following issues, depending on your specific configuration:

• Performance on the computer may be noticeably reduced for a long time, and unnecessary network traffic may occur. This behavior may occur if your system is configured to install device drivers from a shared folder that hosts many device drivers.
• The computer may stop responding (hangs) during system startup. This behavior occurs because the number of installed IPv6 network adapters grows too large over a long period of time.

You may experience random connectivity issues when you connect a Windows Vista-based mobile PC to certain Wi-Fi hotspots, access points, or routers.

These connectivity issues include the following:

• The wireless network connection is dropped.
• You experience poor performance.

You experience this issue if the Windows Vista-based computer is connecting to a wireless access point or router that is not fully vista compatible.

On a multiprocessor computer that is running Windows Vista or Windows Server 2008, a network connectivity failure occurs randomly when you run certain utilities, such as the Remote Shell (Rsh.exe) utility or the Remote Copy (Rcp.exe) utility. This problem occurs if a network application is using the same four-tuple (server IP address, server port, client IP address, and client port) every time that the utility reconnects a TCP session in a TCP TIME-WAIT delay period.

For example, consider the following scenario:

• On the Windows XP-based computer, the Remote Shell service is installed.
• On the Windows Vista-based computer that has multiple processors, the Remote Shell utility (Rsh.exe) is installed.
• You use the Remote Shell utility on the Windows Vista-based computer to access the Windows XP-based computer.
• The Remote Shell utility commands continue to run one after another for several minutes.

In this scenario, the Remote Shell utility may fail. Additionally, you may receive an error message that resembles the following:

Windows XP computer name: Operation timed out

On a Windows Vista-based client computer, you create many virtual private network (VPN) connections. In this situation, the Connect to a network dialog box takes a long time to appear when you perform one of the following actions:

• Click Start, and then click Connect To
• Right-click the network icon in the taskbar, and then click Connect to a network

On a network, you deploy a Network Access Protection (NAP) architecture. When you connect to this network from a Windows Vista-based client computer, you can access the network resource correctly. However, after you run the gpupdate /force command to reapply the Group Policy settings, the client computer may lose network connectivity.

This issue occurs when the following conditions are true:

• Both IPsec policy and connection security rules are configured for NAP architecture.
• The value of the IKEFlags registry entry is set to 1C in hexadecimal.
  Note: This registry entry is located under the following registry subkey:

  HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\PolicyAgent\Oakley\

You may experience random connectivity issues when you connect a Windows Vista-based mobile PC to certain Wi-Fi “hot spots.” These connectivity issues include the following:

• The wireless network connection is dropped.
• You experience poor performance.

You experience these issues if the Windows Vista-based computer is running on battery power.

Note: You may also experience these issues when you connect a Windows Vista-based mobile PC to a wireless access point (AP) in a small office/home office (SOHO) environment or in an enterprise environment.