XP Error

R

Rajesh

I have a Windows2000 Advance Server as a Domain Controller
with Active Directory & DNS.

When i try to join the WIN XP client to the domain i get
the following error. IP Address of the server is
148.172.135.11 & on the client side it is 10.128.184.146
onwards..


"A domain controller for the domain could not be contacted

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

Common causes of this error include the following:

- The DNS SRV record is not registered in DNS."

Can you pls. help us to resolve this problem.??
 
R

Ron Lowe

Rajesh said:
I have a Windows2000 Advance Server as a Domain Controller
with Active Directory & DNS.

When i try to join the WIN XP client to the domain i get
the following error. IP Address of the server is
148.172.135.11 & on the client side it is 10.128.184.146
onwards..


"A domain controller for the domain could not be contacted

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

Common causes of this error include the following:

- The DNS SRV record is not registered in DNS."

Can you pls. help us to resolve this problem.??

The XP machine can't find a Domain Controller
entry in the DNS server it's using.

XP differs from previous versions of windows in that it uses
DNS as it's primary name resolution method for finding domain
controllers:

How Domain Controllers Are Located in Windows XP
http://support.microsoft.com/default.aspx?scid=kb;en-us;314861

If DNS is misconfigured, XP will spend a lot of time waiting for it to
timeout before it tries using legacy NT4 sytle NetBIOS.
( Which may or may not work. )

1) Ensure that the XP clients are all configured to point to the local
DNS server which hosts the AD domain. That will probably be the
win2k server itself.
They should NOT be pointing an an ISP's DNS server.
An 'ipconfig /all' on the XP box should reveal ONLY the domain's
DNS server.

( you should use the DHCP server to push out the local DNS server
address. )

2) Ensure DNS server on win2k is configured to permit dynamic updates.

3) Ensure the win2k server points to itself as a DNS server.

4) For external ( internet ) name resolution, specify your ISP's DNS server
not on the clients, but in the 'forwarders' tab of the local win2k DNS
server.

On the DNS server, if you cannot access the 'Forwarders' and 'Root Hints'
tabs because they are greyed out, that is because there is a root zone (".")
present on the DNS server. You MUST delete this root zone to permit the
server to forward unresolved queries to yout ISP or the root servers:

HOWTO: Remove the Root Zone (Dot Zone)
http://support.microsoft.com/default.aspx?kbid=298148

The following articles may assist you in setting up DNS correctly:

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
 
G

Guest

-----Original Message-----


The XP machine can't find a Domain Controller
entry in the DNS server it's using.

XP differs from previous versions of windows in that it uses
DNS as it's primary name resolution method for finding domain
controllers:

How Domain Controllers Are Located in Windows XP
http://support.microsoft.com/default.aspx?scid=kb;en- us;314861

If DNS is misconfigured, XP will spend a lot of time waiting for it to
timeout before it tries using legacy NT4 sytle NetBIOS.
( Which may or may not work. )

1) Ensure that the XP clients are all configured to point to the local
DNS server which hosts the AD domain. That will probably be the
win2k server itself.
They should NOT be pointing an an ISP's DNS server.
An 'ipconfig /all' on the XP box should reveal ONLY the domain's
DNS server.

( you should use the DHCP server to push out the local DNS server
address. )

2) Ensure DNS server on win2k is configured to permit dynamic updates.

3) Ensure the win2k server points to itself as a DNS server.

4) For external ( internet ) name resolution, specify your ISP's DNS server
not on the clients, but in the 'forwarders' tab of the local win2k DNS
server.

On the DNS server, if you cannot access the 'Forwarders' and 'Root Hints'
tabs because they are greyed out, that is because there is a root zone (".")
present on the DNS server. You MUST delete this root zone to permit the
server to forward unresolved queries to yout ISP or the root servers:

HOWTO: Remove the Root Zone (Dot Zone)
http://support.microsoft.com/default.aspx?kbid=298148

The following articles may assist you in setting up DNS correctly:

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


--
Best Regards,
Ron Lowe
MS-MVP Windows Networking


.
Hello,

I checked on DNS Server & everything whatever you have
mentioned seems to be all OK. infact to give you more
input's one of the winxp client got joined to the domain
properly & when i tried joining 2ns winxp cleint which is
a fresh installation of winxp o/s, i was getting the above
mentioned error.

Can you pls. help me on the same.
 
R

Ron Lowe

I checked on DNS Server & everything whatever you have
mentioned seems to be all OK. infact to give you more
input's one of the winxp client got joined to the domain
properly & when i tried joining 2ns winxp cleint which is
a fresh installation of winxp o/s, i was getting the above
mentioned error.

Can you pls. help me on the same.


There's FOR SURE a DNS problem here.
Go to a command prompt on the problem machine.

Type "nslookup".
Then type "set type=all"
Then type "_ldap._tcp.dc._msdcs.domainname
(where domainname is the name of your domain).

Nslookup returns one or more SRV service location records in the following
format
hostname.domainname internet address = ipaddress

where hostname is the host name of a domain controller, domainname is the
domain to which the domain controller belongs, and ipaddress is the domain
controller's Internet Protocol (IP) address.

Then 'exit' will quit you out of nslookup.

Here's a screen-dump of me doing this on an XP machine joined to my domain,
"homenet.local.":

C:\Documents and Settings\Ron.HOMENET>nslookup
Default Server: homenetdc01.homenet.local
Address: 81.187.191.78
set type=all
_ldap._tcp.dc._msdcs.homenet.local.
Server: homenetdc01.homenet.local
Address: 81.187.191.78

_ldap._tcp.dc._msdcs.homenet.local SRV service location:
priority = 0
weight = 100
port = 389
svr hostname = homenetdc01.homenet.local
homenetdc01.homenet.local internet address = 81.187.191.78

Do you get the same?

R-click in your command prompt window, and select 'mark';
Highlight all the text, starting with the line where you invoke nslookup,
just like I did.
Hit 'enter' to copy the highlighted text.

Reply to this post and place the mouse cursor in the reply window,
and hit Crtl-V to paste the dump into a reply.
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top