Event ID: 1209Event ID: 118Event ID: 7031Event ID: 1062Event ID: 7036 Entries that resemble the following are logged in the Cluster.log file:
- The Windows Firewall/Internet Connection Sharing service is enabled, or it is set to start automatically.
- Windows Firewall is configured incorrectly to work with the server cluster. When the Cluster service on a computer starts, the computer tries to find a sponsor node so that it can join an existing cluster. If the computer that is running the Cluster service cannot connect to a sponsor, the computer tries to form a cluster.
When this occurs, the node must take ownership of the quorum device. However, because the quorum device is being used by another node, the cluster node that tries to form a cluster cannot gain access to the quorum. Therefore, the Cluster service exits, and then later it tries to restart. For more information about how the Cluster service reserves a disk, click the following article number to view the article in the Microsoft Knowledge Base:309186 How the Cluster service reserves a disk and brings a disk online
By default, when the Cluster service exits, the service tries to restart about a minute later. To determine whether the computer succeeds in joining the cluster on the second try, look for entries that resemble the following in the System log:
Event ID: 1062Event ID: 7036
Method 1: Disable the Windows Firewall/Internet Connection Sharing serviceIf the Windows Firewall/Internet Connection Sharing service is not required, disable the service. To determine whether the Windows Firewall/Internet Connection Sharing service is running and set to start automatically, follow these steps:
- Click Start, point to Administrative Tools, and then click Services.
- In the Services Microsoft Management Console (MMC) snap-in, right-click Windows Firewall/Internet Connection Sharing (ICS), and then click Properties.
- Make sure that the Startup type is set to disabled and that the Service status is Stopped.
Method 2: Make sure that the Windows Firewall/Internet Connection Sharing service is configured so that the cluster nodes can communicate as requiredInstall the hotfix that is described in the following Microsoft Knowledge Base article:
Note The version of the Ipnat.sys file that is included in Windows Server 2003 Service Pack 2 (SP2) also contains this fix. If Windows Server 2003 SP2 is installed on the computer, see the following Microsoft Knowledge Base article:
Article ID: 938615 - Last Review: Feb 15, 2008 - Revision: 1