Quantcast
Channel: Directory Services forum
Viewing all articles
Browse latest Browse all 31638

ActiveDirectory_DomainService

$
0
0

Hi

I recently installed two new 2008R2 DC's, removed all 2003 DC's.  The main DC is on a physical server that holds the FSMO roles.  The other is a Hyper-V VM.  I am seeing two warnings under the event logs.  One once a day, the other a few times a day.  The first one I have tried and followed the below document which Microsoft gives you under the event warning, but it has not stopped these from appearing.  The other one that appears a few times a day is below.

Event ID - 2887, ActiveDirectory_DomainService

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

This directory server is not currently configured to reject such binds.  The security of this directory server can be significantly enhanced by configuring 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.

Summary information on the number of these binds received within the past 24 hours is below.

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.

Number of simple binds performed without SSL/TLS: 0

Number of Negotiate/Kerberos/NTLM/Digest binds performed without signing: 12

Event ID - 29, Kerberos-Key-Distribution-Center

The Key Distribution Center (KDC) cannot find a suitable certificate to use for smart card logons, or the KDC certificate could not be verified. Smart card logon may not function correctly if this problem is not resolved. To correct this problem, either verify the existing KDC certificate using certutil.exe or enroll for a new KDC certificate.


Viewing all articles
Browse latest Browse all 31638

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>