We are experiencing the following schannel errors most frequently on our Remote Desktop Terminal Servers.

Log Name:      System
Source:        Schannel
Date:          11/18/2015 1:04:56 PM
Event ID:      36888
Task Category: None
Level:         Error
User:          SYSTEM
Computer:      RD2.{removed}.com
The following fatal alert was generated: 10. The internal error state is 10.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
    <Provider Name="Schannel" Guid="{1F678132-5938-4686-9FDC-C8FF68F15C85}" />
    <TimeCreated SystemTime="2015-11-18T18:04:56.498068400Z" />
    <Correlation />
    <Execution ProcessID="572" ThreadID="48732" />
    <Security UserID="S-1-5-18" />
    <Data Name="AlertDesc">10</Data>
    <Data Name="ErrorState">10</Data>

Occasionally we will get this on our Exchange server or an IIS server, however it is mostly from our Remote Desktop Terminal Servers that are running 2008 R2 64bit. As you can see by the following graph that we get spikes such as this semi frequently. This graph is of 1 terminal server for the past 12 hours which gave us 407 errors. schannel error graph

Any suggestions on how to find out what is causing these issues? Should we just disable schannel debugging?

2 Answers 2


I wouldn't disable logging those, but I would not be concerned about them. I believe this page should give more information: https://msdn.microsoft.com/en-us/library/windows/desktop/dd721886%28v=vs.85%29.aspx.

Apparently this is connected to SSLv3, so maybe it's related to older clients connecting, or network issues between the clients and the RDP server.

You could try to investigate who actually logs on during those times and attempt to correlate the schannel error with a successful or failed logon.


These errors are exactly correlated with reset TCP connections when someone is attempting to connect and logon through port 3389 ms-wbt-server. If the person fails the system security "black box", then the incoming connection is aborted with a reset packet. The error message you are seeing is then thrown up to the Windows Systems Log. If you are experiencing a lot of these still, then you might want to change the listening port from 3389 to something else, and see if the errors diminish.

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .