Re: Windows 2000 Server: Joining Domain from XP

Tech-Archive recommends: Speed Up your PC by fixing your registry

From: Steven L Umbach (sumbach_at_nospam-ameritech.net)
Date: 02/27/04 

Date: Fri, 27 Feb 2004 14:41:21 GMT

I think you still have a dns problem. Make sure that you change the dc
preferred dns server to be it's actual IP and not 127.0.0.1. The nslookup
error is common if you do not have a reverse zone configured for your dns
zone. See the KB link below about verifying that _srv records were properly
created. Also run netdiag and nslookup on your XP box after you have
verified that the dc is in good helth and properly configured. --- Steve

http://support.microsoft.com/?kbid=241515 -- how to verify _srv records
http://support.microsoft.com/default.aspx?scid=kb%3Ben-us%3B321708 -- netdiag.

"Thomas Nguyen" <bdtomcat@yahoo.com, bao.nguyen@itiserv.com> wrote in
message news:43264146-B159-40AF-B36D-EE961E1DAFB8@microsoft.com...
> I have changed all ip address for all services to point to the DC
(192.168.0.100) as the DC is the actual computer running these services (no
separate WINS/DNS/DHCP Server) and even deleted the "." domain as instructed
on the DNS webpage. There is only one conection: DC <--> XP Pro. All
firewalls have also been shutdown. Now when I try to join the domain
(test.home.net), I am asked to provide the name/password fields. After doing
so, I get another message:
>
> "The following error occurred attempting to join the domain
'test.home.net.' The network path was not found."
>
> Is this somehow still related to the previous problem? or is it a whole
new problem altogether. (I am able to ping the DC, the DC cannot ping back
(XP Pro Machine).
>
> Also, upon running nslookup on the DC I get this message: "Can't find
server name for address 192.168.0.100: Timed out
>
Default Server: UnKnown
>
Address: 192.168.0.100
>
> -Thomas
>
> ----- Steven L Umbach wrote: -----
>
> Change the domain controllers preferred dns server to by it's actual
Ip address and
> not 127.0.0.1. Then reboot it and run dcdiag on it to see if it
passes all the tests.
> Dcdiag is located on the install cdrom in the tolos/support folder
where you want to
> run the setup there. If all looks good, then configure your XP Pro
computer to have
> the domain controller only as it's preferred dns server, make sure
the built in ICF
> firewall is disabled and try again. See the link below for more info
on dns. ---
> Steve
>
> http://support.microsoft.com/default.aspx?scid=kb%3Ben-us%3B291382
>
> "Thomas Nguyen" <bdtomcat@yahoo.com, bao.nguyen@itiserv.com> wrote in
message
> news:EECE8894-AE9D-45D0-92A6-B6A88ECEABF0@microsoft.com...
> > Hello everyone. I've installed Windows 2000 Server onto a computer
and followed
> "Configure Your Server" wizard to make the computer my first server
(DC) for the
> domain "test.home.net". After the computer restarts, the default ip
set for the DC's
> network card is 10.10.1.1 and the Preferred DNS is 127.0.0.1
(loopback). I changed
> the IP from 10.10.1.1 to 192.168.0.100 (the computer I'm trying to
join has static IP
> of 192.168.0.1). I also changed all the services (DHCP, WINS, DNS,
etc.) to use the
> DC's ip, as all services run on the same DC.
> >> I then go to the other computer (Windows XP) and try to join the
domain. I've tried
> to put Test as the domain as well as the FQDN (test.home.net). Both
give me this
> message:
> >> ----------------------------------
> > 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.
> >> An error occurred when DNS was queried for the service location
(SRV) resource
> record used to locate a domain controller for domain TEST.HOME.NET.
> >> The error was: "No DNS servers configured for local system."
> > (error code 0x0000267C DNS_ERROR_NO_DNS_SERVERS)
> >> The query was for the SRV record for
_ldap._tcp.dc._msdcs.TEST.HOME.NET
> >> For more information, click Help.
> > -----------------------------------------------
> > Please give me some tips or pointers to lead me in the right
direction. Your
> response is greatly appreciated.
> >> -Thomas
>
>
>

Relevant Pages

  • Re: Cant logon to domain from WinXP
    ... Verify that the XP computer is configured to use the domain controller as ... it's only preferred dns server in it's tcp/ip properties and as shown with ... preferred dns server. ... Get message that says my account has been disabled. ...
    (microsoft.public.windows.server.security)
  • Re: Newbie policy & security groups ?: SBS/Win 2003 AD
    ... a few minutes for RSOP to complete. ... Another potential problem is if your domain controller or domain clients are ... must point to itself as it's preferred dns server and the domain computers ...
    (microsoft.public.win2000.security)
  • Re: Lost Domain Server and Password Failure
    ... First you need to make sure that the domain controller is configured ... itself as it's ONLY preferred dns server in tcp/ip properties via it's ... static IP address and them the clients must point to the domain controller ... them in a workgroup first before attempting to join the domain. ...
    (microsoft.public.win2000.security)
  • Re: Very slow login
    ... Check the preferred DNS server setting on the problem XP boxes and make sure that it points to the domain controller. ... identical computers with same set of apps installed. ... The other 2 take 15 min to login then speed seems normal. ...
    (microsoft.public.windowsxp.general)
  • Re: WinXP computer not authenicating properly on Win2k Domain Controller
    ... it's preferred dns server. ... Such errors would indicate there is a problem locating the domain controller ... > new win2k domain, I am not granted Administrator-level rights. ... when I apply a group policy to the OU ...
    (microsoft.public.win2000.networking)