Validating cluster resource ip address
Issue 1: SQL Server service accounts are unable to contact a domain controller.Resolution 1: Check your event logs for signs of networking issues such as adapter failures or DNS problems. Issue 2: SQL Server service account passwords are not identical on all cluster nodes, or the node does not restart a SQL Server service that has migrated from a failed node.Resolution: To prevent such problems, you must fully enable MS DTC services on the servers where SQL Server is installed and MS DTC is configured.To fully enable MS DTC, use the following steps: When you use extended stored procedures with a failover clustering configuration, all extended stored procedures must be installed on a SQL Server-dependent cluster disk.Doing so ensures that when a node fails over, the extended stored procedures can still be used.If the extended stored procedures use COM components, the administrator must register the COM components on each node of the cluster.
This will enable cluster validation with no downtime.
Resolution 1: Verify that all nodes are using correct firmware versions and same driver versions.
Issue 2: A node cannot recover cluster disks that have migrated from a failed node on a shared cluster disk with a different drive letter.
The first diagnostic step is to run a fresh cluster validation check.
For details on validation, see Failover Cluster Step-by-Step Guide: Validating Hardware for a Failover Cluster.
Resolution 3: To connect using Named Pipes, create an alias using the SQL Server Configuration Manager to connect to the appropriate computer.