Table
Problem | Probable Cause | Corrective Action |
|
|
|
One of the nodes takes a | The | Check the network cabling. |
long time to join the | network has failed due | Ensure that the |
cluster. | to a cabling or | interconnection and the public |
or | hardware failure. | network are connected to the |
| correct NICs. | |
One of the nodes fail to |
| |
|
| |
join the cluster. | Long delays in node- | Verify that the nodes can |
| ||
| communicate with each other | |
| communications may | by running the ping command |
| be normal. | from each node to the other |
|
| node. Try both the host name |
|
| and IP address when using the |
|
| ping command. |
|
|
|
| One or more nodes | Configure the Internet |
| may have the Internet | Connection Firewall to allow |
| Connection Firewall | communications that are |
| enabled, blocking | required by the Microsoft® |
| Remote Procedure | Cluster Service (MSCS) and the |
| Call (RPC) | clustered applications |
| communications | or services. |
| between the nodes. | See Microsoft Knowledge Base |
|
| |
|
| article KB883398 at the |
|
| Microsoft Support website at |
|
| support.microsoft.com for more |
|
| information. |
48