Re: cannot join WinXP to Windows 2000 domain

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" <meiweb(nospam)@gmx.de> wrote in message
news:ff16fb66a10928ca9b8770d82565@xxxxxxxxxxxxxxxxxxxxxxx
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

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" <meiweb(nospam)@gmx.de> wrote in message
news:ff16fb66a0eab8ca9ab647b6ec2e@xxxxxxxxxxxxxxxxxxxxxxx

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




.

Relevant Pages

  • Issues migrating SBS 2003 domain to Server 2008 Standard
    ... We are stuck migrating our SBS 2003 domain to Server 2008. ... Fatal Error:DsGetDcName (SRV-EXCH) call failed, ... Verify your Domain Name Sysytem (DNS) is ... network connectivity to a domain controller. ...
    (microsoft.public.windows.server.sbs)
  • Re: Issues migrating SBS 2003 domain to Server 2008 Standard
    ... Since you have migrated to standard server 2008 you would be better served posting in a Standard server NG. ... Event String: ... Verify your Domain Name Sysytem (DNS) is ... network connectivity to a domain controller. ...
    (microsoft.public.windows.server.sbs)
  • Re: SBS 2003 and Replication Errors with Remote DC
    ... alpha server as soon as you can to get things going. ... A simple DNS replication test is to create a host record in the SBS server ... Domain Controller Diagnosis ...
    (microsoft.public.windows.server.sbs)
  • Re: Issues migrating SBS 2003 domain to Server 2008 Standard
    ... One thought, when you introduced the Windows Server 2008 and before making them DC's, did you extend the schema on the SBS 2003 server? ... Event String: ... Verify your Domain Name Sysytem (DNS) is ... network connectivity to a domain controller. ...
    (microsoft.public.windows.server.sbs)
  • Re: Big trouble with DC in China
    ... > Since then, this server has so may errors in the event logs (KCC, ... > DNS, FRS) that I wouldnt know where to start. ... > Source domain controller address: ...
    (microsoft.public.windows.server.active_directory)