Link to home
Start Free TrialLog in
Avatar of SpiderPig
SpiderPigFlag for United States of America

asked on

Event ID: 2887

Keep getting this on a Windows 2008 R2 AD. Anyone did the changes in domain and have feedback for me? My concern is Windows XP clients that are still on the network. I dont want to change anything that will effect clients (Win 7 and XP) in any way.

Thanks.

Service Details:
Event Log Module Status: 0
The Last Record Number of the eventlog type that current event entry belongs to: 0
# of duplicate events: 1
Source: NTDS LDAP
Category: LDAP Interface
Event ID: 2887
User (If Applicable): NT AUTHORITY\ANONYMOUS LOGON
Computer: srv01.domain.com
Event Description: During the previous 24 hour period, some clients attempted to perform LDAP binds that were either:

(1) A SASL (Negotiate, Kerberos, NTLM, or Digest) LDAP bind that did not request signing (integrity validation), or

(2) A LDAP simple bind that was performed on a cleartext (non-SSL/TLS-encrypted) connection
ASKER CERTIFIED SOLUTION
Avatar of UndefinedException
UndefinedException

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of SpiderPig

ASKER

60% Win XP 40% Win 7. I have one old Windows 2000 server that is being used for the telephone system. It is on the same class B network, but should not communicate with AD in any way. Its a proprietary ProTel software.

How can I find out the device causing this?

If Ill make the changes in your article will I have to update anything on Win XP and 7 PCs? Will the transition be transparent to the user?