Cannot join domain-receve the network name cannot be found

[HummingbirdDM]

I tried to put a win2k sp3 client pc to join a domain (win2k advanced server, sp4, DC, have AD, DHCP and DNS installed), and I caanot join the domain (received the network name cannot be found message)

I can ping the server/DC, IP address. The nslookup on DC is working. Client PC can release/renew IP address, and the DC can browse the client shared folders. However, client PC cannot browse server resourses. I manupilate the TCP/IP tags (DNS tags) on client's PC without any success. Could someone help me? Thanks!

 

[zee7]

Is File and Printer sharing for Microsoft Networks checked in Lan Properties?

Adam
adamz@onq.com.au

 

[HummingbirdDM]

Yes, it is checked!

 

[GlenJohnson]

2003 has some bugs in it. Can you give us more details as to who's pinging who and such? Good luck.

Glen A. Johnson
Johnson Computer Consulting

http://www.johnsoncomputers.us

"The best fire does not flare up the soonest."
George Eliot (1819-1880); Englist novelist.

Want to get great answers to your Tek-Tips questions? Have a look at FAQ219-2884

 

[HummingbirdDM]

Glen:

*from DC: ping client IP and Clinet name: no problem
*from Client: ping DC/DNS/DHCP (the same server box) IP and DC server name: no problem
*client can release and renew IP
*DC can browse client but not from client to see DC.
*from DC: nslookup: no problem
*from client: manupilate TCP/IP-advanced tag, enter dns IP and typing several combination of dns suffix names
I try to uninstsall and reinstall TCP/IP
Change Client name, or add client from AD and they all fail.

Cannot join domain, received network name cannot be found message

Please advise, thanks!

 

[GlenJohnson]

Only one client or multiple?

Glen A. Johnson
Johnson Computer Consulting

http://www.johnsoncomputers.us

"The best fire does not flare up the soonest."
George Eliot (1819-1880); Englist novelist.

Want to get great answers to your Tek-Tips questions? Have a look at FAQ219-2884

 

[dholbrook]

I would check the the gateway and DNS TCP/IP settings on the new system. Are your using DHCP to provide this info to the new system? If so, check the values being provided to the clients, especially for the gateway address.

Also, just for kicks, does your DNS server point to itself first for DNS lookup?

Run IPCONFIG /ALL on the new system and on the DC and look carefully at the values received. It sounds like you have a mistake being passed to the client, so check the entries on the DHCP and DNS servers also.

HTH

David

 

[Seaspray0]

Ping the domain controller by it's Fully qualified domain name... (i.e. ping myserver.mydomain.mycom). Verify your DNS has service records in the _msdcs\dc\_tcp folder in the forward lookup zone for your domain. Use the DNS domain name and not the NetBios name when joining (i.e. use "mydomain.mycom" and not "mydomain&quot to the myserver.mydomain.mycom domain controller.

 

[svsawkar]

Also, what error messages are we seeing in the event logs of both the DC and the client.

This sounds like name resolution isn't working, and Seaspray has the best advice so far. Are the client and DC on the same hub?

/Siddharth

 

[john8188]

Seems to me you are trying to join a domain using the DC machine name instaed of the domain name