Guest User!

You are not Sophos Staff.

This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Audit Failure Sophos Account

I am not sure what this is for, looking for some help on it, basically showing up in event viewer on the DC

 

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: SOPHOS$
Account Domain: DFLLC

Failure Information:
Failure Reason: Unknown user name or bad password.
Status: 0xC000006D
Sub Status: 0xC000006A

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

Network Information:
Workstation Name: SOPHOS
Source Network Address: 192.168.1.1
Source Port: 45606

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.



This thread was automatically locked due to age.
Parents
  • Hello grifter,

    Sophos Account
    not sure how this is related to Sophos, as far as I can see it's a failed logon from a computer named SOPHOS and the account is the machine account SOPHOS$.
    Are you indeed using Sophos Central?

    Christian

  • Yes we have Sophos Central and Firewall, I was not here when it was initially setup and no one who was works here anymore, so I am not sure if the Sophos computer listed in AD is there for a reason or just something left over from a previous use.  Really other than the mention of it in AD Users and Computers I cannot find any record of the Sophos computer, no ping, no lookup, nothing.  I was thinking maybe this is the firewall as well but again I am just not sure.

  • Hello grifter

    Windows security claims it's called SOPHOS, the address (192.168.1.1) suggests a gateway device (that might not respond to a ping).

    Christian

  • That address is the FW, but I am not sure if it is showing that IP because that is the device or because another device is using that one to connect?  Maybe it is the FW registered as a computer but why it would try to reach our to AD is where I would get confused.

Reply
  • That address is the FW, but I am not sure if it is showing that IP because that is the device or because another device is using that one to connect?  Maybe it is the FW registered as a computer but why it would try to reach our to AD is where I would get confused.

Children
No Data