Failure audit recurs for Vista system being merged to Win 2K domai

W

WT

It is a known issue that Vista system being merged to Win 2K domain will
generate the following errors.

Event Type: Failure Audit
Event Source: Security
Event Category: Account Logon
Event ID: 675
Date: 8/17/2009
Time: 8:10:43 AM
User: NT AUTHORITY\SYSTEM
Computer: <ServerName>
Description:
Pre-authentication failed:
User Name: <ComputerName>$
User ID: <DomainName>\<ComputerName>$
Service Name: krbtgt/<DomainName>.local
Pre-Authentication Type: 0x0
Failure Code: 0x19
Client Address: x.x.x.x

Event Type: Failure Audit
Event Source: Security
Event Category: Account Logon
Event ID: 677
Date: 8/17/2009
Time: 8:10:43 AM
User: NT AUTHORITY\SYSTEM
Computer: <ServerName>
Description:
Service Ticket Request Failed:
User Name: <ComputerName>$
User Domain: <DomainName>.LOCAL
Service Name: ldap/<ServerName>.<DomainName>.local/<DomainName>.local
Ticket Options: 0x40800000
Failure Code: 0x29
Client Address: x.x.x.x

Other errors will follow as for services eg. CIFS

Event Type: Failure Audit
Event Source: Security
Event Category: Account Logon
Event ID: 677
Date: 8/17/2009
Time: 8:10:51 AM
User: NT AUTHORITY\SYSTEM
Computer: <ServerName>
Description:
Service Ticket Request Failed:
User Name: <ComputerName>$
User Domain: <DomainName>.LOCAL
Service Name: cifs/<ServerName>.<DomainName>.local
Ticket Options: 0x40810000
Failure Code: 0x29
Client Address: x.x.x.x

The workaround is noted in the following KB.

http://support.microsoft.com/default.aspx/kb/824905

Are there any other solutions besides suppressing the errors as noted in the
KB.
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top