Christopher Hand
asked on
Security Event Log - 4625
Hello - I have been trying to troubleshoot this issue for days now and I am coming up empty. Some service or task is trying to, as I understand, access EHP1SRV01 (DC), with my credentials of 'chand'. I think maybe why it is failing is because it doesn't have my latest password updated or it needs the domain 'EHP1\chand'. Not sure. Any help is appreciated. Below is the error message I keep receiving. About 1000+ every 2 minutes.
An account failed to log on.
Subject:
Security ID: SYSTEM
Account Name: EHP1SRV01$
Account Domain: EHP1
Logon ID: 0x3e7
Logon Type: 3
Account For Which Logon Failed:
Security ID: NULL SID
Account Name: chand
Account Domain: EHP1
Failure Information:
Failure Reason: Unknown user name or bad password.
Status: 0xc000006d
Sub Status: 0xc000006a
Process Information:
Caller Process ID: 0x344
Caller Process Name: C:\Windows\System32\lsass. exe
Network Information:
Workstation Name: EHP1SRV01
Source Network Address: 10.50.201.1
Source Port: 55267
Detailed Authentication Information:
Logon Process: Advapi
Authentication Package: MICROSOFT_AUTHENTICATION_P ACKAGE_V1_ 0
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.
An account failed to log on.
Subject:
Security ID: SYSTEM
Account Name: EHP1SRV01$
Account Domain: EHP1
Logon ID: 0x3e7
Logon Type: 3
Account For Which Logon Failed:
Security ID: NULL SID
Account Name: chand
Account Domain: EHP1
Failure Information:
Failure Reason: Unknown user name or bad password.
Status: 0xc000006d
Sub Status: 0xc000006a
Process Information:
Caller Process ID: 0x344
Caller Process Name: C:\Windows\System32\lsass.
Network Information:
Workstation Name: EHP1SRV01
Source Network Address: 10.50.201.1
Source Port: 55267
Detailed Authentication Information:
Logon Process: Advapi
Authentication Package: MICROSOFT_AUTHENTICATION_P
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.
ASKER
Chris - I checked services.msc and none of the services use my domain account. Yes, I changed my password quite a few months back. I believe the errors started then. However, I'm not sure how to pin point what task or service is trying to use my account. So frustrating.
ASKER
Here is the other error which may be helpful:
The computer attempted to validate the credentials for an account.
Authentication Package: MICROSOFT_AUTHENTICATION_P ACKAGE_V1_ 0
Logon Account: chand
Source Workstation: EHP1SRV01
Error Code: 0xc000006a
The computer attempted to validate the credentials for an account.
Authentication Package: MICROSOFT_AUTHENTICATION_P
Logon Account: chand
Source Workstation: EHP1SRV01
Error Code: 0xc000006a
ASKER
I followed these directions and attached the netlogon.log file
Solution: We had to put the domain controller in verbose logging for the netlogon service to actually find out where the logon attempt was coming from.
First, open up command prompt as an administrator and execute the following command:
nltest /dbflag:0x2080ffff
Once done, execute the following command to turn off the debugging:
nltest /dbflag:0x0
This logs every transaction made to the file: %windir%\debug\netlogon.lo g (note, you need to run notepad as an administrator to read this file).
Solution: We had to put the domain controller in verbose logging for the netlogon service to actually find out where the logon attempt was coming from.
First, open up command prompt as an administrator and execute the following command:
nltest /dbflag:0x2080ffff
Once done, execute the following command to turn off the debugging:
nltest /dbflag:0x0
This logs every transaction made to the file: %windir%\debug\netlogon.lo
ASKER
Here is the file.
netlogon.log
netlogon.log
Hi Chris,
Unfortunately, the log just seems to point to the DC.
Are you syncing your phone or mobile device to your account?
In my experience, these 99.9% of these types of events are typically caused 1 of 2 ways.
1> a service account of some type is running using your username/password, but your credentials changed/expired.
2> a mobile device is attempting to authenticate, but your credentials changed/expired.
Unfortunately, the log just seems to point to the DC.
Are you syncing your phone or mobile device to your account?
In my experience, these 99.9% of these types of events are typically caused 1 of 2 ways.
1> a service account of some type is running using your username/password, but your credentials changed/expired.
2> a mobile device is attempting to authenticate, but your credentials changed/expired.
ASKER
Thanks for getting back to me, Chris.
I am not syncing any type of mobile device to my account. It is probably a service using my old credentials, I just have to find which one it is.
I did change my domain password which then it locked me out of my account after next login. I am no longer getting that first error message but the second one I posted above, I am still receiving.
At this point I just have to browse and think of what is trying to access my account. Could it be a service on my local machine even if the error points to the DC?
I am not syncing any type of mobile device to my account. It is probably a service using my old credentials, I just have to find which one it is.
I did change my domain password which then it locked me out of my account after next login. I am no longer getting that first error message but the second one I posted above, I am still receiving.
At this point I just have to browse and think of what is trying to access my account. Could it be a service on my local machine even if the error points to the DC?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Oh brother. That is going to take forever. I would have to go to each and every machine on the network and check each scheduled task. Is that the most feasible option right now? Isn't there a program that can do it for me?
ASKER
I finally figured it out. I noticed the source network address of the error was coming from our firewall appliance. Apparently I used my personal credentials to configure LDAP. I updated the credentials and the errors in Event Viewer disappeared and now my account no longer is being locked every 10 seconds.
Thanks for your assistance and for pointing me in the right direction, Chris.
Thanks for your assistance and for pointing me in the right direction, Chris.
Sure man! Great to hear you figured it out. Happy to help! :-)
Have you changed your password recently?