cannot join WinXP to Windows 2000 domain

[Russell]

I have previously been successful joining WinXP PC to this Win2000 domain.
Have 2 new PCs with WinXP SP3 that will not join the domain. dcdiag.txt
output is show below. nslookup resolves the server name fine. I do not
have reverse DNS zone configured. (never needed that in past for joining PC
to this domain). I'm stumped. Any suggestions appreciated. Russell

------dcdiag.txt ___
The domain name ccs 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.

DNS was successfully queried for the service location (SRV) resource record
used to locate a domain controller for domain ccs:

The query was for the SRV record for _ldap._tcp.dc._msdcs.ccs
The following domain controllers were identified by the query:
ccsserver.ccs

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.
- Domain controllers registered in DNS are not connected to the network or
are not running.
For information about correcting this problem, click Help.
-----

 

[Meinolf Weber]

Hello Russell,

What is the error message during the join process?
Also you mix a bit 2 different items, client join problem and DC diagnostic/troubleshooting
tools. So if you think there are domain problems run dcdiag, netdiag and
repadmin /showreps and post the complete output here. For the clients check
that they have the correct ip settings, subnet mask and only domain internal
DNS server. Make sure that no firewall is enabled.

Best regards

Meinolf Weber
Disclaimer: This posting is provided "AS IS" with no warranties, and confers
no rights.
** Please do NOT email, only reply to Newsgroups
** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm

 

[Russell]

Below is the error message when attempting to join domain. It finds the DC.
nslookup can resolve the DC both forward and backward, so it seems that the
A record for DC must be right.

Now, here is the odd situation. This W2000 DC (Domain1) is using another
server W2003 DC (Domain2) for it's DNS and the LAN's DHCP services. (I
think this was done so the LAN would have a single DHCP server.)

I would even be willing to move the W2000 DNS services to reside on the
Domain1 DC if that would solve problem. I'm not sure how to get all the DNS
records set up for Active Directory if not done as part of the original
dcpromo.

Any further advice appreciated. Russell

-----
DNS was successfully queried for the service location (SRV) resource record
used to locate a domain controller for domain ccs:
The query was for the SRV record for _ldap._tcp.dc._msdcs.ccs
The following domain controllers were identified by the query:
ccsserver.ccs

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.
- Domain controllers registered in DNS are not connected to the network or
are not running.
For information about correcting this problem, click Help.
Search the Web:
domain name

 

[Meinolf Weber]

Hello Russell,

Please post the output from netdiag /v and dcdiag /v. Additional post an
unedited ipconfig /all from both servers and the client machine.

Best regards

Meinolf Weber
Disclaimer: This posting is provided "AS IS" with no warranties, and confers
no rights.
** Please do NOT email, only reply to Newsgroups
** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm

 

[Ace Fekay [MVP]]

In

I have previously been successful joining WinXP PC to this Win2000
domain. Have 2 new PCs with WinXP SP3 that will not join the domain.
dcdiag.txt output is show below. nslookup resolves the server name
fine. I do not have reverse DNS zone configured. (never needed that
in past for joining PC to this domain). I'm stumped. Any
suggestions appreciated. Russell
------dcdiag.txt ___
The domain name ccs 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.
DNS was successfully queried for the service location (SRV) resource
record used to locate a domain controller for domain ccs:

The query was for the SRV record for _ldap._tcp.dc._msdcs.ccs
The following domain controllers were identified by the query:
ccsserver.ccs

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.
- Domain controllers registered in DNS are not connected to the
network or are not running.
For information about correcting this problem, click Help.
-----

Based on the error message you provided, and assuming it is unedited and
correct, (" The query was for the SRV record for _ldap._tcp.dc._msdcs.ccs"),
it apparently seems you have a single label AD DNS domain name called 'ccs'
which is apparently causing the problem. DNS requires a minimum of two
hierarchal levels. Simply, the DNS name should have been something to the
extent of ccs.com, ccs.net, ccs.russell, etc.

The NETBios name could still be CCS. No problem there, but AD solely uses
DNS. DNS single label names are extremely problematic.

XP SP2 and newer have problems querying DNS for a resolution with DNS single
label names.

There are a number of ways to fix it:

1. Build a new pristine domain and migrate everything over using ADMT. If
Exchange is installed, install it on the new domain and use ExMerge to
migrate mailboxes and pub folders.
2. Upgrade to Windows 2003 domain and use the rendom tool to rename it
properly. If Exchange is installed, it will hugely complicate this method.
3. Bandaid it, but not suggested or recommended. You may still have
problems. See the following link for more info:

300684 - Information About Configuring Windows 2000 for Domains with
Single-Label DNS Names
http://support.microsoft.com/?id=300684

--
Regards,
Ace

This posting is provided "AS-IS" with no warranties or guarantees and
confers no rights.

Ace Fekay, MCSE 2003 & 2000, MCSA 2003 & 2000, MCSE+I, MCT,
MVP Microsoft MVP - Directory Services
Microsoft Certified Trainer

For urgent issues, you may want to contact Microsoft PSS directly. Please
check http://support.microsoft.com for regional support phone numbers.

