Hi, We are experiencing numerous logon failures by a system account on a newly installed 2008R2 Server running Symantec's CCS 11 application. The account seems to be invoked by a lsass.exe process. Please find logs below. We would love to find a way to stop these logon failures. Thanks a mill. Guy Log Name: Security Source: Microsoft-Windows-Security-Auditing Date: 2012/10/03 08:12:04 AM Event ID: 4625 Task Category: Logon Level: Information Keywords: Audit Failure User: N/A Computer: Server Description: An account failed to log on. Subject: Security ID: SYSTEM Account Name: SERVER$ Account Domain: DOMAIN Logon ID: 0x3e7 Logon Type: 3 Account For Which Logon Failed: Security ID: NULL SID Account Name: Account Domain: Failure Information: Failure Reason: Unknown user name or bad password. Status: 0xc000006d Sub Status: 0xc0000064 Process Information: Caller Process ID: 0x208 Caller Process Name: C:\Windows\System32\lsass.exe Network Information: Workstation Name: SERVER Source Network Address: - Source Port: - Detailed Authentication Information: Logon Process: Schannel Authentication Package: Kerberos 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="2012-10-03T06:12:04.377951200Z" /> <EventRecordID>601000</EventRecordID> <Correlation /> <Execution ProcessID="520" ThreadID="8972" /> <Channel>Security</Channel> <Computer>SERVER</Computer> <Security /> </System> <EventData> <Data Name="SubjectUserSid">S-1-5-18</Data> <Data Name="SubjectUserName">SERVER$</Data> <Data Name="SubjectDomainName">DOMAIN</Data> <Data Name="SubjectLogonId">0x3e7</Data> <Data Name="TargetUserSid">S-1-0-0</Data> <Data Name="TargetUserName"> </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">Schannel</Data> <Data Name="AuthenticationPackageName">Kerberos</Data> <Data Name="WorkstationName">SERVER</Data> <Data Name="TransmittedServices">-</Data> <Data Name="LmPackageName">-</Data> <Data Name="KeyLength">0</Data> <Data Name="ProcessId">0x208</Data> <Data Name="ProcessName">C:\Windows\System32\lsass.exe</Data> <Data Name="IpAddress">-</Data> <Data Name="IpPort">-</Data> </EventData> </Event>

Hi, Here is a hotfix, I would like suggest you try it: The Security event that has Event ID 4625 does not contain the user account name on a computer that is running Windows Vista, Windows Server 2008, Windows 7, or Windows Server 2008 R2 http://support.microsoft.com/default.aspx?scid=kb;en-us;2157973 In addition: 4625: An account failed to log on http://www.ultimatewindowssecurity.com/securitylog/encyclopedia/event.aspx?eventID=4625 Regards, Yan Li TechNet Subscriber Support If you are TechNet Subscription user and have any feedback on our support quality, please send your feedback here. Yan Li TechNet Community Support

Hi Yan, When trying to apply update - reported that it was not applicable to my computer. I used 64 bit version as it needs to be applied to 2008R2 server.

Hi, I would like to know that when you click Hotfix download availiable to down load the hotfix, the error is that it was not applicable? I would like to know what your OS version is? Regards, Yan Li TechNet Subscriber Support If you are TechNet Subscription user and have any feedback on our support quality, please send your feedback here. Yan Li TechNet Community Support

Hi, 2008R2 SP1. I made sure that I downloaded the 64 bit hotfix.

Hi, this event indicates there is some using bad password to log on to this computer from netwrok, we should find out who use the bad password to log on. So here i'd like to know if you encounter any issue like lockout. if not, please check if you have enabled lock out policy in default domain policy. http://technet.microsoft.com/en-us/library/cc787455(v=ws.10).aspx Best regards, Jason Mei Please remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

Hi, There is no account lockout policy enforced at the moment. Guy

So did you configure account lockout policy in your domain? If we want this event not to occure, we should find which computer send this request. Best regards, Jason Mei Please remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

If you take a look at the logs sumitted in my original post, it looks like a local system account which is causing the issue when being called by a lsass process.

I am having the exact same events on 2008 R2 SP1. EventID 4625 with no user information. My kerberos.dll version is 6.1.7601.17527 which that hotfix doesnt apply to. Is there another hotfix for R2 SP1?

Hi, the account causing the logon failure doesn't display. If the hotfix mentioned above doesn't work, (ensure we reboot the server after installing the hotfix) i think we may need more logs like netmon trace for the further research. Best regards, Jason Mei Please remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

How do we run netmon trace?

Hi, below is the information we should check to find which user cause the logon failure, but it is blank. The only thing we found for this issue is the hotfix below, if this hotfix doesn't work, i think this issue may cause by other reason. http://support.microsoft.com/default.aspx?scid=kb;en-us;2157973 Account For Which Logon Failed: Security ID: NULL SID Account Name: Account Domain: Best regards, Jason Mei Please remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

Hi, We have 64 bit 2008 R2 servers. Took care to download 64 bit hotfix. It says update is not applicable to computer :(

Hi, you may find it from following registry. HKEY_CURRENT_USER \ Software \ Microsoft \ Windows \ Shell \ Bags \ 1 \ Desktop. the key may be ItemposBest regards, Jason Mei Please remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

Hi, HKEY_CURRENT_USER \ Software \ Microsoft \ Windows \ Shell \ Bags \ 1 - there is no Desktop after that, only shell. What am I supposed to do with this registry key when we can locate it?

Hi, to run netmon trace, please perform following steps. 1.Download the network monitor from the link below and install it on machine where we got the event.1. http://www.microsoft.com/downloads/details.aspx?displaylang=en&FamilyID=983b941d-06cb-4658-b7f6-3088333d062f 2.Run the following command in command line.1."ipconfig/flushdns" to refresh the DNS cache. 2.nbtstat -RR" to clear the NetBIOS cache. 3.Click new capture button to create a new capture mission and click start on the network monitor panel. 4.steop the netmon trace untill 5.Wait about 1 minutes, save the capture and upload it to our workspace. Rergarding the hotfix, please try to download it from following link and test it again. Package: ----------------------------------------------------------- KB Article Number (s) : 2157973 Language: All (Global) Platform: x64 Location: ( http://hotfixv4.microsoft.com/Windows%207/WindowsServer%202008%20R2/sp1/Fix325425/7600/free/417999_intl_x64_zip.exe ) NOTE: Be sure to include all text between '(' and ')' when navigating to this hot fix location!Best regards, Jason Mei Please remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

Thanks for this: - hotfix still gives incompatible operating system error. - I have created a capture with network monitor. Where is the workspace to upload to? Guy

Hi, Here is some information for how to analyze netmon trace. http://blogs.technet.com/b/netmon/ If you want someone to analyze netmon trace, i'm afraid you may need to submite a call to MS. Best regards, Jason Mei Please remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

Hi, the hotfix has been included in SP1, so this is the reason the hotfix is incompatible with your OS.Best regards, Jason Mei Please remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

Hi, the hotfix has been included in SP1, so this is the reason the hotfix is incompatible with your OS.Best regards, Jason Mei Please remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.