A fatal error has occurred check the hp connection manager in event viewer for more details10/13/2023 ![]() At least under Windows Server 2008 R2 SP1. Thomas wroteĭuring hardening our systems (RDP, Exchange, SQL, Server 2008R2/2012R2) with TLS 1.2, I noticed the following.Īfter only TLS 1.2 is allowed, the Windows Error Reporting Service no longer works and triggers an Event Id 36871 channel error in the event log / system log. ![]() pointed out an issue with TLS 1.2 to me at the end of July 2018. It occurred to me that blog reader Thomas B. Recently the transport encryption TLS 1.3 was officially approved by the IETF as RFC 8446.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |