Cluster resources do not automatically fail over to another node when you disconnect the private and public network interfaces in a Windows Server 2008 failover cluster or in a Windows Server 2008 R2 failover cluster

Consider the following scenario:

• You install the Failover Clustering feature on a computer that is running Windows Server 2008 or Windows Server 2008 R2 so that the computer becomes a node in a failover cluster.
• You enable the Do not allow the Cluster to use this network option for network interfaces that are not used for cluster communications.
• You disconnect the private and public network interfaces on the computer.

In this scenario, cluster resources do not automatically fail over to another cluster node.

When the Cluster service searches for available networks, the Cluster service ignores the Do not allow the Cluster to use this network option. This behavior causes the Cluster service to incorrectly detect an available network when the private and public network interfaces are disconnected. Therefore, the affected cluster resources do not automatically fail over to another node.

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, your computer must be running Windows Server 2008, Windows Server 2008 Service Pack 2 (SP2), or Windows Server 2008 R2. Additionally, you must have the Failover Clustering feature installed. 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:

Registry information

To use 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 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.

• 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.

  Version	Product	SR_Level	Service branch
  6.0.600 1 . 22xxx	Windows Server 2008	SP1	LDR
  6.0.600 2 . 22xxx	Windows Server 2008	SP2	LDR

• Service Pack 1 is integrated into the release version of Windows Server 2008. Therefore, RTM milestone files apply only to Windows Vista. RTM milestone files have a 6.0.0000.xxxxxx version number.
• 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 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 Server 2008

For all supported x64-based versions of Windows Server 2008

For all supported IA-64-based versions of Windows Server 2008

For all supported IA-64-based versions of Windows Server 2008 R2

For all supported x64-based versions of Windows Server 2008 R2

Workaround for Windows Server 2008 or for Windows Server 2008 R2

To work around this issue, manually move the cluster resources to another node.

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

Additional file information

Additional file information for Windows Server 2008

Additional files for all supported x86-based versions of Windows Server 2008

Additional files for all supported x64-based versions of Windows Server 2008

Additional files for all supported IA-64-based versions of Windows Server 2008