slow logon in windows 2003

  • Thread starter Thread starter Ricardo
  • Start date Start date
You may want to check the DNS settings for your clients. If you are
running Windows 2000/XP clients they will use DNS to find the DC, if this
fails they check WINS then do a broadcast. If your sever and workstations
are not working off of the same DNS structure that is capable of DDNS
(Dynamic DNS) then Active Directory will not work and client logons will be
quite slow.
The second possibility is that you are pushing a very large number of GP
(Group Policy) objects down to the client. This could also have a
signifigant effect on client logon times.
Finally if you are using roaming profiles logon time can be quite
lengthy if users have large amounts of data in My Documents or the Desktop.
This issue can be mitigated by using folder redirection on the My Documents
directory and the Desktop. I hope this helps a little.

Sean
 
-----Original Message-----
You may want to check the DNS settings for your clients. If you are
running Windows 2000/XP clients they will use DNS to find the DC, if this
fails they check WINS then do a broadcast. If your sever and workstations
are not working off of the same DNS structure that is capable of DDNS
(Dynamic DNS) then Active Directory will not work and client logons will be
quite slow.
The second possibility is that you are pushing a very large number of GP
(Group Policy) objects down to the client. This could also have a
signifigant effect on client logon times.
Finally if you are using roaming profiles logon time can be quite
lengthy if users have large amounts of data in My Documents or the Desktop.
This issue can be mitigated by using folder redirection on the My Documents
directory and the Desktop. I hope this helps a little.

Sean




.
Ricardo,

Further to what Sean added, take a look at the following
two MSKB Article that describe how WIN2000 / WINXP Pro
clients find a Domain Controller:

http://support.microsoft.com/default.aspx?scid=KB;en-
us;247811

http://support.microsoft.com/default.aspx?scid=kb;
[LN];314861

DNS is usually at issue here!

HTH,

Cary
 
Back
Top