Windows Forum

Ask something
Discussion Locked

Problem joining XP Pro to NT Domain

0 helpful
8 replies

by wayne r. 1 view

Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

I have a user in a remote office who has upgraded his computer to Windows XP Professional.

The remote office is has a routed leased line connection to us.

The problem:

When the user is trying to join the computer to our domain it comes up with the error "A domain controller for the domain NAME could not be contacted...."

The name and password he is using when trying to join the domain have been given 'admin' and 'domain admin' permissions.

He is using the same TCP/IP settings that were previosly working fine on his old box.

He can ping our network.

Any ideas? (Apart from telling him to get a proper OS that isn't going to breach the network when it eventually decides to work!!).

All comments appreciated.

8 replies

by ketan_lakhani999

Have you get the lmhost file which says that that server is on the list.

Have you installed/configured any services on this PC ?.
If you have than you should reapply the service packs.

I hope that this helps

by wayne r.

The computer already has a valid LMHOSTS file.

No extra services or software have been installed yet.

Thanks anyway.

by gerald.brown

Client probably cannot resolve the Domain name to an IP address for a domain controller. Adding a LMHOSTS file with the correct entries to the client machine should resolve the problem. This file is normally located in C:\WINNT\SYSTEM32\DRIVERS\ETC and has no extension. A LMHOSTS.SAM (sample file) is in this directory and can be used to build a LMHOSTS file for your Domain.

Example entries:

102.54.94.97 rhinodc #DOM:rhino #The rhino domain PDC #PRE
102.54.94.99 zoobdc #DOM:rhino #BDC for rhino domain #PRE

NOTE: PDC is primary domain controller and BDC is backup domain controller.

**LMHOSTS is only used by the NBT (NetBIOS over TCP/IP) interface.

by merv amos

I have seen this problem in NT 4.0 many times.
Usually the wrong driver for the network adapter
has been selected.

by wayne r.

Correct driver, even tried downloading a newer driver, there wasn't one so I tried an older driver and this still didn't work.

by wayne r.

Managed to sort this one... Believe it or not simply removing the networking card and reinstalling it cured the problem.

This discussion is closed to new replies.