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