Select the product you need help with
After you enable the dynamic backlog settings on a Windows Server 2003-based computer, the System Handle count and the nonpaged pool usage may increase significantlyArticle ID: 951162 - View products that this article applies to. On This PageSYMPTOMSOn a Windows Server 2003-based computer, you may decide to use the Afd.sys driver to enable the
dynamic backlog settings.
You do this
to harden the
TCP/IP stack against SYN attacks. Note You configure the dynamic backlog settings according to the instructions in the following Microsoft Knowledge Base article: 142641 In
this scenario, the System Handle count and the nonpaged
pool memory
usage may increase significantly.
Eventually, the nonpaged
pool memory
may be exhausted, and then the system stops
responding (hangs).
(http://support.microsoft.com/kb/142641/
)
Internet server unavailable because of malicious SYN attacks
CAUSEWhen the dynamic backlog is triggered to create new
connections, the Afd.sys driver creates
connections according to the value of the
DynamicBacklogGrowthDelta registry
entry. However, under
certain circumstances, the driver may incorrectly
create connections according to the value of the
MaximumDynamicBacklog
registry entry. Because of this incorrect behavior, the Afd.sys driver creates many unnecessary connections. Therefore, the System Handle count and the nonpaged pool memory usage increase significantly. RESOLUTIONHotfix 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. 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: http://support.microsoft.com/contactus/?ws=support 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.
(http://support.microsoft.com/contactus/?ws=support)
PrerequisitesTo apply this hotfix, you must have Windows Server 2003 Service Pack 1 (SP1) or Windows Server 2003 Service Pack 2 (SP2) installed.Restart requirementYou must restart the computer after you apply this hotfix.Hotfix replacement informationThis hotfix does not replace any other previously released hotfixes.Registry informationTo use this hotfix, you do not have to make any changes to the registry.File informationThe 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 SP1, x86-based versionsCollapse this table
Windows Server 2003 SP2, x86-based versionsCollapse this table
Windows Server 2003 SP1, Itanium-based versionsCollapse this table
Windows Server 2003 SP2, Itanium-based versionsCollapse this table
Windows Server 2003 and Windows XP, x64-based versionsCollapse this table
Windows Server 2003 SP2 and Windows XP SP2, x64-based versionsCollapse this table
WORKAROUNDImportant This section, method, or task contains steps that tell you how to
modify the registry. However, serious problems might occur if you modify the
registry incorrectly. Therefore, make sure that you follow these steps
carefully. For added protection, back up the registry before you modify it.
Then, you can restore the registry if a problem occurs. For more information
about how to back up and restore the registry, click the following article
number to view the article in the Microsoft Knowledge Base: 322756 To work around this issue, disable the backlog settings. To
do this,
follow these steps:
(http://support.microsoft.com/kb/322756/
)
How to back up and restore the registry in Windows
STATUSMicrosoft
has confirmed that this is a problem in the Microsoft products that are listed
in the "Applies to" section. MORE INFORMATIONThe Afd.sys driver is expected to create free connections
according to the value of the DynamicBacklogGrowthDelta registry
entry when the following conditions are true.
824684
(http://support.microsoft.com/kb/824684/
)
Description of the standard terminology that is used to describe
Microsoft software updates
Technical support for x64-based versions of Microsoft WindowsIf your hardware came with a Microsoft Windows x64 edition already installed, your hardware manufacturer provides technical support and assistance for the Windows x64 edition. In this case, your hardware manufacturer provides support because a Windows x64 edition was included with your hardware. Your hardware manufacturer might have customized the Windows x64 edition installation by using unique components. Unique components might include specific device drivers or might include optional settings to maximize the performance of the hardware. Microsoft will provide reasonable-effort assistance if you must have technical help with a Windows x64 edition. However, you might have to contact your manufacturer directly. Your manufacturer is best qualified to support the software that your manufacturer installed on the hardware. If you purchased a Windows x64 edition such as a Windows Server 2003 x64 edition separately, contact Microsoft for technical support.For product information about Windows XP Professional x64 Edition, visit the following Microsoft Web site: http://www.microsoft.com/windowsxp/64bit/default.mspx For product information about x64-based versions of Windows
Server 2003, visit the following Microsoft Web site:
(http://www.microsoft.com/windowsxp/64bit/default.mspx)
http://www.microsoft.com/windowsserver2003/64bit/x64/default.mspx
(http://www.microsoft.com/windowsserver2003/64bit/x64/default.mspx)
PropertiesArticle ID: 951162 - Last Review: October 8, 2011 - Revision: 2.0 APPLIES TO
|



Back to the top








