Why can't my domain controller be contacted?

[Guest]

Trying to join a new pc running xp pro sp2 to a domain.

Windows firewall has been disabled. Norton has been uninstalled.
TCP/IP settings are identical to other machines on the network, some running
xp pro sp1, others w2000pro. Server runs Server 2003.
PC was added to list of active computers.

I can connect to the internet through the LAN. I can ping the server. The
server recognizes me. When I try to join the domain, I get this message:

A domain controller for the domain xxx could not be contacted.
Ensure that the domain name is typed correctly (check!)
Some other stuff, then:
DNS was successfully queried for the service location (SRV) resource record
used to locate a domain controller for domain xxx.
The query was for the SRV record for_ldap_tcp._msdcs.xxx
The following domain controllers were identified by the query:
server.xxx
Common causes of this error include:
-Host (A) records that map the name of the domain controller to its IP
addresses are missing or contain incorrect addresses (well then, how come
everybody else's pc can find it?)
-Domain controllers registered in DNS are not connected to the network or
are not running (ditto my last comment!)

Does anybody out there have a clue as to what is going on?

Thanks....

And to think, I used to love computers! Arrrggghhhh!

 

[Chuck]

Trying to join a new pc running xp pro sp2 to a domain.

Windows firewall has been disabled. Norton has been uninstalled.
TCP/IP settings are identical to other machines on the network, some running
xp pro sp1, others w2000pro. Server runs Server 2003.
PC was added to list of active computers.

I can connect to the internet through the LAN. I can ping the server. The
server recognizes me. When I try to join the domain, I get this message:

A domain controller for the domain xxx could not be contacted.
Ensure that the domain name is typed correctly (check!)
Some other stuff, then:
DNS was successfully queried for the service location (SRV) resource record
used to locate a domain controller for domain xxx.
The query was for the SRV record for_ldap_tcp._msdcs.xxx
The following domain controllers were identified by the query:
server.xxx
Common causes of this error include:
-Host (A) records that map the name of the domain controller to its IP
addresses are missing or contain incorrect addresses (well then, how come
everybody else's pc can find it?)
-Domain controllers registered in DNS are not connected to the network or
are not running (ditto my last comment!)

Does anybody out there have a clue as to what is going on?

Thanks....

And to think, I used to love computers! Arrrggghhhh!

You have to setup a domain properly to support Windows XP clients.
<http://nitecruzr.blogspot.com/2005/05/windows-xp-on-nt-domain.html>

 

[Daniel Crichton]

Chuck wrote on 10 Aug 2005 16:34:02 -0500:

You have to setup a domain properly to support Windows XP clients.
<http://nitecruzr.blogspot.com/2005/05/windows-xp-on-nt-domain.html>

The OP clearly stated it's a Windows 2003 domain server, so this article is
useless.

FWIW, I had no trouble getting my XP Pro clients here to work on a Windows
2000 domain server, so Windows 2003 should have been painless.

As to the messages, check the Windows 2003 Server DNS (server.xxx) for the
_ldap_tcp._msdcs.xxx SRV record - it's possible that the the other machines
aren't using that record (as they're all XP SP1 or W2K rather than XP SP2).
As it is right now, it doesn't look right anyway - on my network there is a
SRV record for _ldap._tcp._msdcs.xxx (notice the . between _ldap and _tcp),
if the messages were copied and pasted then for some reason it's looking for
an incorrect SRV record.

Dan

 

[Daniel Crichton]

Please ignore part of my other reply (which hasn't appeared yet so I can
reply to it :|) about the article being useless as it's for NT domains - I
missed the part about it being the W2K3 server settings. However, it's still
useless - the OP clearly stated he already has XP Pro SP1 machines working
on the domain so the W2K3 server settings must already be correct.

Dan

 

[Guest]

Thanks for the info Chuck and Daniel. Let me take another look. I'll let
you know what I find.

 

[Guest]

Say, I just noticed an information message on my server:

Source: Schannel

No suitable default server credential exists on this system. This will
prevent server applications that expect to make use of the system default
credentials from accepting SSL connections. An example of such an
application is the directory server. Applicaltions that manage their own
credentials, such as the internet information server, are not affected by
this.

Might this have anything to do with my problem? I just thought that with
SP2's upped security features........?

 

[Guest]

After 3 days, hours on the phone with tech support and countless attempts,
checks, double-checks, re-boots, etc. etc. ad infinitum.... I have decided
that this is the result of a compatibility issue between xp, server 2003 and
the NIC card (Intel Pro/100 VE). I discovered that I actually did have
another client running XP Pro sp2 that is running just fine. Different NIC
card.

If swapping the NIC doesn't work.....I'll be back!