Extremely slow local logon after hardware failure

We have a Windows Server 2003 (installed on a DELL POWEREDGE) which
serves as the DC for our small office - we have only about 20 computers
in the domain.

One month ago this server suffered a hardware failure. After it was
fixed, we began experiencing extremely slow local logon. But logon from
other computers are normal as before.

It used to take only seconds to logon, but now it takes at least 10
seconds. Are there any known solutions to this problem?

Edward Yang wrote:
> We have a Windows Server 2003 (installed on a DELL POWEREDGE) which
> serves as the DC for our small office - we have only about 20 computers
> in the domain.
>
> One month ago this server suffered a hardware failure. After it was
> fixed, we began experiencing extremely slow local logon. But logon from
> other computers are normal as before.
>
> It used to take only seconds to logon, but now it takes at least 10
> seconds. Are there any known solutions to this problem?

More information on this problem:

>ping localhost
(after about 12 seconds, it produces the following information)
Pinging dellpoweredge.[domainname].local [::1] from ::1 with 32 bytes of
data:

Reply from ::1: time<1ms
Reply from ::1: time<1ms
Reply from ::1: time<1ms
Reply from ::1: time<1ms

Ping statistics for ::1:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms

In news:%(E-Mail Removed),
Edward Yang <(E-Mail Removed)> typed:
> We have a Windows Server 2003 (installed on a DELL POWEREDGE) which
> serves as the DC for our small office - we have only about 20
> computers in the domain.
>
> One month ago this server suffered a hardware failure. After it was
> fixed, we began experiencing extremely slow local logon. But logon
> from other computers are normal as before.
>
> It used to take only seconds to logon, but now it takes at least 10
> seconds. Are there any known solutions to this problem?

Event logs?
And what was the nature of the hardware failure?

Lanwench [MVP - Exchange] wrote:
> In news:%(E-Mail Removed),
> Edward Yang <(E-Mail Removed)> typed:
>> We have a Windows Server 2003 (installed on a DELL POWEREDGE) which
>> serves as the DC for our small office - we have only about 20
>> computers in the domain.
>>
>> One month ago this server suffered a hardware failure. After it was
>> fixed, we began experiencing extremely slow local logon. But logon
>> from other computers are normal as before.
>>
>> It used to take only seconds to logon, but now it takes at least 10
>> seconds. Are there any known solutions to this problem?
>
> Event logs?
> And what was the nature of the hardware failure?
>
>
The event log are lost since it is a server for testing only. We
discovered viruses on the computer. That may be causing the problem.

Edward Yang wrote:

> Lanwench [MVP - Exchange] wrote:
>
>> In news:%(E-Mail Removed),
>> Edward Yang <(E-Mail Removed)> typed:
>>
>>> We have a Windows Server 2003 (installed on a DELL POWEREDGE) which
>>> serves as the DC for our small office - we have only about 20
>>> computers in the domain.
>>>
>>> One month ago this server suffered a hardware failure. After it was
>>> fixed, we began experiencing extremely slow local logon. But logon
>>> from other computers are normal as before.
>>>
>>> It used to take only seconds to logon, but now it takes at least 10
>>> seconds. Are there any known solutions to this problem?
>>
>>
>> Event logs?
>> And what was the nature of the hardware failure?
>>
> The event log are lost since it is a server for testing only. We
> discovered viruses on the computer. That may be causing the problem.

Get rid of the viruses and see if things improve.

--
The e-mail address in our reply-to line is reversed in an attempt to
minimize spam. Our true address is of the form che...@prodigy.net.

CJT wrote:
> Edward Yang wrote:
>
>> Lanwench [MVP - Exchange] wrote:
>>
>>> In news:%(E-Mail Removed),
>>> Edward Yang <(E-Mail Removed)> typed:
>>>
>>>> We have a Windows Server 2003 (installed on a DELL POWEREDGE) which
>>>> serves as the DC for our small office - we have only about 20
>>>> computers in the domain.
>>>>
>>>> One month ago this server suffered a hardware failure. After it was
>>>> fixed, we began experiencing extremely slow local logon. But logon
>>>> from other computers are normal as before.
>>>>
>>>> It used to take only seconds to logon, but now it takes at least 10
>>>> seconds. Are there any known solutions to this problem?
>>>
>>>
>>> Event logs?
>>> And what was the nature of the hardware failure?
>>>
>> The event log are lost since it is a server for testing only. We
>> discovered viruses on the computer. That may be causing the problem.
>
> Get rid of the viruses and see if things improve.
>

I think we have removed the viruses. But the problem still exists.

I read thru Event Logs but found no evident proofs of what is wrong.

Edward Yang wrote:

