Windows Forum

Ask something
Discussion Locked

Deafult server credential

0 helpful
4 replies

by lfross

Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

I have recently constructed a Win2k AD at my office, all seems to be running well except I keep getting a warning in my event log as follows

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.

Which leads to the following warning

LDAP over SSL will be unavailable at this time because the server was unable to obtain a certificate.

Is this something to be worried about or is this normal.

Any help here is greatly appreciated

4 replies

by joseph moore

Event ID 36872 on Windows 2000 Domain Controller (Q261196)

--------------------------------------------------------------------------------
The information in this article applies to:

Microsoft Windows 2000 , Server
Microsoft Windows 2000, Advanced Server
Microsoft Windows 2000 , Datacenter Server

--------------------------------------------------------------------------------

SYMPTOMS
On a Windows 2000 domain controller, the following event may be logged in the systemlog:

Event Type: Warning
Event Source: Schannel
Event Category: None
Event ID: 36872
Date: Date
Time: Time
User: N/A
Computer: computername
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.

by joseph moore

CAUSE
This event is logged when a server application (for example, Active Directory) attempts to perform a Secure Sockets Layer (SSL) connection, but no server certificate is found. Server certificates are either enrolled for by hand or are automatically generated by the domain's enterprise Certificate Authority (CA). In domains where no enterprise CA exists, this is an expected event and you can safely ignore the message.

This discussion is closed to new replies.