Hey all,
The problem we are experiencing is with Windows Server 2000, installed
with Service Pack 3.
The environment is: AD, DNS, DHCP and WINS.
We got 1 DC on that site.
Client computers that are joined to the domain are experiencing slow
initilization times.
The slow appears before the GINA initialization - where a user need to
input login information (Preparing network connections or Applying
Computer Settings...).
The slowness is not always appears, only sometimes !
We can reproduce this problem by rebooting computers a couple of times.
Name resolution are checked and found to be working correctly (on the server
and clients), using
DNSLint, DCDIAG, NETDIAG, eventvwr and manual checkup of SRV records.
I think that the problem relates to a service which is sometimes loads
before another, which is critical for the before-GINA initialization
part.
The clients are running Windows 2000 Pro SP3 and have the following
applications installed:
1. Norton Antivirus 8.1.
2. SMS 2.0.
Most of the hardware is more then today's enterprise standard: P4 2.0,
256MB.
Running latest software (drivers...).
I think Hardware, Naming resolution or network isn't the issue here.
I have tried to disable SMS, NAV and other services but it doesn't
solved the problem. also tried to manually give ip to avoid the use of
DHCP.
I decided to do a netlogon logging, on the times we got slow logons an
message is logged on the netlogon.log saying wmi: waiting for service
to start.
I have compared this to a times where the slow doesn't appears and
found this message to be the direct connection to our slowness
problem.
I wonder if there is any way to log the Service Control Manger
activity, so we can point on a specific service that causes the
slowness?
(I've tried to remotely manage the computer but it need a service
which isn't started yet).
Any one can help me on this, I'm kidda stuck with this problem and I don't
have
a clue.
Thanks.
Regards.
|