Infinite Diversities in Infinite Combinations

 

[Hank Arnold (MVP)]

I have previously been successful joining WinXP PC to this Win2000 domain.
Have 2 new PCs with WinXP SP3 that will not join the domain. dcdiag.txt
output is show below. nslookup resolves the server name fine. I do not
have reverse DNS zone configured. (never needed that in past for joining PC
to this domain). I'm stumped. Any suggestions appreciated. Russell

------dcdiag.txt ___
The domain name ccs 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.

DNS was successfully queried for the service location (SRV) resource record
used to locate a domain controller for domain ccs:

The query was for the SRV record for _ldap._tcp.dc._msdcs.ccs
The following domain controllers were identified by the query:
ccsserver.ccs

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.
- Domain controllers registered in DNS are not connected to the network or
are not running.
For information about correcting this problem, click Help.

I just ran into a similar problem last week. I was at a remote location
and unable to join an XP workstation to the "HOSPICE" domain. All the
servers (and DCs) are at the primary site connected over a point to
point T1 line)

The problem was resolved when I joined the "HOSPICE.LOCAL" domain
instead of the "HOSPICE" domain.

Maybe something similar for you??

--

Regards,
Hank Arnold
Microsoft MVP
Windows Server - Directory Services

 

[Ace Fekay [MVP]]

In

I just ran into a similar problem last week. I was at a remote
location and unable to join an XP workstation to the "HOSPICE"
domain. All the servers (and DCs) are at the primary site connected
over a point to point T1 line)

The problem was resolved when I joined the "HOSPICE.LOCAL" domain
instead of the "HOSPICE" domain.

Maybe something similar for you??

Hi Hank,

If he hasn't edited the error messages, I *believe* his problem may be there
is no TLD (such as ".local") on his domain name, which makes it a single
lable name, so he wouldn't be able to do that.

I think you got lucky your customer's DNS domain name was correctly created
at inception. I think the problem not being able to join using HOSPICS
NetBIOS name may indicate a lack of NetBIOS name resolution issue across
subnets. WINS would be answer for that, especially if all the DCs are at
their primary site.

Ace

 

[Hank Arnold (MVP)]

In

Hi Hank,

If he hasn't edited the error messages, I *believe* his problem may be there
is no TLD (such as ".local") on his domain name, which makes it a single
lable name, so he wouldn't be able to do that.

I think you got lucky your customer's DNS domain name was correctly created
at inception. I think the problem not being able to join using HOSPICS
NetBIOS name may indicate a lack of NetBIOS name resolution issue across
subnets. WINS would be answer for that, especially if all the DCs are at
their primary site.

Ace

Thanks for the tip........ Naming the domain (I'm the "customer",
by the way) is just about one of the very few things that these
so-called consultants did correctly (can you spell "Exchange Circular
Logging"?)...

--

Regards,
Hank Arnold
Microsoft MVP
Windows Server - Directory Services

 

[Ace Fekay [MVP]]

In

Thanks for the tip........ Naming the domain (I'm the "customer",
by the way) is just about one of the very few things that these
so-called consultants did correctly (can you spell "Exchange Circular
Logging"?)...

Circular logging? Why? Well, at least they got the name right!

 

[Russell]

I've collected all of this info. but the newsgroup will not let me post
saying it is too large. I even tryed to break it into smaller pieces, but
still was not small enough.

I really wish I could let you see it because I cannot see anything that is
wrong from these outputs.

 

[Meinolf Weber]

Hello Russell,

Lets start with ipconfig /all and dcdiag and netdiag without the /v switch.

Best regards

Meinolf Weber
Disclaimer: This posting is provided "AS IS" with no warranties, and confers
no rights.
** Please do NOT email, only reply to Newsgroups
** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm

 

[Russell]

ipconfigs

Hello Russell,

Please post the output from netdiag /v and dcdiag /v. Additional post an
unedited ipconfig /all from both servers and the client machine.

Best regards

Meinolf Weber
Disclaimer: This posting is provided "AS IS" with no warranties, and
confers
no rights.
** Please do NOT email, only reply to Newsgroups
** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm

 

[Russell]

fyi, the problem ended up being related to having a single label windows
domain name. Very frustrating trying to identify this problem because
dcdiag and netdiag did not identify it. Everything used to work fine and it
seems the problem was related to changes in Microsoft SPs. Anyway, the
final resolution is described in
300684 - Information About Configuring Windows 2000 for Domains with
Single-Label DNS Names
http://support.microsoft.com/?id=300684

 

[Russell]

Hi Ace, Many thanks!!!!!

the article you referred to below solved my problem which was related to
having a single label window domain dns name. The registery changes
corrected this difficult to resolve problem. Russell

 

[Ace Fekay [MVP]]

In

Hi Ace, Many thanks!!!!!

the article you referred to below solved my problem which was related
to having a single label window domain dns name. The registery
changes corrected this difficult to resolve problem. Russell

Sorry for my late response. Tied up with some things.

Glad to hear that. Keep in mind the reg entries are just bandaids. I hope
you are planning to fix it by migrating to a new domain or upgrading to 2003
and using the domain rename tool.

Ace