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 or Windows Server 2008-based computer that has multiple processors, the TCP initial sequence number (ISN) generation method has changed. Therefore, if a TCP connection that uses the same four-tuple (server IP address, server port, client IP address, and client port) is reestablished in a TCP TIME-WAIT delay period to a remote host, the ISN that is generated for that connection does not let the TCP session continue. However, you expect the session to continue. For more information, see Request for Comments (RFC) 1337, "TIME-WAIT Assassination Hazards in TCP. To see RFC 1337, visit the following Internet Society Web site:
Microsoft provides third-party contact information to help you find technical support. This contact information may change without notice. Microsoft does not guarantee the accuracy of this third-party contact information.
A hotfix is available to resolve this problem. However, not all the Windows Vista-based or Windows Server 2008-based multiprocessor computers need this hotfix. Only the computers that run the specific commands need the hotfix.
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.
Important Windows Vista and Windows Server 2008 hotfixes are included in the same packages. However, only one of these products may be listed on the “Hotfix Request” page. To request the hotfix package that applies to both Windows Vista and Windows Server 2008, just select the product that is listed on the page.
There are no prerequisites.
You have to restart the computer after you apply this hotfix.
Hotfix replacement information
This hotfix does not replace any other previously released hotfixes.
To use this hotfix, you do not have to make any changes to the registry.
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, x86-based versions
Windows Vista Enterprise 64-bit Edition, Windows Vista Home Basic 64-bit Edition, Windows Vista Home Premium 64-bit Edition, Windows Vista Ultimate 64-bit Edition, Windows Vista Business, Windows Vista Business 64-bit Edition, Windows Vista Enterprise, Windows Vista Home Basic, Windows Vista Home Premium, Windows Vista Ultimate, Windows Server 2008 Datacenter without Hyper-V, Windows Server 2008 Enterprise without Hyper-V, Windows Server 2008 for Itanium-Based Systems, Windows Server 2008 Standard without Hyper-V, Windows Server 2008 Datacenter, Windows Server 2008 Enterprise, Windows Server 2008 Standard