Brute Force Attack?
Hello,
The event log keeps getting filled up with login failures for random accounts @WSERemoteApp (see error below) and the server becomes so slow it is unusable. Anything you can suggest to help us block these logon requests:
An account failed to log on.
Subject:
Security ID: IIS APPPOOL\RDWebAccess
Account Name: RDWebAccess
Account Domain: IIS APPPOOL
Logon ID: 0x458C9
Logon Type: 3
Account For Which Logon Failed:
Security ID: NULL SID
Account Name: exfk@WSERemoteApp
Account Domain:
Failure Information:
Failure Reason: Unknown user name or bad password.
Status: 0xC000006D
Sub Status: 0xC0000064
Process Information:
Caller Process ID: 0xf10
Caller Process Name: C:\Windows\System32\inetsrv\w3wp.exe
Network Information:
Workstation Name: XXXXXX
Source Network Address: –
Source Port: –
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.
- bramweja asked 2 months ago
- You must log in to post comments.
I’m not a network security guy, and so there’s not much I can offer you on this one I’m afraid. Best I can tell, from your log and from what you’ve said, is that someone is attempting to sign in to your Windows Server Essentials server’s built-in Remote Web Access (RWA) website over and over again using a set of user names that do not exist (as WSE RemoteApp doesn’t ever create any user accounts on your server). I’m not exactly sure there’s much you can do to stop that from happening though (other than researching ways to prevent brute force attacks or possibly just using a new/different domain name for your server). I’ve personally never come across a case where nonexistent @WSERemoteApp users were randomly attacking RWA before (and it seems a bit odd to me unless it’s being done intentionally) Hopefully someone else will chime in with a suggestion for you.
- Mike answered 2 months ago
- last edited 2 months ago
- You must log in to post comments.