Re: Applying gpos after logon very slow



Usually slow logins are a result of the clients DNS being mis configured.
All AD clients must point to the DNS server set up for the AD domain only.

What DNS server do your clients use for DNS?

hth
DDS

"flabs" <flabs@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:F21F2B9C-CA00-46A7-B5F9-ED875290DF36@xxxxxxxxxxxxxxxx
Hello Newsgroup members.

we are using windows 2003 AD in 2000 native mode. 2 domain controllers the
first DC holds all fsmo roles and GC both DCs are in the same site. All
Users
uses local Userprofiles.

Our Problem is, the computer is started and a user is looging in with his
valid creds, the logon screen goes away and a new window pops up "computer
settings will be applied" and after this a new text "user settings will be
applied" this logon is very slow.
after a user entered his correct password needs the computer 4 -5 mins to
apply the computer and user settings before users can begin his work on
the
machine why is applying the gpo so slow?

Thanks Florian


.



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)