Article ID: 923200
Article Last Modified on 4/27/2007
APPLIES TO
- Microsoft Windows Server 2003, Standard Edition (32-bit x86)
- Microsoft Windows Server 2003, Enterprise Edition (32-bit x86)
- Microsoft Windows Server 2003, Datacenter Edition (32-bit x86)
- Microsoft Windows Server 2003, Web Edition
- Microsoft Windows Server 2003, Enterprise x64 Edition
- Microsoft Windows Server 2003, 64-Bit Datacenter Edition
Important This article contains information about how to modify the registry. Make sure that you 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
SYMPTOMS
When you try to receive Transmission Control Protocol (TCP) data in Microsoft Windows Server 2003, the TCP connection may be reset before all the data can be processed.
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
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:
889100 How to obtain the latest service pack for Windows Server 2003
Hotfix information
Prerequisites
To apply this hotfix, you must have Windows Server 2003 installed.
Restart requirement
You must restart the 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, 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 |
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, 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 |
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 the 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 details pane, double-click TCPFinWait2Delay, and then enter a value from 30 through 300.
Note If the TCPFinWait2Delay value does not exist, you must create it as a REG_DWORD registry value. This registry value controls how many seconds that a TCP connection waits before it is forced to close after the shutdown(s, SD_SEND) function is called. The default value is 240 seconds. The range for this value is from 30 through 300. This registry value must be created manually. Otherwise, the default value is used.
STATUS
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 Microsoft Windows Server 2003 Service Pack 2.
MORE INFORMATION
For more information about the terms that are used to describe software updates, click the following article number to view the article in the Microsoft Knowledge Base:
824684 Description of the standard terminology that is used to describe Microsoft software updates
Keywords: kbwinserv2003sp2fix kbregistry kbnetwork kbfix kbhotfixserver kbqfe kbpubtypekc KB923200
