Windows XP Client cannot connect to win2k domain controller

  • Thread starter Thread starter jogeedaklown
  • Start date Start date
J

jogeedaklown

Hello,
OK, here's my situation. I have a Windows XP client trying to connect
to a Windows 2000 Server Domain controller. I get the usual error
message.


The error was: "DNS name does not exist."
(error code 0x0000232B RCODE_NAME_ERROR)

The query was for the SRV record for _ldap._tcp.dc._msdcs.DOMAIN-NAME


I've added the DOMAIN-NAME as well as the hostname of the DC server
into my lmhosts file and I still have the same problem. Here's my
lmhost file config.

10.1.1.99 DC-SERVER #PRE #DOM:DOMAIN-NAME
10.1.1.99 "DOMAIN-NAME \0x1b" #PRE
# IP Address "123456789012345*7890"

I've tried both the \0x1b and \0x1c and no luck.

But when I change my DNS server to point to DC-SERVER, things work.
Unfortunately, I don't want to use DC-SERVER for DNS.

I've seen in news postings that if my client is behind a firewall and
NAT'ed that using the lmhosts file to resolve names won't work. Could
that be the problem I am encountering? Or is there something else that
I'm missing?

Bear with me everyone. I'm still kinda of new to the Windows
networking stuff. Thanks for being patient with me!

Jose Torres
 
But when I change my DNS server to point to DC-SERVER, things work.
Unfortunately, I don't want to use DC-SERVER for DNS.
Click to expand...

Sorry, that is a requirement for Active directory Systems.
That is the way it must be.
 
But when I change my DNS server to point to DC-SERVER, things work.
Unfortunately, I don't want to use DC-SERVER for DNS.
Click to expand...

What does this mean? Which is your "DNS" server? The Win 2k DC or do you
have another DNS server? What is the "DC-Server"? Is the the Win 2k DC?

AD requires a DNS server set up for the AD domain. All AD clients must point
to the DNS server set up for the domain in order to "find" the domain.

Suggest you install DNS on the Win 2k DC. In the properties of TCP/IP point
the Win 2k server to itself for DNS, and point the XP client to the Win 2k
DNS server for DNS.

See:
Best Practices for DNS Client settings in Windows 2000 server and in Windows
Server 2003

http://support.microsoft.com/default.aspx?scid=kb;en-us;825036

Setting Up the Domain Name System for Active Directory

http://support.microsoft.com/default.aspx?scid=kb;en-us;237675

How to configure DNS for Internet access in Windows 2000

http://support.microsoft.com/default.aspx?scid=kb;en-us;300202



hth

DDS W 2k MVP MCSE
 
Danny said:
What does this mean? Which is your "DNS" server? The Win 2k DC or do you
have another DNS server? What is the "DC-Server"? Is the the Win 2k DC?
Click to expand...

The DNS Server is the Win 2k DC. I have other DNS servers but it does
not have DC-Server registered and where. That is why I attempted to
use the lmhosts file.
AD requires a DNS server set up for the AD domain. All AD clients must point
to the DNS server set up for the domain in order to "find" the domain.
Click to expand...

I was afraid of that. Oh well.
Suggest you install DNS on the Win 2k DC. In the properties of TCP/IP point
the Win 2k server to itself for DNS, and point the XP client to the Win 2k
DNS server for DNS.

See:
Best Practices for DNS Client settings in Windows 2000 server and in Windows
Server 2003

http://support.microsoft.com/default.aspx?scid=kb;en-us;825036

Setting Up the Domain Name System for Active Directory

http://support.microsoft.com/default.aspx?scid=kb;en-us;237675

How to configure DNS for Internet access in Windows 2000

http://support.microsoft.com/default.aspx?scid=kb;en-us;300202
Click to expand...

Thanks for the links, help and for the quick response!

Jose
 
Back
Top