windows-server-2008 – 登录类型8(NetworkCleartext)的数千个46

我有一个 Windows Server 2008 R2系统,每天在Windows日志的安全部分中显示数千个4625登录失败错误和登录类型8(NetworkCleartext).尝试获取源网络地址中列出的访问权限的系统没有IP地址,因此我构建的用于阻止失败的IP的脚本无法找到它们.

这些登录尝试可以来自哪些服务？

以下是其中一个的示例：

An account failed to log on.

Subject:
    Security ID:        SYSTEM
    Account Name:       server-name$
    Account Domain:     example
    Logon ID:       0x3e7

Logon Type:         8

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

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

Process Information:
    Caller Process ID:  0x4d0
    Caller Process Name:    C:\Windows\System32\svchost.exe

Network Information:
    Workstation Name:   system-name
    Source Network Address: -
    Source Port:        -

Detailed Authentication Information:
    Logon Process:      Advapi  
    Authentication Package: MICROSOFT_AUTHENTICATION_PACKAGE_V1_0
    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.

> FTP登录 – 检查您的FTP日志以查看登录失败是否同时出现.这是我的案例中的来源,我花了很长时间才弄明白,这就是我发布这个的原因.
>通过http或https通过基本身份验证登录(简单,但可能是危险的,以密码保护网站的方式)
> ASP脚本
>可能还有其他一些我不知道的事情

Numbers 2 and 3 are mentioned at WindowsSecurity.com：

This logon type indicates a network logon like logon type 3 but where the password was sent over the network in the clear text. Windows server doesn’t allow connection to shared file or printers with clear text authentication. The only situation I’m aware of are logons from within an ASP script using the ADVAPI or when a user logs on to IIS using IIS’s basic authentication mode. In both cases the logon process in the event’s description will list advapi. Basic authentication is only dangerous if it isn’t wrapped inside an SSL session (i.e. https). As far as logons generated by an ASP,script remember that embedding passwords in source code is a bad practice for maintenance purposes as well as the risk that someone malicious will view the source code and thereby gain the password.

（编辑：ASP站长网）