troubleshooting Question

Cannot reach writable domain controller error when creating Server 12 failover cluster

Avatar of SINC_dmack
SINC_dmack asked on
Microsoft Virtual ServerWindows Server 2012
7 Comments1 Solution8034 ViewsLast Modified:
We have two Server 12 boxes which are running HyperV.  virtserver1 is a primary domain controller.  virtserver2 is a member server.  virtserver1 hosts a handful of virtual machines, which I would like to make redundant through a failover cluster.

I installed the failover cluster feature on both servers.  I created a cluster using just virtserver2. I forgot to add virtserver1 when I was creating the cluster, so I attempted to add virtserver1 as a node.  The Validate a Configuration Wizard reports the following:

The servers do not all have the same domain role.
The servers are not all in the same organizational unit.
Node(s) virtserver2.virtdomain.local can reach a writable domain controller.
Node(s) virtserver1.virtdomain.local cannot reach a writable domain controller. Please check connectivity of these nodes to the domain controllers.

The strange thing is that virtserver1 IS the primary domain controller, so how can it not be able to reach a writable domain controller?  This is the only failure in the wizard, so presumably if I get it resolved, I'll be able to successfully add virtserver1 as a node.

I've been reading this article, , but am not easily coming to any conclusions.

What's the best way to proceed, to get virtserver1 added as a node?  Should I:
a) Delete the cluster, remove virtserver2 from virtdomain.local, demote virtserver1 to no longer be a domain controller, and attempt to recreate the cluster with both servers simply being workgroup members? (I'm guessing no, as the article says "There are instances when you can deploy cluster nodes in an environment where there are no pre-existing Active Directory. This scenario requires that you configure at least one of the cluster nodes as a domain controller."
b) Delete the cluster, promote virtserver2 to be a domain controller, and then attempt to recreate the cluster with both servers as domain controllers?  (I'm not sure about this as the article also says "It is not supported to combine the Active Directory Domain Services role and the Failover Cluster feature on Windows Server 2012.
It is recommended that at least two nodes be configured as domain controllers and potentially all nodes for consistency if cluster nodes are configured as domain controllers. "  Those statements sound conflicting.)
c) Something else?

(I don't NEED either server to be a domain controller--they are not hosting any services other than HyperV and clustering, and the only account logging into them will be the administrator account for administration purposes.)

Join the community to see this answer!
Join our exclusive community to see this answer & millions of others.
Unlock 1 Answer and 7 Comments.
Join the Community
Learn from the best

Network and collaborate with thousands of CTOs, CISOs, and IT Pros rooting for you and your success.

Andrew Hancock - VMware vExpert
See if this solution works for you by signing up for a 7 day free trial.
Unlock 1 Answer and 7 Comments.
Try for 7 days

”The time we save is the biggest benefit of E-E to our team. What could take multiple guys 2 hours or more each to find is accessed in around 15 minutes on Experts Exchange.

-Mike Kapnisakis, Warner Bros