I originally asked this question in the Hyper-V forum because I thought that it is a Hyper-V issue but I'm not sure. So I thought I'd drop it here as well.
What I am trying to do is to set up a second office. To that end, I need a new DC so I set one up on a host in my existing office and tried to move it to a host in the new office 2 ways: 1) copy the VHDX file to the new host and create a new VM using an existing VHD and 2) export the DC VM from the original host and import it one the new host. The result is exactly the same in both cases: the new VM works perfectly as a server but fails as a DC with the error "The domain either does not exist or cannot be contacted" - or whatever the wording is. DNS is set up correctly, the DC is in the new site and has the correct ip address. I can ping the DC from another machine and I can even remote into it. It simply won't work as a DC. Even when I try to run ADU&C, ADS&S or ADSI Edit on the DC, they all fail with the same error. The AD service is running on the DC VM as well. The server does function correctly as a DNS server and an attempt to join a computer to the domain in the new site failed, but it did list all of the DC's. It just complained that it couldn't contact any of them.
I have also ran DCDIAG and had an error of "Fatal Error:DsGetDcName (DC2) call failed, error 1355" and found that the SYSVOL folder was no longer shared for some reason. I recreated the share with the correct permissions but that made no difference. the symptoms remained exactly the same including the DCDIAG error.
Any suggestions?
Thanks
Bert