Schannel. Event ID 36886, 36887.

Answered Schannel. Event ID 36886, 36887.

  • Donnerstag, 17. Januar 2013 14:50
     
     

    Hi!
    After installing ADCS I've got warnings on both domain controllers (Win 2008 R2):

    Event ID :- 36886
    Source :-   Schannel
    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.

    I've noticed that controllers have not received a certificate from CA. When I requested certificate manually, I've got the following error:

    Event ID :- 36887
    Source :-   Schannel
    The following fatal alert was received: 46.

    When I removed the requested certificate, the error (id36887) was replaced by warning (id36886).  Does someone have the same issue?

Alle Antworten

  • Freitag, 18. Januar 2013 08:42
    Moderator
     
     Beantwortet

    Hi,

    Event 36886 is a warning that is logged when a server attempt to make an SSL connection but no server certificate is found. 

    Refer to below discussion for more information about Error 36887 and possible troubleshooting methods:
    Schannel errors on three of my DC's; Event ID 36887, Alert 46
    http://social.technet.microsoft.com/Forums/en-US/winserverManagement/thread/7f478de6-ccf4-4792-a04a-772b9aa7efd0

    Hope it helps.

    Regards,
    Cicely

    • Als Antwort markiert KrotovDA Montag, 21. Januar 2013 06:49
    •  
  • Montag, 21. Januar 2013 02:08
    Moderator
     
     

    Hi,

    Hi,

    I would like to confirm what is the current situation? If there is anything that I can do for you, please do not hesitate to let me know, and I will be happy to help.

    Regards,

    Cicely Feng

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

    TechNet Subscriber Support

    If you are TechNet Subscription  user and have any feedback on our support quality, please send your feedback here .

  • Montag, 21. Januar 2013 06:49
     
     

    I scanned network traffic, defined the computer causing an error and solved this issue. Thanks.