[Webinar] Streamline your web hosting managementRegister Today

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 393
  • Last Modified:

Windows 7 doesn't want to join Windows Server 2003

"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 the can resolve DNS names in the target domain."

5 Windows XP Pro PCs are set up to connect to the Domain. These 5 client PCs have no trouble accessing the Domain Controller of the Windows Server 2003. However, this new Windows 7 Pro client keeps giving the above error message when I try to join the Domain.
0
expertclyde
Asked:
expertclyde
3 Solutions
 
ReubenwelshCommented:
Can you ping the DCs from the windows 7 computer? Im thinking if the firewall might be causing problems.
0
 
Sushant GulatiConsultantCommented:
Disable the firewall on Win 7 and make sure that under Advanced Sharing Settings the Network Discovery is enabled.

Good Luck..!!
~SG~
0
 
subhashmCommented:
Make sure the DNS settings are correct.
Check if computer is able to resolve FQDN of Domain as well as DC
Disable firewall, if any
0
Free Tool: SSL Checker

Scans your site and returns information about your SSL implementation and certificate. Helpful for debugging and validating your SSL configuration.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

 
expertclydeAuthor Commented:
Reubenwelsh/susguperf/subhashm:

I'll try the above suggestions. I'll keep you posted.

later
cg
0
 
Sushant GulatiConsultantCommented:
Also check on the active network card the NETBIOS over TCP/IP is enabled on the Windows 7 Pro machine.

Good Luck..!!
~SG~
0
 
expertclydeAuthor Commented:
Sorry for the delay.
Good news and bad news.
Turning off the firewall did not help.
FQDN didn't have the IP address associated with it. Nevertheless, it didn't help either.
Discovery was enabled.

However, I was able to map the server drives I wanted by leaving the PC as a workgroup member, as opposed to trying to add the PC into the domain.
0
 
Sushant GulatiConsultantCommented:
This is not recommended and there are many resources you won't be able to use and it will keep on prompting for the domain credentials..

ipconfig /all --- can you send me the results please?

Also checking it from the Network Adapters properties what do you the status for the NetBios Over TCP/IP? Is it enabled?

Kindly check this.. Because there are some known issues with this... Also disable the firewall using elevated command prompt..

netsh firewall set opmode mode=disable

Let us know your result..

Good Luck..!!
~SG~
0
 
expertclydeAuthor Commented:
Client was only interested in mapping the drives of the low usage workstation. Adding the PC to the domain wasn't a priority with the client.
0

Featured Post

Get your problem seen by more experts

Be seen. Boost your question’s priority for more expert views and faster solutions

Tackle projects and never again get stuck behind a technical roadblock.
Join Now