When you try to receive TCP data in Microsoft Windows Server 2003, the TCP connection may be reset before all the data can be processed (923200)

Important This article contains information about how to modify the registry. Make sure to back up the registry before you modify it. Make sure that you know how to restore the registry if a problem occurs. For more information about how to back up, restore, and modify the registry, click the following article number to view the article in the Microsoft Knowledge Base:

256986 Description of the Microsoft Windows registry

CAUSE

This problem occurs when the receiving computer cannot process all the data that is sent within a certain length of time. By default in Windows Server 2003, TCP connections must close after the TCP connection state has been set to FIN_WAIT_2 for two minutes.

Note When the sending computer sends FIN, the state of the TCP connection is set to FIN_WAIT_2. After the TCP connection has been closed, the sending computer sends RST in order to reset the connection if the receiving computer sends any packets to the sending computer.

RESOLUTION

Hotfix information

A supported hotfix is now available from Microsoft, but it is only intended to correct the problem that is described in this article. Only apply it to systems that are experiencing this specific problem. This hotfix may receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next Windows Server 2003 service pack that contains this hotfix.

To resolve this problem immediately, contact Microsoft Product Support Services to obtain the hotfix. For a complete list of Microsoft Product Support Services telephone numbers and information about support costs, visit the following Microsoft Web site:

http://support.microsoft.com/contactus/?ws=support

Note In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The usual support costs will apply to additional support questions and issues that do not qualify for the specific update in question.

Prerequisites

The following list contains prerequisites for the hotfix:

Microsoft Windows Server 2003

Restart requirement

You must 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 item in Control Panel.Windows Server 2003, Itanium-based versions

File name	File version	File size	Date	Time	Platform
Tcpip.sys	5.2.3790.2768	1,283,072	10-Aug-2006	01:40	IA-64

Windows Server 2003, x64-based versions

File name	File version	File size	Date	Time	Platform
Tcpip.sys	5.2.3790.2768	813,056	10-Aug-2006	01:40	x64

Windows Server 2003, x86-based versions

File name	File version	File size	Date	Time	Platform
Tcpip.sys	5.2.3790.2768	386,048	09-Aug-2006	15:21	x86

WORKAROUND

Warning Serious problems might occur if you modify the registry incorrectly by using Registry Editor or by using another method. These problems might require that you reinstall your operating system. Microsoft cannot guarantee that these problems can be solved. Modify the registry at your own risk.

To work around this problem, increase the time that TCP connections may remain in the FIN_WAIT_2 state. To do this, follow these steps:

Click Start, click Run, type regedit, and then click OK.
Locate and then click the following registry subkey:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters
In the right pane, double-click TCPFinWait2Delay, and then enter a value from 1 through 300.

Note If the TCPFinWait2Delay value does not exist, you must create it.

Note The TCPFinWait2Delay value determines the maximum number of seconds that a TCP connection may remain in the FIN_WAIT_2 state. The maximum value for TCPFinWait2Delay is 300 seconds. The TCP/IP stack does not let a connection remain in the FIN_WAIT_2 state for more than five minutes.