Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Can't join NT machine to domain

Status
Not open for further replies.

chunky28

Technical User
Apr 14, 2003
121
GB
I recently reconfigured my network after purchasing a CheckPoint firewall.

This involved changing all IP addresses to a private range (192.168.2.1-192.168.2.14)

However since changing this I have managed to join every PC to the domain except for one NT machine.

When I attempt to join it I just get the message:

"The domain controller for this domain cannot be located"

- I have successfully joined another NT machine to the domain.
- The gateway, subnet mask is correct.
- All PC's use identical hosts file
This is the contents of the hosts files. mailgate is the dc and webserver is the NT machine I am having problems with:
127.0.0.1 localhost
192.168.2.12 oracledatabaseconsulting.com webserver.datachase.local webserver
192.168.2.9 mailgate.datachase.local mailgate
192.168.2.10 infrastructure.datachase.local infrastructure
192.168.2.11 ocsmid.datachase.local ocsmid
192.168.2.13 9iserver.datachase.local 9iserver
192.168.1.1 firewallint.datachase.local firewallint
193.195.xxx.xxx firewallext.datachase.local firewallext
- I can ping the domain controller from the NT machine
- I can run tracert mailgate (2000 server machine and dc) from the NT machine successfully.
- The dns server has an entry for the NT machine with the correct IP address
- I have added the NT machine to Active Directory Users and Computers


Any ideas what the problem could be? Anyone?

Thanks

Charlie
 
On the NT4 machine, can you ping the FULL domain name of the DC?
dc.domain.com or whatever?

pinging by ip or hostname doesn't test the full requirements joining a domain requires. You NEED to have successful dns resolution for the domain.

I've had a similar problem. I could ping the name and ip but couldn't register with dns. I had a dns resolution problem. Your nt4 machine might not be getting dns resolution.
 
what if you added pre-loads to the host file, assuming 9iserver is GC DC

192.168.2.13 9iserver.datachase.local 9iserver #PRE #DOM:yourdomname

then nbtstat -RR
then nbtstat -R

and add to domain.


01110000
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top