Hi everyone.
Can I just vent and say NLA is a pain in the ass! Why can't you alter it!!!
Anyway, back to my issue.
I have a Windows 2012r2 HyperV Host with a single DC VM. I have shutdown the VM and exported it, then imported the VM onto a different HyperV Hosts (still 2012r2) in for me to perform some testing.
The export and import went without a hitch, and when I logged into the VM on the new hosts, the network was connected with a domain profile bearing the domain name. everything looked perfect. I tried to open AD and got the error message...
Naming information cannot be location because:
The specified domain either does not exist or could not be contacted.
Contact your system administrator to verify that your domain is properly configured and is currently online.
So I rebooted the server just to ensure everything came up correctly. On reboot, the DC network changed from Domain to Public.
I have checked every single solution I can find. I have ensured DNS is up and running and that the primary DNS on the network is the same as the IP of the server. I have via powershell changed the profile from public to private, I have gone through the registry and followed changes there. stopped and restarted NLA, disabled and enabled the network. All of which end the same bloody problem. Public network no domain. I've even disabled the firewall completely and set the dns prefix to the domain and still nothing.
There are probably other steps I've found via Google that I'm forgetting but this is frustrating.
has anyone had this exact same issue with a DC being moved from one Host to another?
This is driving me nuts, there should be an option to select the network profile.
any help appreciated.
Paul