A Cluster node may lose an MNS quorum, and the Cluster service may stop on a Windows Server 2003, Enterprise Edition-based computer

Consider the following scenario:

• The Cluster service is installed on Windows Server 2003, Enterprise Edition-based computers.
• A Majority Node Set (MNS) quorum is configured.
• One cluster node is restarted.

In this scenario, another Cluster node may lose an MNS quorum, and the Cluster service may stop. Additionally, information that resembles the following is logged in the Cluster log:

The Cluster service lets the server message block (SMB) connection use only NetBIOS-less transport when the service accesses an MNS quorum as a network share. However, when the SMB connection uses NetBIOS-less transport to access the MNS quorum, the Cluster service returns a "STATUS_CONNECTION_ACTIVE" error. The Cluster service does not try to make SMB connections by using NetBIOS transport. Therefore, the MNS quorum resource is lost, and the Cluster service stops.

After you install this hotfix, the Cluster service tries to make the SMB connection to an MNS quorum by using NetBIOS transport if it cannot make an SMB connection by using NetBIOS-less transport.

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 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: 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

Windows Server 2003 Service Pack 1 (SP1) or Windows Server 2003 Service Pack 2 (SP2) must be installed on the computer.

Restart requirement

You have to restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace any other hotfixes.

File information

The 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 with SP1, x86-based versions

Windows Server 2003 with SP2, x86-based versions

Windows Server 2003, x64-based versions

Windows Server 2003 with SP2, x64-based versions

Windows Server 2003 with SP1, Itanium-based versions

Windows Server 2003 with SP2, Itanium-based versions

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

After you install this hotfix, the following information may be logged in the Cluster log: