ADWS 错误日志1202
Log Name: Active Directory Web Services
Source: ADWS
Date: 2012/8/31 11:25:55
Event ID: 1202
Task Category: ADWS Instance Events
Level: Error
Keywords: Classic
User: N/A
Computer: RTDC01.rt.console.local
Description:
This computer is now hosting the specified directory instance, but Active Directory Web Services could not service it. Active Directory Web Services will retry this operation periodically.
Directory instance: NTDS
Directory instance LDAP port: 389
Directory instance SSL port: 636
Event Xml:
1202
2
3
0x80000000000000
1183
Active Directory Web Services
RTDC01.rt.console.local
NTDS
389
636
DFSR 错误日志1202
Log Name: DFS Replication
Source: DFSR
Date: 2012/8/31 11:24:52
Event ID: 1202
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: RTDC01.rt.console.local
Description:
The DFS Replication service failed to contact domain controller to access configuration information. Replication is stopped. The service will try again during the next configuration polling cycle, which will occur in 60 minutes. This event can be caused by TCP/IP connectivity, firewall, Active Directory Domain Services, or DNS issues.
Additional Information:
Error: 160 (One or more arguments are not correct.)
Event Xml:
1202
2
0
0x80000000000000
4163
DFS Replication
RTDC01.rt.console.local
60
160
One or more arguments are not correct.
DS日志2086
Log Name: Directory Service
Source: Microsoft-Windows-ActiveDirectory_DomainService
Date: 2012/8/31 11:22:48
Event ID: 2886
Task Category: LDAP Interface
Level: Warning
Keywords: Classic
User: ANONYMOUS LOGON
Computer: RTDC02.rt.console.local
Description:
The security of this directory server can be significantly enhanced by configuring the server to reject SASL (Negotiate, Kerberos, NTLM, or Digest) LDAP binds that do not request signing (integrity verification) and LDAP simple binds that are performed on a cleartext (non-SSL/TLS-encrypted) connection. Even if no clients are using such binds, configuring the server to reject them will improve the security of this server.
Some clients may currently be relying on unsigned SASL binds or LDAP simple binds over a non-SSL/TLS connection, and will stop working if this configuration change is made. To assist in identifying these clients, if such binds occur this directory server will log a summary event once every 24 hours indicating how many such binds occurred. You are encouraged to configure those clients to not use such binds. Once no such events are observed for an extended period, it is recommended that you configure the server to reject such binds.
For more details and information on how to make this configuration change to the server, please see http://go.microsoft.com/fwlink/?LinkID=87923.
You can enable additional logging to log an event each time a client makes such a bind, including information on which client made the bind. To do so, please raise the setting for the "LDAP Interface Events" event logging category to level 2 or higher.
Event Xml:
2886
0
3
16
0
0x8080000000000000
4100
Directory Service
RTDC02.rt.console.local