Client Can't join Domain

  • Thread starter Thread starter scott
  • Start date Start date
S

scott

I have a Win2003 standard ed. Parent PDC and Child Domain PDC. I also have 3
WinXP Client pc's. I recently had to reformat 1 XP Client. After a fresh
install, and setting up TCP/IP Settings, I'm unable to join either the
parent or child domain. It doesn't prompt for credentials, instead it
displays an error message saying 'A domain controller for the domain could
not be contacted.' I'm logging in fine from other 2 clients and everything
seems to be working fine with both servers, what could be preventing me to
join either domains? I've had this domain running fine for over a year.

Any help?



After clicking DETAILS, XP reported the below error ...

ERROR
================================

Note: This information is intended for a network administrator. If you are
not your network's administrator, notify the administrator that you received
this information, which has been recorded in the file
C:\WINDOWS\debug\dcdiag.txt.

The domain name bytex might be a NetBIOS domain name. If this is the case,
verify that the domain name is properly registered with WINS.

If you are certain that the name is not a NetBIOS domain name, then the
following information can help you troubleshoot your DNS configuration.

The following error occurred when DNS was queried for the service location
(SRV) resource record used to locate a domain controller for domain bytex:

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.bytex

Common causes of this error include the following:

- The DNS SRV record is not registered in DNS.

- One or more of the following zones do not include delegation to its child
zone:

bytex
.. (the root zone)

For information about correcting this problem, click Help.
 
It sounds like the connection between the client and one of the DCs cannot be
made. Make sure you can ping your DCs by name. Since the other clients are
running OK I would think the problem does not rely within your DCs, but the
client itself. Is there another machine you can try joining to the domain
(or rejoining)? This would help isolate the problem. Also, check the event
logs on the problem client.

Hope this helps.
AJD, MCSE
 
Verify your DNS settings on the client point to the DC of the domain you are trying to join.

--
Tony Eversole MCSE, MCSA, Net+, A+
I have a Win2003 standard ed. Parent PDC and Child Domain PDC. I also have 3
WinXP Client pc's. I recently had to reformat 1 XP Client. After a fresh
install, and setting up TCP/IP Settings, I'm unable to join either the
parent or child domain. It doesn't prompt for credentials, instead it
displays an error message saying 'A domain controller for the domain could
not be contacted.' I'm logging in fine from other 2 clients and everything
seems to be working fine with both servers, what could be preventing me to
join either domains? I've had this domain running fine for over a year.

Any help?



After clicking DETAILS, XP reported the below error ...

ERROR
================================

Note: This information is intended for a network administrator. If you are
not your network's administrator, notify the administrator that you received
this information, which has been recorded in the file
C:\WINDOWS\debug\dcdiag.txt.

The domain name bytex might be a NetBIOS domain name. If this is the case,
verify that the domain name is properly registered with WINS.

If you are certain that the name is not a NetBIOS domain name, then the
following information can help you troubleshoot your DNS configuration.

The following error occurred when DNS was queried for the service location
(SRV) resource record used to locate a domain controller for domain bytex:

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.bytex

Common causes of this error include the following:

- The DNS SRV record is not registered in DNS.

- One or more of the following zones do not include delegation to its child
zone:

bytex
. (the root zone)

For information about correcting this problem, click Help.
 
A standard name to IP address test (ping) doesn't prove DNS is working. For
a true test, you need to query the SRV records that Windows calls. In this
case, as the client is not a domain member and is therefore not site aware
(yet), the generic LDAP record _ldap._tcp.dc._msdcs.domain-name.com.

The %systemroot%\debug\netsetup.log (which the details tab references) is
what you need to look at.

This sounds like the client is not configured to use the internal DNS
server.

--

Paul Williams

http://www.msresource.net/
http://forums.msresource.net/

It sounds like the connection between the client and one of the DCs cannot
be
made. Make sure you can ping your DCs by name. Since the other clients are
running OK I would think the problem does not rely within your DCs, but the
client itself. Is there another machine you can try joining to the domain
(or rejoining)? This would help isolate the problem. Also, check the event
logs on the problem client.

Hope this helps.
AJD, MCSE
 
The firewall allows this kind of communication by default, and only blocks
incoming traffic that wasn't initiated by the client. Unless the poster has
changed the firewall settings this is not likely the problem. DNS is the
most likely culprit.

--

Paul Williams

