Audit failure event id 4625 - sbs2011 single server.

We have a single sbs2011 serverwhich was working OK, and I have just noticed that we are suddenly getting numerous errors in our security event log, as follows :-

An account failed to log on.

Subject:
      Security ID:            SYSTEM
      Account Name:            SBS2011$
      Account Domain:            HDS1
      Logon ID:            0x3e7

Logon Type:                  10

Account For Which Logon Failed:
      Security ID:            NULL SID
      Account Name:            root
      Account Domain:            SBS2011

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

Process Information:
      Caller Process ID:      0x10d0
      Caller Process Name:      C:\Windows\System32\winlogon.exe

Network Information:
      Workstation Name:      SBS2011
      Source Network Address:      46.105.2.112
      Source Port:            56920

Detailed Authentication Information:
      Logon Process:            User32
      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.

The thing that concerned me, was the apparent external IP address, and wondered if somone was trying to hack in??

Can anyone advise what might be causing this, and how to resolve it??

I have also attached a screenshot of the event log.

Any help would be much appreciated.
screenshot.bmp
nigelbeatsonAsked:
Who is Participating?
 
David AtkinConnect With a Mentor IT ProfessionalCommented:
It looks like someone has tried to log onto your server via RDP.

By default SBS doesn't have a Root account and the standard administrator account is disabled for security reasons.

The attempts are coming from:
46.105.2.112

Report that IP to your ISP. You could block the IP address on your firewall if its capable of doing it.

Another good idea is to either disable the RDP port rule on your firewall and just use RWW or change the RDP port to something on the router to something else and have a port redirection.  I.e. port 55555 > 3389.
0
 
nigelbeatsonAuthor Commented:
No further errors have subsequently appeared in our event log. Thanks to both for the information which helped me understand what is going on. Very helpful.
0
All Courses

From novice to tech pro — start learning today.