windows-server-2008-r2 – 没有源IP的事件ID 4625

前端之家收集整理的这篇文章主要介绍了windows-server-2008-r2 – 没有源IP的事件ID 4625前端之家小编觉得挺不错的,现在分享给大家,也给大家做个参考。
我们在开发和生产环境中共使用了7个 Windows Server(2008/2012)R2标准版.上个月我们的服务器遭到破坏,我们在Windows事件查看器中发现许多失败的尝试日志.我们尝试过cyberarms IDDS,但事先证明它并不好.

现在我们重新映像了所有服务器并重命名了Administrator / guest帐户.在再次设置服务器之后,我们使用this idds来检测和阻止不需要的IP地址.

IDDS工作正常,但我们仍然在事件查看器中获得4625个事件而没有任何源IP地址.如何阻止来自匿名IP地址的这些请求?

  1. <Event xmlns='http://schemas.microsoft.com/win/2004/08/events/event'>
  2. <System>
  3. <Provider Name='Microsoft-Windows-Security-Auditing' Guid='{54849625-5478-4994-A5BA-3E3B0328C30D}'/>
  4. <EventID>4625</EventID>
  5. <Version>0</Version>
  6. <Level>0</Level>
  7. <Task>12544</Task>
  8. <Opcode>0</Opcode>
  9. <Keywords>0x8010000000000000</Keywords>
  10. <TimeCreated SystemTime='2015-04-18T15:18:10.818780700Z'/>
  11. <EventRecordID>187035</EventRecordID>
  12. <Correlation/>
  13. <Execution ProcessID='24876' ThreadID='133888'/>
  14. <Channel>Security</Channel>
  15. <Computer>s17751123</Computer>
  16. <Security/>
  17. </System>
  18. <EventData>
  19. <Data Name='SubjectUserSid'>S-1-0-0</Data>
  20. <Data Name='SubjectUserName'>-</Data>
  21. <Data Name='SubjectDomainName'>-</Data>
  22. <Data Name='SubjectlogonId'>0x0</Data>
  23. <Data Name='TargetUserSid'>S-1-0-0</Data>
  24. <Data Name='TargetUserName'>aaron</Data>
  25. <Data Name='TargetDomainName'>\aaron</Data>
  26. <Data Name='Status'>0xc000006d</Data>
  27. <Data Name='FailureReason'>%%2313</Data>
  28. <Data Name='SubStatus'>0xc0000064</Data>
  29. <Data Name='logonType'>3</Data>
  30. <Data Name='logonProcessName'>NtLmSsp </Data>
  31. <Data Name='AuthenticationPackageName'>NTLM</Data>
  32. <Data Name='WorkstationName'>SSAWSTS01</Data>
  33. <Data Name='TransmittedServices'>-</Data>
  34. <Data Name='LmPackageName'>-</Data>
  35. <Data Name='KeyLength'>0</Data>
  36. <Data Name='ProcessId'>0x0</Data>
  37. <Data Name='ProcessName'>-</Data>
  38. <Data Name='IpAddress'>-</Data>
  39. <Data Name='IpPort'>-</Data>
  40. </EventData>
  41. </Event>

更新:
检查我的防火墙日志后,我认为这些4625事件无论如何都与Rdp无关,但可能是SSH或任何其他我不熟悉的尝试

即使启用了NLA,也会在此处记录失败的RDP尝试的IP地址(无需调整)(在Server 2012 R2上测试,不确定其他版本)

应用程序和服务日志>
微软Windows的RemoteDesktopServices-RdpCoreTS /运营
(事件ID 140)

记录的文本示例:

A connection from the client computer with an IP address of
108.166.xxx.xxx Failed because the user name or password is not correct.

XML:

  1. - <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  2. - <System>
  3. <Provider Name="Microsoft-Windows-RemoteDesktopServices-RdpCoreTS" Guid="{1139C61B-B549-4251-8ED3-27250A1EDEC8}" />
  4. <EventID>140</EventID>
  5. <Version>0</Version>
  6. <Level>3</Level>
  7. <Task>4</Task>
  8. <Opcode>14</Opcode>
  9. <Keywords>0x4000000000000000</Keywords>
  10. <TimeCreated SystemTime="2016-11-13T11:52:25.314996400Z" />
  11. <EventRecordID>1683867</EventRecordID>
  12. <Correlation ActivityID="{F4204608-FB58-4924-A3D9-B8A1B0870000}" />
  13. <Execution ProcessID="2920" ThreadID="4104" />
  14. <Channel>Microsoft-Windows-RemoteDesktopServices-RdpCoreTS/Operational</Channel>
  15. <Computer>SERVER</Computer>
  16. <Security UserID="S-1-5-20" />
  17. </System>
  18. - <EventData>
  19. <Data Name="IPString">108.166.xxx.xxx</Data>
  20. </EventData>
  21. </Event>

猜你在找的Windows相关文章