Re: Win Server 2003 login delay

From: Marc Reynolds [MSFT] (marcrey_at_online.microsoft.com)
Date: 02/23/04


Date: Mon, 23 Feb 2004 15:08:18 -0600

Make sure that the clients are configured to use the internal DNS server
that contains your DNS records for your domain and NOT an ISP DNS server.

-- 
Thanks,
Marc Reynolds
Microsoft Technical Support
This posting is provided "AS IS" with no warranties, and confers no rights.
"entech" <anonymous@discussions.microsoft.com> wrote in message
news:1523701c3fa39$2fd8c0c0$a401280a@phx.gbl...
> This newly installed server is experiencing "very long"
> delays for user login.  Clients are waiting 10 -15 minutes
> for login from Win 2000 and Win XP pc's.
>
> Also, network map are being lost overnight.
>
> Thank you.
>
> Entech


Relevant Pages

  • Re: AD clients can no longer connect to DC in 2003
    ... perhaps you should look at the clients. ... Verify that the clients are pointing to an existing, internal DNS server ... However it does not prove that the correct SRV records are present. ... >net start netlogin>>That should get logins going again. ...
    (microsoft.public.windows.server.active_directory)
  • Re: nslookup
    ... and switch to NetBIOS resolution so you cannot be sure what you ... NSLookup will NOT use the built-in name cache nor the hosts file NOR ... DNS server to check so you can determine if SOME DNS server is working ... servers are hosting dhcp successfully giving IP's to clients. ...
    (microsoft.public.windows.server.dns)
  • RE: NT to AD upgrade question (advanced)
    ... The DNS Server that is in the DMZ, ... I cannot manually change the DNS setting on the clients. ... transfers the AD Integrated zone from the DC. ...
    (microsoft.public.windows.server.migration)
  • Re: setup/configure internal domain dns server?
    ... the ISP provided dns servers and not the main domain controller but I ... AD must have a DNS server setup for the AD domain. ... DNS server to itself for DNS, use the actual IP address not 127.0.0.1. ... Point all AD clients to the DNS server setup for the AD domain ONLY (Servers ...
    (microsoft.public.windows.server.dns)
  • Re: setup/configure internal domain dns server?
    ... the ISP provided dns servers and not the main domain controller but I ... AD must have a DNS server setup for the AD domain. ... DNS server to itself for DNS, use the actual IP address not 127.0.0.1. ... Point all AD clients to the DNS server setup for the AD domain ONLY (Servers ...
    (microsoft.public.windows.server.dns)