If you check your event logs following this, you'll see a fatal alert 10 with internal error state of 1203. (note the use of http on port 443, NOT https) You can generate a similar error by attempting to access your Outlook Web Access site in the following (invalid) manner.
Update: Many times these are externally caused. If you'd like to suppress the SChannel alerts, you can tweak the registry setting detailed in KB260729. This sounds truly problematic until you realize that it's likely that the machine attempting to establish the TLS connection likely tries again in a more agreeable fashion. In this case, other connections corresponding to the session may continue, but the session identifier MUST be invalidated, preventing the failed session from being used to establish new connections. Alert messages with a level of fatal result in the immediate termination of the connection. According to the TLS Protocol RFC, this indicates an unexpected message. Help, please!ĭo you receive these errors often (on a schedule?) and are you aware of any actual problems that coincide with their appearance? I ask because it's likely that you can safely ignore them or suppress them.
I can't find much related to that specific error. The following fatal alert was received: 10. Here are the details of the error: Log Name: System I get this error (event 36887 schannel The following fatal alert was received: 10.) on my Exchange Server 2010, running on Windows Server 2008 圆4 Enterprise.
0 kommentar(er)
