@kunal mitra .. Have you looked at this article https://techcommunity.microsoft.com/t5/failover-clustering/workgroup-and-multi-domain-clusters-in-windows-server-2016/ba-p/372059 ?
multi domain failover cluster
I have 2 domains and i created one node each one of them.In both the nodes i have created same local administrator account and signed into both the nodes using the same account.But when i am trying to create a cluster i get this error
server-2 node cant be contacted ensure that it is on and connected to newtork,Please somebody help
Windows for business Windows Server Storage high availability Clustering and high availability
3 answers
Sort by: Most helpful
-
kumar kaushal 176 Reputation points Microsoft Employee
2021-04-18T17:13:52.117+00:00 -
Anonymous
2021-04-19T07:03:24.663+00:00 Hi,
To deploy a multi-domain failover cluster, there’re several requirements that need to be met:- The operation system of all nodes should be after Windows Server 2016;
- All nodes should use certified hardware;
- Failover Cluster feature should be installed on all nodes;
- Each node of the cluster needs to use the same user and password. The user needs to be a member of the local management group. If it is a non-administrator user, additional registry keys need to be modified;
- For a multi-domain mode cluster, each node needs to have the DNS suffix of all domains.
Based on your description, I suggest that you check the operation system and DNS configuration of all the nodes, and see if all the requirements are met.
For your reference:
https://techcommunity.microsoft.com/t5/failover-clustering/workgroup-and-multi-domain-clusters-in-windows-server-2016/ba-p/372059
Thanks for your time.
Best regards,
Danny-----------------------------
If the Answer is helpful, please click "Accept Answer" and upvote it.
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.
-
kunal mitra 1 Reputation point
2021-04-19T07:52:11.847+00:00 I was able to fix the issue by creating a trust between the two domains