Client to Cluster Connectivity Problems

Client-to-clust er connectivit y problems What problem are you having? • Clients cannot connect to virtual servers. • Clients cannot access resources. • A node cannot communicate on a network. • Clients cannot access a group that has failed over. • Clients cannot attach to a cluster file share resource. • Clients cannot access a cluster resource. • Client can detect all nodes but cannot detect a virtual server. • Clients cannot connect to a virtual server and the system event logs on the client computers contain Kerberos authentication errors. Clients cannot connect to virtual servers. Cause: The client might not be using the correct network name or IP address to access the cluster. Solution: Make sure that the client is accessing the cluster using the correct network name or IP address. Cause: The client might not have the TCP/IP protocol correctly installed and configured. Solution: Make sure that the client has the TCP/IP protocol correctly installed and configured. Depending on the application being accessed, the client can address the cluster by specifying either the resource network name or the IP address. In the case of the network name, you can verify proper name resolution by checking the NetBT cache (using the Nbtstat.e xe utility) to determine wheth er the name had been previously resolved. Also, confirm proper WINS configuration, both at the client and through the WINS Administrator. If the client is accessing the resource through a specific IP address, ping the IP address of the cluster resource and cluster nodes from a command prompt. For more information on Nbtstat.exe, see Nbtstat . For instructions on how to troubleshoot connec tivity problems, see Troubleshoot client-to-virtual server connectivity. Cause: The client may be attempting to connect to an incorrect node after a failover. Solution: Make sure that the routers are configured correctly. For more information, see article Q244331, "MAC Address Changes for Virtual Server During a Failover with Clustering" in the Microsoft Knowledge Base. Clients cannot access resources. Cause: Both your private network and the primary network are down. Solution: If your server cluster nodes are multihomed and use a private network to communicate, the primary network can be down and the Cluster service can still function normally. If the private network is l ost between nodes, resources that are configured to do so will fail o ver to the node that has ownership of the quorum resource. Each of the other nodes will stop its Cluster service. Cause: A node might have lost connectivity with the network. Solution: If you suspect a node has lost connectivity with the network:

Client to Cluster Connectivity Problems

Documents

Transcript of Client to Cluster Connectivity Problems