I cannot connect a VM server to domain controller host running Server 2012 R2

I setup a domain controller running Server 2012 R2.  I also installed they Hyper-V role and created a new vm running server 2012.  When I go to connect the vm server to the domain controller I get an error that: "the specified domain either does not exist or could not be contacted."  
I have DNS statically assigned of the domain controller on the nic of the VM. I get a popup asking for credentials when I go to add the VM but I get the error stated above.  I can ping both ways from the domain controller to the vm.

Is there something I am missing here?
maximus7569Asked:
Who is Participating?
 
Cliff GaliherCommented:
Don't run Hyper-V and other roles together. The changes Hyoer-V makes to support virtual switches kill other networking pieces. This is particularly disastrous to ADDS. If you want to consolidate, you can run your DCs as guests on Hyper-V. That is a much better alternative than trying to run both on the host. That is likely the source of your issues.
0
 
maximus7569Author Commented:
So make another vm a domain controller and make the physical server just a work group server and carry the hyper v role??
0
 
Cliff GaliherCommented:
Workgroup or a domain member server, depending on availability of other DCs, stability of hardware, and preferences, etc. Yes. It is a common and supported deployment strategy.
0
Creating Active Directory Users from a Text File

If your organization has a need to mass-create AD user accounts, watch this video to see how its done without the need for scripting or other unnecessary complexities.

 
maximus7569Author Commented:
Ok, I will do that now.  I will let you know how it goes. Thanks for the info Cliff.
0
 
maximus7569Author Commented:
Hi Cliff,  That did the trick. I removed that AD roles from hyper-v server and created a VM with AD roles and both vms are now on the domain I created.   So thanks for that.

What is best practice in the event that something happens to the VM with AD role on it?  Like it crashes or gets corrupt?  Is it just making sure I have a current backup of that VM?  I was looking at Veem Backup since it was free.
0
 
Cliff GaliherCommented:
No real change from the rules on a physical DC. Have good backups. Know how to restore a DC (especially in multi-DC eivnronments), etc.   Last I checked, since Veeam has its roots as a virtualization-only backup product and virtualizing DCs wasn't always reliable until 2012 for various reasons, Veeam didn't support AD restores, but that may have changed recently. So normal precautions prevail here.
0
 
maximus7569Author Commented:
Ok great.  Thanks for your help!
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.