Brute force attacks and anonymous logon
-
Wednesday, January 16, 2013 9:40 AM
Hello
I have noticed that before the brute force attacks there is always a successful anonymous logon event from the same IP of the brute force attack, for example the successful anonymous logon
An account was successfully logged on. Subject: Security ID: NULL SID Account Name: - Account Domain: - Logon ID: 0x0 Logon Type: 3 New Logon: Security ID: ANONYMOUS LOGON Account Name: ANONYMOUS LOGON Account Domain: NT AUTHORITY Logon ID: 0x2c9dfa67 Logon GUID: {00000000-0000-0000-0000-000000000000} Process Information: Process ID: 0x0 Process Name: - Network Information: Workstation Name: SUMMIT01 Source Network Address: 66.147.235.240 Source Port: 16935 Detailed Authentication Information: Logon Process: NtLmSsp Authentication Package: NTLM Transited Services: - Package Name (NTLM only): NTLM V1and after it the brute force attack
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 Account Domain: FXNB 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: FXNB Source Network Address: 66.147.235.240 Source Port: 16964 Detailed Authentication Information: Logon Process: NtLmSsp Authentication Package: NTLM Transited Services: - Package Name (NTLM only): - Key Length: 0
My questions are:
- What is this anonymous logon?
- Which information obtains the attacker from it?
- Can this anonymous login blocked or disabled?
Thanks
All Replies
-
Thursday, January 17, 2013 2:46 AMModerator
Hi,
Thanks for posting in Microsoft TechNet forums.
Please check this to see if it is useful:
Restricting Anonymous Access
http://technet.microsoft.com/en-us/library/cc785670(v=ws.10).aspx
Regards
Kevin- Marked As Answer by K_evin ZhuMicrosoft Contingent Staff, Moderator Wednesday, February 06, 2013 1:38 AM
-
Friday, January 18, 2013 9:00 AM
Thank for the reply, I had already read the article and enabled the "Do not allow anonymous enumeration of SAM accounts and shares" policy but the "ANONYMOUS LOGON" are still there. The server is a VM for a Web Application, it isn't in a network, it doesn't require LDAP or NTLM, we use RD to connect with it.
Here the settings of the local security policy, can I change something to block them?

- Edited by Casual Trash Friday, January 18, 2013 9:01 AM

