Re: Slow domain logon (with detail try out)

If you are using roaming profiles:

"The speed of the logon is directly related the size of the profile and the
speed of the network. There are a number of things that you can do to limit
the size of the profile:

Redirect large folders such as My Documents this will reduce the amount of
data copied to/from the computer at logon and logoff.

Exclude large folders from the roaming profile. By default large folders
such as Local Settings, Temp and Temporary Internet Files folders do not
roam. You can use the "Exclude directories in roaming profile" Group Policy
Setting to add new folders to the exclusion list; once included in the
policy these folders will not be copied to the local machine at logon, nor
copied back to the server at logoff.

Set the Slow Network timeout appropriately if you're logging on over a slow
link. When a slow link is detected, the system uses the locally cached
profile, rather than copying the profile from the server.

Don't save large files inside the user profile."

If you are not using roaming profiles and your clients are running XP, try
the fast logon feature:

http://support.microsoft.com/kb/305293/en-us

Doug Sherman
MCSE, MCSA, MCP+I, MVP

"Peter CCH" <petercch.wodoy@xxxxxxxxx> wrote in message
news:1148031956.592138.254720@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
When I was first install the OS and join it into domain, it works fine,
the login almost instantly ... around 1 seconds.

But after a day, it takes 2 minutes to logon (after a lot of software
had been installed).
It only happens to some machine, all the others still remain instant
logon without delay.
All the machine is installed with the same softwares.
I'd search around and try those solutions, but doesn't work out.

Tried but fail to resolve actions:
1. Uninstall "Client for Microsoft Network", restart, install it again
2. Uninstall all the other network component (clients, services,
protocol) [except TCP/IP], then restart and install all of them again
3. Remove from domain, restart, join domain again, restart
4. Try login at safe mode with networking
5. Put in static IP

* No logon script for the particular user

All the action above had been tried one by one, but the problem still
remain unsolved, the client still needs to takes 2 minutes to logon to
domain.

I'd check the settings:
Server (Active Directory, DNS, DHCP all in one server)
Static IP
IP: 10.1.1.10
Primary DNS: 10.1.1.10
Secondary DNS: 10.1.0.50

Client machine
DHCP
IP: 10.1.2.112
Primary DNS: 10.1.1.10
Secondary DNS: 10.1.0.50

I'd done some testing and suspecting the delay was caused by the
process of registering the IP into DNS.

1. Delete the client IP from DHCP and DNS at the DC server.
2. (not sure how it works, but the machine will always get the same IP
from DHCP)
So, I run a infinite ping to the IP (10.1.2.112) from the DC server
3. Boot the client machine and logon (TCP/IP configured to get IP from
DHCP)
4. Monitor the client machine, DHCP list and DNS (forward & reverse
lookup zone)
Across the time:
30 seconds - client machine still at the logon screen (client
machine)
DHCP not yet have the client IP assigned
(server)
DNS not yet have the client IP registered
(server)
Server cannot ping the client IP (server)
60 seconds - client machine still at the logon screen (client
machine)
DHCP ALREADY assign IP to the client and have
it in the DHCP list (server)
DNS not yet have the client IP registered
(server)
Server cannot ping the client IP (server)
90 seconds - client machine pass through the logon screen and
loading the rest of the program (client machine)
DHCP already assign IP to the client and have
it in the DHCP list (server)
DNS have the client IP REGISTERED in the list
(server)
Server SUCCESSFULLY ping to client machine
(server)

It seems like only when the IP of the client machine is registered into
DNS then only the user can pass through the logon screen and continue
with the rest of the startup program loading.

It always happen in this way, after entering the user name and
password, and logon.
Then will need to wait for around 2 minute until the logon screen
disappear and continue loading the rest of the startup program.

If I leave the machine at the logon screen without entering the user
name and password, after waiting for around 2 minutes, then only I
enter user name and password and logon, I have instant logon to the
machine.

Anyone have any idea what else I can do to resolve this slow logon
problem?

Thanks.



Peter CCH



.

Relevant Pages

  • Cant delegate/share to a group
    ... I am running Exchange 2000 SP3 on SBS 2000 on a network with one server box. ... The client operation failed". ... Successful Network Logon: ...
    (microsoft.public.exchange2000.general)
  • Cant delegate/share to a group
    ... I am running Exchange 2000 SP3 on SBS 2000 on a network with one server box. ... The client operation failed". ... Successful Network Logon: ...
    (microsoft.public.backoffice.smallbiz2000)
  • Re: Network Connection
    ... For the clients make sure that you use following policy to prevent logon with cached credentials: ... Additional post an unedited ipconfig /all from the DC/DNS server and a problem machine so we can exclude DNS configuration problems. ... From last December I have been experiencing network connection problem ... out client pc some with Vista and the rest with XP. ...
    (microsoft.public.windows.server.networking)
  • Re: XP join SBS 2003
    ... I've created both the users and client machine via Add User Wizard. ... Everything else on the server seems to be functioning perfect, ... I also didn't modify the server network card. ...
    (microsoft.public.windows.server.sbs)
  • Re: Still strange not fully working DNS server
    ... At logon on the network with a client the error event ID 1054 appears. ... The new server is global catalog and has joined the domain as a member, ... If the clients are domain members they have to be registered in your DNS ...
    (microsoft.public.windows.server.dns)
Loading