Cannot join a server to the domain

[Brett]

I have a Windows 2000 server, that was originally upgraded
from NT, long story, buts lets just sufice that this had
to be done. Anyhow, the server had a drive crash this
weekend (no raid) so I was placed into a situation of
doing a restore from the weekend full tape. I install the
OS, during which the server joins the domain just fine. I
restore the server from a tape, and it comes back just
fine, except for the NIC is now set to DHCP, where it was
and always has been static. Anyhow, I change the IP
address back, to the static address, and the server can no
longer log onto the domain. I remove the server from the
domain, remove the account out of AD, and when I try to
add it back using the NetBios name of our domain it gives
me a big error right away, which states that there is an
error validating the name, which could be caused by a DNS
lookup problem. If I use the FQDN of our domain in AD, it
actually brings up a user name and password box, but no
matter how I format the username (is.. domainname\user
trying both netbios and FQDN) it tells me the network
location cannot be reached. Any ideas on this?

 

[Robert L [MS-MVP]]

this may help quote form http://www25.brinkster.com/ChicagoTech
Can't join or logon domain
Symptoms: When attempting to join a domain, you may receive one of the
following error messages 1) "The following error occurred attempting to join
domain "example.com": The network location cannot be reached."
2) "Network path not found."
3) "The remote computer is not available."
4) "The domain name "Domain" is either invalid or doesn't exist."
5) "The specified domain either does not exist or could not be contacted."

Resolutions: 1) Make sure the File and Print Sharing for Microsoft Networks
option is not enabled on the Windows 2000 domain controller.
2) If you receive "Network path not found.", it is possible you are using an
incorrect IP for the Domain Name Service (DNS) server. Make sure you have
correct DNS and WINS settings. You also can use nslookup or ping to check if
the client points to the correct DNS.
3) If you get "The specified domain either does not exist or could not be
contacted", check if there is network protocol installed on the computer.
4) If you try to join the domain by using the NetBIOS domain name, you are
successful but not the fully qualified domain name (FQDN) of the domain, and
receive "The following error occurred attempting to join domain
"example.com": The network location cannot be reached." To fix this problem,
enable the TCP/IP NetBIOS Helper Service is not running on the client
computer.
5) If WINS is not enabled on the computer and the computer is located in
different TCP/IP subnet than the NT 4.0 PDC, you can configure the computer
to use the LMHOSTS file for NetBIOS name resolution.
6) If you have two NICs in the client, make sure that you can ping DNS
server.
For more and other information, go to
http://www25.brinkster.com/ChicagoTech

Don't send e-mail or reply to me except you need consulting services.
Posting on MS newsgroup will benefit all readers and you may get more help.

Robert Lin, MS-MVP, MCSE & CNE
Windows & Network Support, Tips and FAQs on
http://www25.brinkster.com/ChicagoTech
This posting is provided "AS IS" with no warranties.

 

[Robert L [MS-MVP]]

try enable netbios over tcp/ip on xp, can w2k join the domain?

--
For more and other information, go to
http://www25.brinkster.com/ChicagoTech

Don't send e-mail or reply to me except you need consulting services.
Posting on MS newsgroup will benefit all readers and you may get more help.

Robert Lin, MS-MVP, MCSE & CNE
Windows & Network Support, Tips and FAQs on
http://www25.brinkster.com/ChicagoTech
This posting is provided "AS IS" with no warranties.