Dear all I have a W8K SBS server and I seeing a lot of events in the security log Log Name: Security Source: Microsoft-Windows-Security-Auditing Date: 31/03/2011 11:54:53 Event ID: 4625 Task Category: Logon Level: Information Keywords: Audit Failure User: N/A Computer: servername.domain.local Description: An account failed to log on. Subject: Security ID: SYSTEM Account Name: servername$ Account Domain: domain Logon ID: 0x3e7 Logon Type: 3 Account For Which Logon Failed: Security ID: NULL SID Account Name: servername$ Account Domain: Failure Information: Failure Reason: Unknown user name or bad password. Status: 0xc000006d Sub Status: 0xc0000064 Process Information: Caller Process ID: 0x1254 Caller Process Name: C:\Program Files\Microsoft\Exchange Server\Bin\Microsoft.Exchange.Search.ExSearch.exe Network Information: Workstation Name: servername Source Network Address: - Source Port: - Detailed Authentication Information: Logon Process: Advapi Authentication Package: Negotiate Transited Services: - Package Name (NTLM only): - Key Length: 0 This event is generated when a logon request fails. It is generated on the computer where access was attempted. The Subject fields indicate the account on the local system which requested the logon. This is most commonly a service such as the Server service, or a local process such as Winlogon.exe or Services.exe. The Logon Type field indicates the kind of logon that was requested. The most common types are 2 (interactive) and 3 (network). The Process Information fields indicate which account and process on the system requested the logon. The Network Information fields indicate where a remote logon request originated. Workstation name is not always available and may be left blank in some cases. The authentication information fields provide detailed information about this specific logon request. - Transited services indicate which intermediate services have participated in this logon request. - Package name indicates which sub-protocol was used among the NTLM protocols. - Key length indicates the length of the generated session key. This will be 0 if no session key was requested. Event Xml: <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"> <System> <Provider Name="Microsoft-Windows-Security-Auditing" Guid="{54849625-5478-4994-a5ba-3e3b0328c30d}" /> <EventID>4625</EventID> <Version>0</Version> <Level>0</Level> <Task>12544</Task> <Opcode>0</Opcode> <Keywords>0x8010000000000000</Keywords> <TimeCreated SystemTime="2011-03-31T10:54:53.323Z" /> <EventRecordID>133502399</EventRecordID> <Correlation /> <Execution ProcessID="632" ThreadID="8516" /> <Channel>Security</Channel> <Computer>servername.domain.local</Computer> <Security /> </System> <EventData> <Data Name="SubjectUserSid">S-1-5-18</Data> <Data Name="SubjectUserName">servername$</Data> <Data Name="SubjectDomainName">domain</Data> <Data Name="SubjectLogonId">0x3e7</Data> <Data Name="TargetUserSid">S-1-0-0</Data> <Data Name="TargetUserName">servername$</Data> <Data Name="TargetDomainName"> </Data> <Data Name="Status">0xc000006d</Data> <Data Name="FailureReason">%%2313</Data> <Data Name="SubStatus">0xc0000064</Data> <Data Name="LogonType">3</Data> <Data Name="LogonProcessName">Advapi </Data> <Data Name="AuthenticationPackageName">Negotiate</Data> <Data Name="WorkstationName">servername</Data> <Data Name="TransmittedServices">-</Data> <Data Name="LmPackageName">-</Data> <Data Name="KeyLength">0</Data> <Data Name="ProcessId">0x1254</Data> <Data Name="ProcessName">C:\Program Files\Microsoft\Exchange Server\Bin\Microsoft.Exchange.Search.ExSearch.exe</Data> <Data Name="IpAddress">-</Data> <Data Name="IpPort">-</Data> </EventData> </Event> can anyone help me understand what is going on

it seems you posted twice. http://social.technet.microsoft.com/Forums/en-US/winserversecurity/thread/9385406b-c65d-48b5-8e7b-e81eb3bf29e6 are the two servers (W2k8 std and SBS) in the same domain?

Looks to be a little bug. http://support.microsoft.com/kb/957713 "This should be fixed in the Exchange Rollup Update 4 release which is currently targeted to be released in September of 2008. It can be ignored otherwise." Have you installed the latest Exchange updates? If not, that would be a good first step.

Hi Desmond The two posts are both different, for this post the server is a SBS 2008 server