Select the product you need help with
- Internet Explorer
- Windows Phone
- More products
Default TCP Window Size Is Still Used After You Specify a Different TCPWindowSize Value
Article ID: 810382 - View products that this article applies to.
IMPORTANT: This article contains information about modifying the registry. Before you modify the registry, make sure to back it up and make sure that you understand how to restore the registry if a problem occurs. For information about how to back up, restore, and edit the registry, click the following article number to view the article in the Microsoft Knowledge Base:
(http://support.microsoft.com/kb/256986/EN-US/ )Description of the Microsoft Windows Registry
In Windows 2000, when you set the
SynAttackProtectregistry value to 2, you may not be able to configure the TCP receive window size globally for all interfaces. For example, if you set the
SynAttackProtectvalue in the
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameterskey to 2, and then set the
TCPWindowSizevalue in the
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameterskey to a value other than the default value, the new window size setting may not apply. The default TCP receive window size is still used.
This problem occurs because the
TCPWindowSizevalue is not processed correctly at the parameters (global) level when the
SynAttackProtectvalue is set to 2.
Service Pack InformationTo resolve this problem, obtain the latest service pack for Microsoft Windows 2000. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:
(http://support.microsoft.com/kb/260910/EN-US/ )How to Obtain the Latest Windows 2000 Service Pack
Hotfix InformationA 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:
http://support.microsoft.com/contactus/?ws=supportNote 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. The Global version of this fix has the file attributes (or later) 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 tool in Control Panel.
Date Time Version Size File name ----------------------------------------------------------- 13-Nov-2002 16:36 5.0.2195.6127 118,896 Afd.sys 02-Dec-2002 17:57 5.0.2195.6020 105,232 Msafd.dll 02-Dec-2002 17:56 5.0.2195.6145 313,648 Tcpip.sys 31-Jul-2001 00:15 5.0.2195.3988 16,240 Tdi.sys 02-Dec-2002 17:57 5.0.2195.4874 17,680 Wshtcpip.dll
Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article. This problem was first corrected in Microsoft Windows 2000 Service Pack 4.
WARNING: If you use Registry Editor incorrectly, you may cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that you can solve problems that result from using Registry Editor incorrectly. Use Registry Editor at your own risk. To work around this problem, use one of the following methods.
Method 1: Set the SynAttackProtect Registry Value to Either 0 (Zero) or 1To set the
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcip\Parameters\SynAttackProtectvalue to either 0 (zero) or 1:
Method 2: Configure the TCPWindowSize Registry Value at the Interfaces LevelTo configure the
TCPWindowSizeregistry value at the interfaces level:
SynAttackProtectregistry value is used to harden the TCP/IP stack against denial of service attacks. You configure this value according to the level of protection that you want to set. For additional information about TCP/IP-related registry values that you can configure to harden the TCP/IP stack on computers that are directly connected to the Internet, click the following article number to view the article in the Microsoft Knowledge Base:
(http://support.microsoft.com/kb/315669/EN-US/ )HOW TO: Harden the TCP/IP Stack Against Denial of Service Attacks in Windows 2000
TCPWindowSizeregistry value is used to determine the maximum TCP receive window size that is offered by a computer when it establishes a TCP connection. The receive window specifies the number of bytes that a sender can transmit without receiving an acknowledgment. For additional information about TCP features in Windows 2000, click the following article number to view the article in the Microsoft Knowledge Base:
(http://support.microsoft.com/kb/224829/EN-US/ )Description of Windows 2000 TCP Features
Article ID: 810382 - Last Review: February 21, 2007 - Revision: 2.7