> CJT wrote:
>
>> Edward Yang wrote:
>>
>>> Lanwench [MVP - Exchange] wrote:
>>>
>>>> In news:%(E-Mail Removed),
>>>> Edward Yang <(E-Mail Removed)> typed:
>>>>
>>>>> We have a Windows Server 2003 (installed on a DELL POWEREDGE) which
>>>>> serves as the DC for our small office - we have only about 20
>>>>> computers in the domain.
>>>>>
>>>>> One month ago this server suffered a hardware failure. After it was
>>>>> fixed, we began experiencing extremely slow local logon. But logon
>>>>> from other computers are normal as before.
>>>>>
>>>>> It used to take only seconds to logon, but now it takes at least 10
>>>>> seconds. Are there any known solutions to this problem?
>>>>
>>>>
>>>>
>>>> Event logs?
>>>> And what was the nature of the hardware failure?
>>>>
>>> The event log are lost since it is a server for testing only. We
>>> discovered viruses on the computer. That may be causing the problem.
>>
>>
>> Get rid of the viruses and see if things improve.
>>
>
> I think we have removed the viruses. But the problem still exists.
>
Apparently not. Did you do a bare metal re-install?


> I read thru Event Logs but found no evident proofs of what is wrong.


--
The e-mail address in our reply-to line is reversed in an attempt to
minimize spam. Our true address is of the form che...@prodigy.net.

>>
>> I think we have removed the viruses. But the problem still exists.
>>
> Apparently not. Did you do a bare metal re-install?
>
>
Sorry, we do not have time to do a re-install.

Can anyone redirect me to resources that may have answers to this
problem? Thanks.

Edward Yang wrote:
>>>
>>> I think we have removed the viruses. But the problem still exists.
>>>
>> Apparently not. Did you do a bare metal re-install?
>>
>>
> Sorry, we do not have time to do a re-install.
>
> Can anyone redirect me to resources that may have answers to this
> problem? Thanks.
>
1st thing to check - do you have any UPS Software insalled? see:
http://support.microsoft.com/?kbid=905716&SD=tech

If that's not it:
Have you ran DCDIAG to see if any issues are highlighted?

Ian

Ian wrote:
> Edward Yang wrote:
>>>>
>>>> I think we have removed the viruses. But the problem still exists.
>>>>
>>> Apparently not. Did you do a bare metal re-install?
>>>
>>>
>> Sorry, we do not have time to do a re-install.
>>
>> Can anyone redirect me to resources that may have answers to this
>> problem? Thanks.
>>
> 1st thing to check - do you have any UPS Software insalled? see:
> http://support.microsoft.com/?kbid=905716&SD=tech
>
> If that's not it:
> Have you ran DCDIAG to see if any issues are highlighted?
>
> Ian

After running DCDIAG, I think there are serious problems, but I cannot
determine what they are.

Here is the result of DCDIAG:

Domain Controller Diagnosis

Performing initial setup:
[{computer}] Directory Binding Error -2146892976:
The system detected a possible attempt to compromise security.
Please ensure that you can contact the server that authenticated you.
This may limit some of the tests that can be performed.
Done gathering initial info.

Doing initial required tests

Testing server: Default-First-Site\{computer}
Starting test: Connectivity
[{computer}] DsBindWithSpnEx() failed with error -2146892976,
The system detected a possible attempt to compromise security.
Please ensure that you can contact the server that authenticated you..
......................... {computer} failed test Connectivity

Doing primary tests

Testing server: Default-First-Site\{computer}
Skipping all tests, because server {computer} is
not responding to directory service requests

Running partition tests on : TAPI3Directory
Starting test: CrossRefValidation
......................... TAPI3Directory passed test
CrossRefValidation
Starting test: CheckSDRefDom
......................... TAPI3Directory passed test CheckSDRefDom

Running partition tests on : ForestDnsZones
Starting test: CrossRefValidation
......................... ForestDnsZones passed test
CrossRefValidation
Starting test: CheckSDRefDom
......................... ForestDnsZones passed test CheckSDRefDom

Running partition tests on : DomainDnsZones
Starting test: CrossRefValidation
......................... DomainDnsZones passed test
CrossRefValidation
Starting test: CheckSDRefDom
......................... DomainDnsZones passed test CheckSDRefDom

Running partition tests on : Schema
Starting test: CrossRefValidation
......................... Schema passed test CrossRefValidation
Starting test: CheckSDRefDom
......................... Schema passed test CheckSDRefDom

Running partition tests on : Configuration
Starting test: CrossRefValidation
......................... Configuration passed test
CrossRefValidation
Starting test: CheckSDRefDom
......................... Configuration passed test CheckSDRefDom

Running partition tests on : {domain}
Starting test: CrossRefValidation
......................... {domain} passed test CrossRefValidation
Starting test: CheckSDRefDom
......................... {domain} passed test CheckSDRefDom

Running enterprise tests on : {domain.local}
Starting test: Intersite
......................... {domain.local} passed test Intersite
Starting test: FsmoCheck
......................... {domain.local} passed test FsmoCheck