Don't know if this is the list for this ... just spank me and tell me to
go away if it is not ...

A client had their battery on their domain controller go bad ... all the
"time" in their domain get messed up ... battery has been replaced, time
has been reset ...

since then, once a week, their exchange server would get the error below
and could not log in to the domain ... they would enable/disable the
computer account for exchange and everything would start working ... 

now they still get the error, but nothing seems to be affected (i.e. it
appears as if everything is working) 

is this something they should worry about? what  should they look for
and where? (I have a feeling it is a DNS issue as it occurs every week
... )

thanks for any help ...

oh yeah ... exchange 2000, native , 200 domain ..

Mike

Event Message
========================================================================
Record Number:  10168900
Event Type:     Failure Audit
Event Source:   Security
Event Category: Account Logon
Event ID:       675
Date:           2/11/2005
Time:           09:08
User:           \\NT AUTHORITY\SYSTEM
Computer:       BES1KAPPS
Description:

Pre-authentication failed:
        User Name:              BES1EXCHANGE$
        User ID:                OURGROUP\BES1EXCHANGE$
        Service Name:           krbtgt/OURGROUP.MIA
        Pre-Authentication Type:        0x2
        Failure Code:           0x18
        Client Address:         172.20.1.5

_________________________________________________________________
List posting FAQ:       http://www.swinc.com/resource/exch_faq.htm
Web Interface: http://intm-dl.sparklist.com/read/?forum=exchange
To subscribe: http://e-newsletters.internet.com/discussionlists.html/
To unsubscribe send a blank email to [EMAIL PROTECTED]
Exchange List admin:    [EMAIL PROTECTED]
To unsubscribe via postal mail, please contact us at:
Jupitermedia Corp.
Attn: Discussion List Management
475 Park Avenue South
New York, NY 10016

Please include the email address which you have been contacted with.

Reply via email to