http://www.msresource.net/
http://forums.msresource.net/

Check that the windows firewall is not hampering you from contacting
the dc.

jOSH...
 
_ldap._tcp.dc._msdcs.bytex

That's the issue there.

Try entering the FQDN name.

Or are you using a single-label domain name? If so, this is bad...


--

Paul Williams

http://www.msresource.net/
http://forums.msresource.net/

I have a Win2003 standard ed. Parent PDC and Child Domain PDC. I also have 3
WinXP Client pc's. I recently had to reformat 1 XP Client. After a fresh
install, and setting up TCP/IP Settings, I'm unable to join either the
parent or child domain. It doesn't prompt for credentials, instead it
displays an error message saying 'A domain controller for the domain could
not be contacted.' I'm logging in fine from other 2 clients and everything
seems to be working fine with both servers, what could be preventing me to
join either domains? I've had this domain running fine for over a year.

Any help?



After clicking DETAILS, XP reported the below error ...

ERROR
================================

Note: This information is intended for a network administrator. If you are
not your network's administrator, notify the administrator that you received
this information, which has been recorded in the file
C:\WINDOWS\debug\dcdiag.txt.

The domain name bytex might be a NetBIOS domain name. If this is the case,
verify that the domain name is properly registered with WINS.

If you are certain that the name is not a NetBIOS domain name, then the
following information can help you troubleshoot your DNS configuration.

The following error occurred when DNS was queried for the service location
(SRV) resource record used to locate a domain controller for domain bytex:

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.bytex

Common causes of this error include the following:

- The DNS SRV record is not registered in DNS.

- One or more of the following zones do not include delegation to its child
zone:

bytex
.. (the root zone)

For information about correcting this problem, click Help.
 
I'm afraid to try and join another working client to the domain band mess it
up since they are already joined and working.
 
How do I run this query?


ptwilliams said:
A standard name to IP address test (ping) doesn't prove DNS is working.
For
a true test, you need to query the SRV records that Windows calls. In
this
case, as the client is not a domain member and is therefore not site aware
(yet), the generic LDAP record _ldap._tcp.dc._msdcs.domain-name.com.

The %systemroot%\debug\netsetup.log (which the details tab references) is
what you need to look at.

This sounds like the client is not configured to use the internal DNS
server.

--

Paul Williams

http://www.msresource.net/
http://forums.msresource.net/

It sounds like the connection between the client and one of the DCs cannot
be
made. Make sure you can ping your DCs by name. Since the other clients
are
running OK I would think the problem does not rely within your DCs, but
the
client itself. Is there another machine you can try joining to the domain
(or rejoining)? This would help isolate the problem. Also, check the
event
logs on the problem client.

Hope this helps.
AJD, MCSE
Click to expand...
 
It was DNS issue, thanks guys.


ptwilliams said:
That's the issue there.

Try entering the FQDN name.

Or are you using a single-label domain name? If so, this is bad...


--

Paul Williams

http://www.msresource.net/
http://forums.msresource.net/

I have a Win2003 standard ed. Parent PDC and Child Domain PDC. I also have
3
WinXP Client pc's. I recently had to reformat 1 XP Client. After a fresh
install, and setting up TCP/IP Settings, I'm unable to join either the
parent or child domain. It doesn't prompt for credentials, instead it
displays an error message saying 'A domain controller for the domain could
not be contacted.' I'm logging in fine from other 2 clients and everything
seems to be working fine with both servers, what could be preventing me to
join either domains? I've had this domain running fine for over a year.

Any help?



After clicking DETAILS, XP reported the below error ...

ERROR
================================

Note: This information is intended for a network administrator. If you
are
not your network's administrator, notify the administrator that you
received
this information, which has been recorded in the file
C:\WINDOWS\debug\dcdiag.txt.

The domain name bytex might be a NetBIOS domain name. If this is the
case,
verify that the domain name is properly registered with WINS.

If you are certain that the name is not a NetBIOS domain name, then the
following information can help you troubleshoot your DNS configuration.

The following error occurred when DNS was queried for the service location
(SRV) resource record used to locate a domain controller for domain bytex:

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.bytex

Common causes of this error include the following:

- The DNS SRV record is not registered in DNS.

- One or more of the following zones do not include delegation to its
child
zone:

bytex
. (the root zone)

For information about correcting this problem, click Help.
Click to expand...
 
Back
Top