Hello,

when I try and join to the 2003 domain I get the following error

"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"

Any ideas?

Thanks

Got the same error aswell.
Please do answer if you know anything about this.

open up dos and type in 'ipconfig /renew' to renew your IP. Also, check your TCP/IP network settings and see if there are any DNS's listed, if so just wipe 'em out. Thats the first thing I would do.

I had the IP v4 settings set to auto for IP and DNS. This got the entries from my DHCP, which has the DNS server for my internet provider first and my server second. I changed it from auto to have my server listed as the one and only DNS server. I then repaired the connection and was able to join the domain.

disbale ip ver6
in ipv4 enable the dns , give your domain ip address as dns server.

restart the computer.....
\

thanks

Ad just had the same problem with joining a Vista computer to 2003 server, but it solved the problem when I changed the DNS to my server IP, so now I network i working fine, but I still cannot access the internet from the Vista computer. The server is connected to internet via ADSL, and works fine, any suggestions

Thanks
Martin

point your vista machine to your server for DNS and make sure your server is set up as a DNS server. Alternatively you can put a root server as your secondary DNS so it resolves your server first and then goes out to the net. use (4.2.2.2)

review the following address:
Microsoft Windows Vista Join Domain Troubleshooting firewall error

hope to help

It could be a DNS problem rather than a vista one. If you are running 2003 server R2 (or really any version) and server is configured to be Domain Controller, DNS Server and Active Directory is setup If you delete the forward lookup zone only, reboot re-create forward lookupzone, reboot again then try and join client to the domain. If this does not work I would still consider it to be a DNS problem and keep digging into the event logs to find the problem.

Hope this works for you, it did for me...

I had a similar problem, and resolved it by pointing the DNS, under network properties, to the IP address of the domain controller and also cleared IPv6