Cannot add Windows 7 PC to domain. Get the following message. An attempt to resolve the DNS name of a DC in the domain being joined has failed.

Anonymous
2009-11-10T19:41:01+00:00

When trying to add a new Windows 7 machine to a network I get the following error message..."An attempt to resolve the DNS name of a DC in the domain being joined has failed. Please verify this client is configured to reach a DNS server that can resolve DNS names in the target domain."  I don't have any problems adding XP machines to the domain and not sure why I can't add a Windows 7 machine.  I am able to get on the internet on the Windows 7 PC but can't add it to the domain.  Any suggestions would be greatly appreciated.

Windows for home | Previous Windows versions | Internet and connectivity

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments
Answer accepted by question author
Anonymous
2009-11-16T17:42:34+00:00

We finally got the computer to join the domain by doing the following:  in the network adapter IP 4 properties, set the DNS ip address to that of the domain controller, NOT the DNS.  Then went back to the computer properties to add the computer to the domain, it was added succesfully.  After rebooting the machine and logging into the domain account, go back to the IP 4 properties and reset the DNS to automatically get the ip address.

Was this answer helpful?

200+ people found this answer helpful.
0 comments

54 additional answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Anonymous
    2011-09-29T21:52:00+00:00

    On my Windows 7/Pro 32bit workstation, I tried open UPD port #389 for both inbound and outbound by defining new rules. It did not work. I still get the same message:

    "The following error occurred attempting to join the domain "dcs":

    An attempt to resolve the DNS name of a domain controller in the domain being joined has failed. Please verify this client is configured to reach a DNS server that can resolve the DNS names in the target domain. For information about network troubleshooting, see Windows Help."

    any other suggestions/ideas would be helpful.

    thanks/DCS

    Was this answer helpful?

    0 comments
  2. Anonymous
    2011-09-29T02:19:08+00:00

    My problem maybe the same as yours.  I have a Firewall that all my traffic goes through.

    Check that you have port UDP 389, that contacts your AD server is open.

    **GOOD LUCK!**

    Was this answer helpful?

    0 comments
  3. Anonymous
    2011-08-23T21:16:13+00:00

    First of all, this is a problem joining a Win7/Pro workstation to a Server 2008 R2 Domain Controller. The Win7 workstation can use shared resources on the server and can ping it; it cannot join the domain. The problem does not exist with Server 2003. The problem does not exist when we connect XP/Pro workstations to Server 2008 R2.

    These are most of the suggestions we have tried without success:

    1. Preferred DNS on WS set to server IP - No go
    2. Turned off IPv6 – No go
    3. Removed DNS role on server; then re-added DNS role – No go
    4. Turned off user account settings on WS – No go
    5. Nslookup cannot see the domain controller
    6. Tried fixed IP address – No go
    7. Tried unchecking IP v6 in LAN connection properties – No go

    Any other ideas out there. I am very ready to go back to Server 2003.

    Thanks, DCS

    Was this answer helpful?

    0 comments
  4. Anonymous
    2011-08-23T14:03:38+00:00

    what is your function level set to?

    You might have to do a registry edit in order to get a windows7 machine to connect to a 2003 machine. The following is a part of the link from below:

    http://support.microsoft.com/kb/2008652

    To resolve this issue either delete the NT4Emulatorregistry value on the Active Directory domain controllers in the destination domain if Windows NT 4.0 domain controllers are no longer present or can be retired. Otherwise, set the following registry value on the Windows 7 or Windows Server 2008 R2 client before attempting to join the domain:

    1. Start Registry Editor (Regedit.exe).
    2. Locate the following key in the registry:

    HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Netlogon\Parameters 3. If it does not exist, create a new REG_DWORD value named NeutralizeNT4Emulator, and set the value to 0x1. 4. Quit Registry Editor.

    This registry setting allows the Active Directory domain controllers with the NT4Emulator setting to respond normally to the requesting client (avoiding Windows NT 4.0 emulation mode).

    Was this answer helpful?

    0 comments