RE: [ActiveDir] Using LDAPS

[Isenhour, Joseph]

Title: Using LDAPS

I did.  I used the MS tool to req and then import the cert into the local machine store.  I do this often and succeed most of the time.  Problem is when it does not work I have no idea how to troubleshoot it. From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of [EMAIL PROTECTED] Sent: Tuesday, March 22, 2005 2:19 PM To: ActiveDir@mail.activedir.org Subject: RE: [ActiveDir] Using LDAPS I’m going to guess that this is some kind of a certificate store configuration problem then as well.  Unfortunately, I’m not the guy here who configures this stuff, so I’m not sure what to look for here.   Did you follow the KB article on configuring the DC for a third party certificate?   Maybe someone else will see this and intervene as well.   Joe K.   From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Isenhour, Joseph Sent: Tuesday, March 22, 2005 1:34 PM To: ActiveDir@mail.activedir.org Subject: RE: [ActiveDir] Using LDAPS   The Error is only showing up on the server:   **************************************************************************************** Event Type: Warning Event Source: Schannel Event Category: None Event ID: 36872 Date:  3/22/2005 Time:  11:08:33 AM User:  N/A Computer: XXXXX Description: No suitable default server credential exists on this system. This will prevent server applications that expect to make use of the system default credentials from accepting SSL connections. An example of such an application is the directory server. Applications that manage their own credentials, such as the internet information server, are not affected by this.   For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp. ****************************************************************************************   I tried looking it up but the only explanation I found was that the error indicates that the server does not have a cert, but it clearly does.     This message is for the designated recipient only and may contain privileged, proprietary, or otherwise private information. If you have received it in error, please notify the sender immediately and delete the original. Any other use of the email by you is prohibited.