Account is getting locked & getting failed authentication event in the logs repeatedly
On the server the mentioned "username" account is local admin as well as an exchange user.
Exchange account is configured on iphone accessible using 3G network & on outlook on the internal ip 192.168.0.16
In the event if you notice the authentication failure is coming thru ip 192.168.2.1
this is router IP interface on another VLAN....request from 2.x is not expected.
routing on VLAN is disabled. All the VLAN are configured as isolated.
-----------
An account failed to log on.
Subject:
Security ID: SYSTEM
Account Name: server$
Account Domain: domain
Logon ID: 0x3e7
Logon Type: 8
Account For Which Logon Failed:
Security ID: NULL SID
Account Name: username
Account Domain: domain
Failure Information:
Failure Reason: Unknown user name or bad password.
Status: 0xc000006d
Sub Status: 0xc000006a
Process Information:
Caller Process ID: 0x3d3c
Caller Process Name: C:\Windows\System32\inetsr
--------------------------
Kerberos pre-authentication failed.
Account Information:
Security ID: domain\username
Account Name: username
Service Information:
Service Name: krbtgt/domain
Network Information:
Client Address: ::1
Client Port: 0
Additional Information:
Ticket Options: 0x40810010
Failure Code: 0x18
Pre-Authentication Type: 2
Certificate Information:
Certificate Issuer Name:
Certificate Serial Number:
Certificate Thumbprint:
Certificate information is only provided if a certificate was used for pre-authentication.
Pre-authentication types, ticket options and failure codes are defined in RFC 4120.
If the ticket was malformed or damaged during transit and could not be decrypted, then many fields in this event might not be present.
---------------
Kerberos pre-authentication failed.
Account Information:
Security ID: domain\username
Account Name: username
Service Information:
Service Name: krbtgt/domain
Network Information:
Client Address: ::ffff:192.168.0.16
Client Port: 55627
Additional Information:
Ticket Options: 0x40810010
Failure Code: 0x18
Pre-Authentication Type: 2
Certificate Information:
Certificate Issuer Name:
Certificate Serial Number:
Certificate Thumbprint:
Certificate information is only provided if a certificate was used for pre-authentication.
Pre-authentication types, ticket options and failure codes are defined in RFC 4120.
If the ticket was malformed or damaged during transit and could not be decrypted, then many fields in this event might not be present.
------------
Logon Type: 8
Account For Which Logon Failed:
Security ID: NULL SID
Account Name: username
Account Domain: domain
Failure Information:
Failure Reason: Unknown user name or bad password.
Status: 0xc000006d
Sub Status: 0xc000006a
Process Information:
Caller Process ID: 0x3d3c
Caller Process Name: C:\Windows\System32\inetsr
Network Information:
Workstation Name: IBMDC
Source Network Address: 192.168.2.1
Source Port: 55622
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.
Exchange account is configured on iphone accessible using 3G network & on outlook on the internal ip 192.168.0.16
In the event if you notice the authentication failure is coming thru ip 192.168.2.1
this is router IP interface on another VLAN....request from 2.x is not expected.
routing on VLAN is disabled. All the VLAN are configured as isolated.
-----------
An account failed to log on.
Subject:
Security ID: SYSTEM
Account Name: server$
Account Domain: domain
Logon ID: 0x3e7
Logon Type: 8
Account For Which Logon Failed:
Security ID: NULL SID
Account Name: username
Account Domain: domain
Failure Information:
Failure Reason: Unknown user name or bad password.
Status: 0xc000006d
Sub Status: 0xc000006a
Process Information:
Caller Process ID: 0x3d3c
Caller Process Name: C:\Windows\System32\inetsr
--------------------------
Kerberos pre-authentication failed.
Account Information:
Security ID: domain\username
Account Name: username
Service Information:
Service Name: krbtgt/domain
Network Information:
Client Address: ::1
Client Port: 0
Additional Information:
Ticket Options: 0x40810010
Failure Code: 0x18
Pre-Authentication Type: 2
Certificate Information:
Certificate Issuer Name:
Certificate Serial Number:
Certificate Thumbprint:
Certificate information is only provided if a certificate was used for pre-authentication.
Pre-authentication types, ticket options and failure codes are defined in RFC 4120.
If the ticket was malformed or damaged during transit and could not be decrypted, then many fields in this event might not be present.
---------------
Kerberos pre-authentication failed.
Account Information:
Security ID: domain\username
Account Name: username
Service Information:
Service Name: krbtgt/domain
Network Information:
Client Address: ::ffff:192.168.0.16
Client Port: 55627
Additional Information:
Ticket Options: 0x40810010
Failure Code: 0x18
Pre-Authentication Type: 2
Certificate Information:
Certificate Issuer Name:
Certificate Serial Number:
Certificate Thumbprint:
Certificate information is only provided if a certificate was used for pre-authentication.
Pre-authentication types, ticket options and failure codes are defined in RFC 4120.
If the ticket was malformed or damaged during transit and could not be decrypted, then many fields in this event might not be present.
------------
Logon Type: 8
Account For Which Logon Failed:
Security ID: NULL SID
Account Name: username
Account Domain: domain
Failure Information:
Failure Reason: Unknown user name or bad password.
Status: 0xc000006d
Sub Status: 0xc000006a
Process Information:
Caller Process ID: 0x3d3c
Caller Process Name: C:\Windows\System32\inetsr
Network Information:
Workstation Name: IBMDC
Source Network Address: 192.168.2.1
Source Port: 55622
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.
ASKER CERTIFIED SOLUTION
membership
Create a free account to see this answer
Signing up is free and takes 30 seconds. No credit card required.
ASKER
I removed one entry from credential manager that was having obsolete password.
Secondly I change authentication type to NTLM negotiation in exchange email settings that connect through https (over the web protocol)
I am not getting account lockout notifications now.
Secondly I change authentication type to NTLM negotiation in exchange email settings that connect through https (over the web protocol)
I am not getting account lockout notifications now.
You can user the below account lockout tool which can give you detail information like when the account was locked out, the source and the attempts made as well.
http://www.netwrix.com/account_lockout_examiner.html