Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

The TCP Chimney Offload feature fails on all network adapters in Windows Server 2008 R2 or in Windows 7 if you disable or change the properties of a network adapter


View products that this article applies to.

Symptoms

Consider the following scenario:
  • You install multiple network adapters (NICs) on a computer that is running Windows Server 2008 R2 or Windows 7.
  • You enable the TCP Chimney Offload feature on the computer.
  • You change the properties of a network adapter, or you disable a network adapter.
In this scenario, the TCP Chimney Offload feature fails on all existing network connections, and the computer may stop responding because of a high network load.

Additionally, the existing network connections on the other NICs are in the InHost state instead of the Offload state if you run the netstat -ton command. For example, you receive the following output:
C:\>netstat -ton
Active Connections
  Proto Local Address Foreign Address State PID Offload State
  TCP 192.168.0.39:445 192.168.0.15:61112 ESTABLISHED 4 InHost
Note This issue affects only the existing network connections on other network adapters. This issue does not occur if you create a new network connection.

↑ Back to the top


Cause

This issue occurs because an interface parameter is not received in the reauthorization by Windows Filtering Platform (WFP) Application Layer Enforcement (ALE). Therefore, the TCP Chimney Offload feature stops on the existing network connections. Additionally, the computer stops responding when the network load is high.

↑ Back to the top


Resolution

Hotfix information

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 the problem described in this article. 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.

Prerequisites

To apply this hotfix, you must be running one of the following operating systems:
  • Windows 7
  • Windows 7 Service Pack 1 (SP1)
  • Windows Server 2008 R2
  • Windows Server 2008 R2 Service Pack 1 (SP1)

Registry information

To use the hotfix in this package, you do not have to make any changes to the registry.

Restart requirement

You must restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace a previously released hotfix.

File information

The global version of this hotfix installs files that have the attributes that are listed in the following tables. The dates and the times for these files are listed in Coordinated Universal Time (UTC). The dates and the times for these files on your local computer are displayed in your local time together with your current daylight saving time (DST) bias. Additionally, the dates and the times may change when you perform certain operations on the files.
Windows 7 and Windows Server 2008 R2 file information notes
Important Windows 7 hotfixes and Windows Server 2008 R2 hotfixes are included in the same packages. However, hotfixes on the Hotfix Request page are listed under both operating systems. To request the hotfix package that applies to one or both operating systems, select the hotfix that is listed under "Windows 7/Windows Server 2008 R2" on the page. Always refer to the "Applies To" section in articles to determine the actual operating system that each hotfix applies to.
  • The files that apply to a specific product, milestone (RTM, SPn), and service branch (LDR, GDR) can be identified by examining the file version numbers as shown in the following table:
    VersionProductMilestoneService branch
    6.1.760 0.20xxxWindows 7 and Windows Server 2008 R2RTMLDR
    6.1.760 1.21xxxWindows 7 and Windows Server 2008 R2SP1LDR
  • The MANIFEST files (.manifest) and the MUM files (.mum) that are installed for each environment are listed separately in the "Additional file information for Windows Server 2008 R2 and for Windows 7" section. MUM and MANIFEST files, and the associated security catalog (.cat) files, are extremely important to maintain the state of the updated components. The security catalog files, for which the attributes are not listed, are signed with a Microsoft digital signature.
For all supported x86-based versions of Windows 7
File nameFile versionFile sizeDateTimePlatform
Fwpkclnt.sys6.1.7600.20882187,26417-Jan-201105:42x86
Tcpip.sys6.1.7600.208821,298,30417-Jan-201105:43x86
Fwpkclnt.sys6.1.7601.21643187,77617-Jan-201105:45x86
Tcpip.sys6.1.7601.216431,299,32817-Jan-201105:45x86
For all supported x64-based versions of Windows 7 and of Windows Server 2008 R2
File nameFile versionFile sizeDateTimePlatform
Fwpkclnt.sys6.1.7600.20882288,12817-Jan-201106:23x64
Tcpip.sys6.1.7600.208821,893,24817-Jan-201106:23x64
Fwpkclnt.sys6.1.7601.21643288,64017-Jan-201106:33x64
Tcpip.sys6.1.7601.216431,928,06417-Jan-201106:33x64

