Re: Slooow login to win 2k domain controller

From: Miha Pihler (mihap-news_at_atlantis.si)
Date: 11/06/04 

Date: Sat, 6 Nov 2004 17:58:22 +0100

Brian,

Can you check Event logs (System and Application) on your DC and on your
client for any errors?

Mike

"BA" <topstang@hotmail.com> wrote in message
news:2815457b.0411060850.88deaf0@posting.google.com...
> Thanks for the help Mike,
> I had my dns on the DC set to the local host 127.0.0.1, I changed it
> to the actual internal ip 192.168.0.3 but the same problem is
> happening. My dhcp server on the DC is sending out that same address
> for the dns to the workstation. I actually do have another computer
> on the network; it is a laptop running 2k pro. It, about a week ago,
> could log in fine without all the delays, but now I can't get it to
> log in at all(The system cannot log you on now because the domain * is
> not available). It receives the ip configuration from the DC but
> cannot resolve domain names with the dns. If I statically assign
> one(Using Bellsouth's) and login locally. I can surf the net but still
> not login to the DC. The xp and 2k are plugged into the same router,
> everything was working fine with the 2k machine, and I only had a
> problem with the XP workstation. Also, on the XP workstation I
> flushed the dns cache and still am able to surf the net so I know the
> dns is working. Thanks again for any help/suggestions.
> Brian
>
> "Miha Pihler" <mihap-news@atlantis.si> wrote in message
> news:<uOkl8f3wEHA.1396@tk2msftngp13.phx.gbl>...
>> Hi Brian,
>>
>> How do you have DNS configured under TCP/IP on DC? It should point back
>> to
>> itself (enter DCs own IP under preferred DNS under TCP/IP). After you
>> make
>> such change, restart NetLogon service on DC. Also, make sure that you
>> client
>> (Windows XP) is pointing towards DC for DNS (again under TCP/IP).
>>
>> I hope this helps,
>>
>> Mike
>>
>> "BA" <topstang@hotmail.com> wrote in message
>> news:2815457b.0411051110.430f3f36@posting.google.com...
>> > Hello everyone,
>> > I am just getting into the server side of windows. I have setup a 2k
>> > domain controller which I am logging into from a XP Pro workstation.
>> > The only problem is that it's taking almost an hour to log into a new
>> > account for the first time. After that it takes about 20 minutes. The
>> > DC is providing DNS and DHCP to the workstation, but I do not have
>> > WINS running. Also, when I go to the DC through My Network Places and
>> > I click on a folder it takes 2,3,4 minutes to open it up. Are these
>> > problems related? The hardware should definitly run 2K properly and
>> > these are the only 2 computers on the network. Any help I would
>> > really appreciate.
>> > Thanks,
>> > Brian

Relevant Pages

  • Re: Name resolution issues on W2K Pro
    ... Workstation 1 can not resolve any names on the internet. ... > able to ping the router and the ISP's 2 DNS servers. ... > the windows client fixed this. ... Which Windows client are you talking about here? ...
    (microsoft.public.win2000.dns)
  • Re: XP Client Connection Problem
    ... I'm not the most knowledgable about DNS but I ... > now consists of a single server and single workstation. ... > The server is Windows 2003 and is set up for DNS, ... This first client is also an XP ...
    (microsoft.public.windows.server.dns)
  • Re: Adding XP computer to Domain - access denied
    ... In your NIC configuration on the XP client make sure that the primary DNS ... client is looking to join it, then it must find the server that is hosting ... > The XP workstation and server 2003 computer can communicate, ...
    (microsoft.public.windows.server.active_directory)
  • Re: Slow Desktop loading
    ... DC with one workstation? ... secondary dns on the TCP/IP settings. ... I can add a new host to one DNS server and it propagates to the ... as it measures ANY client, while Windows Netmon take into account itself ...
    (microsoft.public.windows.server.general)
  • RE: server confusion about workstation ip address
    ... Register the IP address from the workstation. ... Sound to me like you have only DHCP setup to manage IP addresses and not the ... then you changed it to a static address and the record in DNS ... > I have an xp sp2 client that has a static IP address. ...
    (microsoft.public.windows.server.dns)