This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
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.
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.
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.
We finally solved the problem by "punting." We had tried so many suggestions that we had reached a point where we were unable to change certain settings displayed by ipconfig/all. So, we did a textbook fresh install on the system/boot partition. We assigned a fixed IP address for the server and reserved that address in our router; then we added the roles: [1] file server, [2] print server, [3] domain controller - using the Server Manager GUI interface. We did not add the role DHCP Server because we already had a DHCP server via our router. After adding the role DC, you are advised to run "dcpromo." Before we did that, we unchecked the IPv6 checkbox in the properties for the LAN connection because we really have no idea how to translate IPv4 numerics to IPv6 and we do not need IPv6 in our LAN. Making a server a domain controller automatically adds the DNS server role. After running dcpromo and re-booting the server, we set the preferred DNS server IP on the Win7Pro/WS to that of the DC/Server and added the Win7Pro workstation with no problem. The re-install of Windows Server 2008 was made easy due to the fact that our o/s lives on a separate spindle. We have a pair of Sata drives with a simple mirror where all our data and work-in-progress lives. Happy New Year! ----DCS 1/2/2012 13:03.
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.
I ran into the same issues which stemmed from the router having a static ip.
I stumbled across this on my test server (which doesn't)
I unplugged the disconected the router and having set the workstation to look for the server for DNS IP, it joined right away when I brought back up. (this was after much hair loss mind you =)
The next PC I brought into the network, I left the eternet disconnected until it was up and set the DNS IP to the Server's.
Re-booted it (still disconnected) and after loading, connected the cable and bang! It found the domain controller and I was able to join it to the domain without a hitch, almost as easy as *cough* XP. .
We have tried all posted suggestions with the exception of editing the registry. One should not have to edit the registry in order to join a domain.
Below is a re-post of our problem situation:
_______________________
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:
Any other ideas out there. I am very ready to go back to Server 2003.
Thanks, DCS
________________________
With the number of people having this problem, there must be an issue regarding joining a Win7Pro workstation to a Win2008R2 domain controller. Maybe it's a bug in Win7, maybe in Win2008R2 server - or both. The fact that it is so easy to add an Xp/Pro workstation and it is not possible to add a Win7Pro workstation suggests this. Yes, I have tried Win7 UAC as well. Anyone out there have the answer?? I will not sell Server 2008 until I can believe in it.
regards/DCS
This worked great for me!! Thanks so much for your help!
