I am experiencing this frustrated issue which I could not figure out.
We recently had a few servers on 192.168.20.0/24 subnet joined the domain on 192.168.250.8/24 subnet.
I did not have problem join them to the domain expect receiving "Changing primary DNS name to .... failed. The name will remain...... The error is the specified domain either does not exist or could not be contacted.
Once these server were on the domain, they were not able to register themselves on the DNS server.
I have tried ipconfig/registerdns with no luck. Wireshark live monitor seems to stuck at dynamic update with domain controller.
Our Dev teams are like yours. They’re continually cranking out code for new features/bugs fixes, testing, deploying, testing some more, responding to production monitoring events and more. It’s complex. So, we thought you’d like to see what’s working for us.
Possible fixes for Windows 7 and Windows Server 2008 updating problem. Solutions mentioned are from Microsoft themselves. I started a case with them from our Microsoft Silver Partner option to open a case and get direct support from Microsoft.
This tutorial will walk an individual through the process of transferring the five major, necessary Active Directory Roles, commonly referred to as the FSMO roles to another domain controller.
Log onto the new domain controller with a user account t…