Forum Discussion

IT null's avatar
IT null
Copper Contributor
Oct 08, 2018

Exchange 2016 Incoming & Outgoing Messages Delay

Dears, I have a big Delay in Incoming and Outgoing Messages in Exchange 2016. Sometimes the messages are delivered whiten seconds and sometimes take more than one Hour which makes me crazy. So i s...
2016
Exchange Server
IT null's avatar
IT null
Copper Contributor
Oct 12, 2018

My Dear,

There are some error Logs i saw in Event Viewer if you can tell me what are the reasons behind them these Logs Are as below:

1- Event ID:36888 "A fatal alert was generated and sent to the remote endpoint. This may result in termination of the connection. The TLS protocol defined fatal error code is 10. The Windows SChannel error state is 1203."

2-Event ID:36874 "An TLS 1.2 connection request was received from a remote client application, but none of the cipher suites supported by the client application are supported by the server. The SSL connection request has failed."

Please if you have any clarification about these two errors tell me.

 

 

Adam Ochs's avatar
Adam Ochs
Iron Contributor
Oct 12, 2018

Hello Again,

 

Thanks for the additional details.

 

"An TLS 1.2 connection request was received from a remote client application, but none of the cipher suites supported by the client application are supported by the server" really holds the key to me.

 

The applications/device you are using to send to your exchange server (be it outlook/a printer/whatever), is trying to use TLS 1.2. It is failing on the server, as the server is having issues translating/understanding the secure cipher that is being used by TLS 1.2.

 

I would guess this comes down to one of maybe a few things:

1. Your SSL cert on the server may be out of date or wrong.

2. You dont have TLS 1.2 enabled on the server:

If you need to check if its on - https://docs.microsoft.com/en-us/previous-versions/windows/it-pro/windows-server-2012-R2-and-2012/dn786418(v=ws.11)#BKMK_SchannelTR_TLS12

If you need to turn it on - https://blogs.technet.microsoft.com/exchange/2018/04/02/exchange-server-tls-guidance-part-2-enabling-tls-1-2-and-identifying-clients-not-using-it/

 

I would start looking there, as the error clearly is telling you it is failing because the server is failing to read the TLS 1.2

 

Goodluck

Adam

  • IT null's avatar
    IT null
    Copper Contributor
    Oct 12, 2018

    Dear Mr Adam,

    I appreciate your Support, just i need to ask if the delay is made by this error or something else?

    I mean is TLS issue made the delay or not ? 

Resources