↑ Back to the top


Workaround

Workaround for Windows 7 and for Windows Server 2008 R2

To work around this issue, use one of the following methods:
  • Run the netsh int tcp set global chimney=disabled command to disable the TCP Chimney Offload feature.
  • Run the net stop BFE command to disable the Base Filtering Engine (BFE) service.

↑ Back to the top


Status

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

↑ Back to the top


More information

For more information about software update terminology, 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
For more information about WFP, visit the following Microsoft Developer Network (MSDN) website:
For more information about ALE reauthorization, visit the following MSDN website:
For more information about the netstat command, visit the following Microsoft TechNet website:
For more information about how to use the netsh commands to enable or disable the TCP Chimney Offload feature, visit the following Microsoft TechNet website:

Additional file information

Additional file information for Windows 7 and for Windows Server 2008 R2

Additional files for all supported x86-based versions of Windows 7
File nameUpdate.mum
File versionNot applicable
File size2,773
Date (UTC)17-Jan-2011
Time (UTC)23:15
PlatformNot applicable
File nameX86_0fdfdd10780d419a879ef4f39eca5d89_31bf3856ad364e35_6.1.7600.20882_none_6493058edd08a1c2.manifest
File versionNot applicable
File size702
Date (UTC)17-Jan-2011
Time (UTC)23:15
PlatformNot applicable
File nameX86_6940601b9bdb29c72dd47b872760e485_31bf3856ad364e35_6.1.7601.21643_none_7fd2bfb96a91f729.manifest
File versionNot applicable
File size702
Date (UTC)17-Jan-2011
Time (UTC)23:15
PlatformNot applicable
File nameX86_microsoft-windows-tcpip-binaries_31bf3856ad364e35_6.1.7600.20882_none_b37b0bfae0da1ec8.manifest
File versionNot applicable
File size3,834
Date (UTC)17-Jan-2011
Time (UTC)06:13
PlatformNot applicable
File nameX86_microsoft-windows-tcpip-binaries_31bf3856ad364e35_6.1.7601.21643_none_b58da8fadddf3447.manifest
File versionNot applicable
File size3,834
Date (UTC)17-Jan-2011
Time (UTC)06:15
PlatformNot applicable
Additional files for all supported x64-based versions of Windows 7 and of Windows Server 2008 R2
File nameAmd64_7284bed783cc23a7730ae6010ac715e7_31bf3856ad364e35_6.1.7600.20882_none_af6b2b20876e52f4.manifest
File versionNot applicable
File size706
Date (UTC)17-Jan-2011
Time (UTC)23:15
PlatformNot applicable
File nameAmd64_ee23462a76322fc91f7ea53bfd42616b_31bf3856ad364e35_6.1.7601.21643_none_c4281291aea682d9.manifest
File versionNot applicable
File size706
Date (UTC)17-Jan-2011
Time (UTC)23:15
PlatformNot applicable
File nameAmd64_microsoft-windows-tcpip-binaries_31bf3856ad364e35_6.1.7600.20882_none_0f99a77e99378ffe.manifest
File versionNot applicable
File size3,838
Date (UTC)17-Jan-2011
Time (UTC)07:02
PlatformNot applicable
File nameAmd64_microsoft-windows-tcpip-binaries_31bf3856ad364e35_6.1.7601.21643_none_11ac447e963ca57d.manifest
File versionNot applicable
File size3,838
Date (UTC)17-Jan-2011
Time (UTC)07:13
PlatformNot applicable
File nameUpdate.mum
File versionNot applicable
File size3,215
Date (UTC)17-Jan-2011
Time (UTC)23:15
PlatformNot applicable

↑ Back to the top


Keywords: kbautohotfix, kbqfe, kbhotfixserver, kbfix, kbsurveynew, kbexpertiseinter, kbexpertisebeginner, KB2477730

↑ Back to the top

Article Info
Article ID : 2477730
Revision : 1
Created on : 2/10/2011
Published on : 2/10/2011
Exists online : False
Views : 368