You configure a Windows failover cluster to host some network-related resources.
You start an application or service on a computer that is running Windows Server 2008 R2, Windows 7, Windows Server 2008, or Windows Vista and that you configure as an application server. The application or service connects to the network-related resources.
No router exists between the failover cluster and the application server.
The Cluster service performs a failover operation.
In this scenario, the Cluster service fails over the network-related resources slowly.
Note This issue does not occur if a router exists between the failover cluster and the application server.
For example, consider the following scenario:
You configure a Windows Server 2008 R2 failover cluster to host an instance of Microsoft SQL Server.
You configure an application server and then directly connect the cluster and application server. No router exists between the cluster and the application server.
The Cluster service performs a failover operation.
In this scenario, the Cluster service requires 9 seconds to fail over the SQL Server resources. However, the Cluster service requires only 3 seconds if a router exists between the cluster and the application server.
To resolve this issue, install the following hotfix on the application server that is running Windows Server 2008 R2, Windows 7, Windows Server 2008, or Windows Vista.
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 Vista Service Pack 2 (SP2)
Windows Server 2008 Service Pack 2 (SP2)
Windows 7
Windows 7 Service Pack 1 (SP1)
Windows Server 2008 R2
Windows Server 2008 R2 Service Pack 1 (SP1)
For more information about how to obtain a Windows Vista service pack, click the following article number to view the article in the Microsoft Knowledge Base:
How to obtain the latest Windows Vista service pack
For more information about how to obtain a Windows Server 2008 service pack, click the following article number to view the article in the Microsoft Knowledge Base:
How to obtain the latest service pack for Windows Server 2008
For more information about how to obtain a Windows 7 or Windows Server 2008 R2 service pack, click the following article number to view the article in the Microsoft Knowledge Base:
Information about Service Pack 1 for Windows 7 and for Windows Server 2008 R2
Registry information
To apply this hotfix, 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 English (United States) 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 Vista and Windows Server 2008 file information notes
Important Windows Vista hotfixes and Windows Server 2008 hotfixes are included in the same packages. However, only "Windows Vista" is listed on the Hotfix Request page. To request the hotfix package that applies to one or both operating systems, select the hotfix that is listed under "Windows Vista" 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, SR_Level (RTM, SPn), and service branch (LDR, GDR) can be identified by examining the file version numbers as shown in the following table.
Collapse this tableExpand this table
Version
Product
SR_Level
Service branch
6.0.600
2
.
22xxx
Windows Vista and Windows Server 2008
SP2
LDR
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 and for Windows Vista" section. MUM files and MANIFEST files, and the associated security catalog (.cat) files, are extremely important to maintaining the state of the updated component. 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 Server 2008 and of Windows Vista
Collapse this tableExpand this table
File name
File version
File size
Date
Time
Platform
Tcpipreg.sys
6.0.6002.22722
31,232
30-Sep-2011
14:07
x86
Tcpip.sys
6.0.6002.22722
913,280
30-Sep-2011
19:15
x86
For all supported x64-based versions of Windows Server 2008 and of Windows Vista
Collapse this tableExpand this table
File name
File version
File size
Date
Time
Platform
Tcpipreg.sys
6.0.6002.22722
40,448
30-Sep-2011
13:50
x64
Tcpip.sys
6.0.6002.22722
1,423,232
30-Sep-2011
19:11
x64
For all supported IA-64–based versions of Windows Server 2008
Collapse this tableExpand this table
File name
File version
File size
Date
Time
Platform
Tcpipreg.sys
6.0.6002.22722
80,896
30-Sep-2011
13:55
IA-64
Tcpip.sys
6.0.6002.22722
2,968,960
30-Sep-2011
19:07
IA-64
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:
Collapse this tableExpand this table
Version
Product
Milestone
Service branch
6.1.760
0.17xxx
Windows 7 and Windows Server 2008 R2
RTM
GDR
6.1.760
0.21xxx
Windows 7 and Windows Server 2008 R2
RTM
LDR
6.1.760
1.17xxx
Windows 7 and Windows Server 2008 R2
SP1
GDR
6.1.760
1.22xxx
Windows 7 and Windows Server 2008 R2
SP1
LDR
GDR service branches contain only those fixes that are widely released to address widespread, extremely important issues. LDR service branches contain hotfixes in addition to widely released fixes.
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 7 and for Windows Server 2008 R2" section. MUM and MANIFEST files, and the associated security catalog (.cat) files, are critical to maintaining the state of the updated component. 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
Collapse this tableExpand this table
File name
File version
File size
Date
Time
Platform
Netio.sys
6.1.7601.17939
240,496
22-Aug-2012
17:16
x86
Netio.sys
6.1.7601.22097
240,496
22-Aug-2012
17:05
x86
Tcpip.sys
6.1.7600.17109
1,287,024
21-Aug-2012
01:05
x86
Fwpkclnt.sys
6.1.7600.21312
187,248
22-Aug-2012
17:29
x86
Tcpip.sys
6.1.7600.21312
1,303,920
22-Aug-2012
17:29
x86
Fwpkclnt.sys
6.1.7601.17939
187,760
22-Aug-2012
17:16
x86
Tcpip.sys
6.1.7601.17939
1,292,144
22-Aug-2012
17:16
x86
Fwpkclnt.sys
6.1.7601.22097
187,760
22-Aug-2012
17:05
x86
Tcpip.sys
6.1.7601.22097
1,306,992
22-Aug-2012
17:05
x86
For all supported x64-based versions of Windows 7 and of Windows Server 2008 R2
Collapse this tableExpand this table
File name
File version
File size
Date
Time
Platform
Netio.sys
6.1.7601.17939
376,688
22-Aug-2012
18:12
x64
Netio.sys
6.1.7601.22097
376,688
22-Aug-2012
18:06
x64
Fwpkclnt.sys
6.1.7600.16385
288,336
14-Jul-2009
01:47
x64
Tcpip.sys
6.1.7600.17109
1,895,280
21-Aug-2012
02:09
x64
Fwpkclnt.sys
6.1.7600.21312
288,112
22-Aug-2012
18:30
x64
Tcpip.sys
6.1.7600.21312
1,877,872
22-Aug-2012
18:30
x64
Fwpkclnt.sys
6.1.7601.17939
288,624
22-Aug-2012
18:12
x64
Tcpip.sys
6.1.7601.17939
1,913,200
22-Aug-2012
18:12
x64
Fwpkclnt.sys
6.1.7601.22097
288,624
22-Aug-2012
18:05
x64
Tcpip.sys
6.1.7601.22097
1,901,936
22-Aug-2012
18:06
x64
For all supported IA-64–based versions of Windows Server 2008 R2