Windows 7 / Server 2008 R2 “Changing the Primary Domain DNS name of this computer to “” failed….”

Windows_Server_2008_R2_Logo

Windows Server 2008 R2 VMs started giving me errors while joining the domain recently, here is the exact error message that comes up:

Windows_7_Server_2008_R2_Changing_the_Primary_Domain_DNS_name_of_this_computer_to_failed_1

netsetup.log (%SystemRoot%\debug\netsetup.log) shows no errors and my VMs appears to be joined properly:

Windows_7_Server_2008_R2_Changing_the_Primary_Domain_DNS_name_of_this_computer_to_failed_2

Now to fix this there are two potential solutions/recommendations:

  • UDP port 137 needs to be open between the PC joining the domain and the domain controller,
  • NetBIOS over TCP/IP should be either left at default value or enabled i.e. it cannot be disabled to verify the setting:

    a] Click Start, Run, type ncpa.cpl, hit Enter.
    b] Right-click Local Area Connection, go to Properties, click Internet Protocol Version 4 (TCP/IPv4), and then click Properties.
    c] In the Internet Protocol Version 4 (TCP/IPv4) Properties dialog box, click Advanced and on the WINS tab, verify Enable NetBIOS Over TCP/IP is enabled.

    Windows_7_Server_2008_R2_Changing_the_Primary_Domain_DNS_name_of_this_computer_to_failed_3

    That should sort it.

  • 8 thoughts on “Windows 7 / Server 2008 R2 “Changing the Primary Domain DNS name of this computer to “” failed….”

    1. Jas

      Adrian,
      I have tried your recommended solution but I still get the same error, whats interesting is that my Domain Controller is in the Trust Zone but a firewall separates my network and the DC. Does that mean my firewall will drop any netbios broadcasts and I will continue to get this error because I cannot enable broadcasts to cross my firewall ?
      What are your thoughts ?

    2. Adrian Kielbowicz Post author

      Jas, are your machines actually joining the domain or failing and never create any computer objects in AD? Firewall can be an issue but without knowing more on how strict the configured rules are its hard to say. Can you elaborate and expand on this a bit more?

    3. Jas

      Hey Adrian, the machines join successfully to the domain and I don’t see any issues anywhere but that error is making me uneasy as I hope it doesn’t lead to something bigger…the network team says that there are no restrictions between the 2 buildings. Basically the DC is in another building down the street and we are connected via an MPLS link which is highly reliable. It is a brand new setup and every machine I join to the domain shows the same error. If I go to the other building there are errors but since there are no firewall restrictions as per the network team, is there anything else I need to look at to solve this ?

    4. Adrian Kielbowicz Post author

      Jas,

      Do you guys append DNS suffix using DHCP scope options in both locations? You can check this by running:

      ipconfig /all | find "Suffix"

      There is something different between your two locations since PCs are not showing any errors when on the same network together with the DC. Can you upload netsetup.log somewhere for me to look at?

    5. Pingback: Fix Netsetup.log Errors - Windows XP, Vista, 7 & 8

    6. Pingback: servermanger error 18ea3f92-d6aa-41d9-a205-2023400c8fbb} | Nkhuong90.wordpress.com

    Leave a Reply