Quantcast
Channel: Small Business Server forum
Viewing all articles
Browse latest Browse all 8539

Strange SAM database lockout error

$
0
0

Hi everybody,

This is a bit of an odd one. I am getting the SAM database lockout message regularly in the System event log, but it says 'unable to lockout the account of invalid'...

According to the event log, one request is coming from a workstation, the other is coming from the server itself, and both are using the name of the server admin account before I renamed it. See events below. I have run Wireshark on the workstation and could not see any sign of a login attempt. I have looked in the credential store on W/S and Server and can see no mention of this account, ditto Services Logon As. 

If anyone is able to make some suggestions as to what to look for next, I would be most grateful.

WORKSTATION:

An account failed to log on.

Subject:
Security ID: NULL SID
Account Name: -
Account Domain:-
Logon ID: 0x0

Logon Type:3

Account For Which Logon Failed:
Security ID: NULL SID
Account Name: administrator.001
Account Domain:VIOLETA-HP

Failure Information:
Failure Reason:Unknown user name or bad password.
Status: 0xc000006d
Sub Status: 0xc0000064

Process Information:
Caller Process ID:0x0
Caller Process Name:-

Network Information:
Workstation Name:VIOLETA-HP
Source Network Address:192.168.31.46
Source Port: 52715

Detailed Authentication Information:
Logon Process:NtLmSsp 
Authentication Package:NTLM
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.

SERVER

An account failed to log on.

Subject:
Security ID: NULL SID
Account Name: -
Account Domain:-
Logon ID: 0x0

Logon Type:3

Account For Which Logon Failed:
Security ID: NULL SID
Account Name: administrator.001
Account Domain:SKANSEN.local

Failure Information:
Failure Reason:Unknown user name or bad password.
Status: 0xc000006d
Sub Status: 0xc0000064

Process Information:
Caller Process ID:0x0
Caller Process Name:-

Network Information:
Workstation Name:HOLLY
Source Network Address:-
Source Port: -

Detailed Authentication Information:
Logon Process:NtLmSsp 
Authentication Package:NTLM
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.


Viewing all articles
Browse latest Browse all 8539

Trending Articles