Why is the client and server cannot communicate?
If you revert back to using TLS 1.0, communication functions as normal. InitializeSecurityContext error while client handshake: The client and server cannot communicate, because they do not possess a common algorithm (0x80090331)
Why is TLS not enabled on Symantec server?
Transport Layer Security (TLS) is not completely enabled on the Symantec Management Platform server. Allow agent and server to both use the same TLS algorithms. This is often caused by the agent profile only having TLS 1.0 checked and the agent operating system only allowing TLS 1.2.
Is there a mismatch in TLS version 1.1?
TLS version mismatch. After enabling TLS (Transport Layer Security) version 1.1 or 1.2, the clients in your environment become disconnected with the following error: InitializeSecurityContext error while client handshake: The client and server cannot communicate, because they do not possess a common algorithm (0x80090331).
Can a Configuration Manager client communicate with a CMG?
Configuration Manager clients can’t communicate together with the CMG. An error message that resembles one of the following is logged in the LocationServices.log file: Error messages that resemble the following are logged in the SMS_Cloud_ProxyConnector.log file:
TDSSNIClient initialization failed with error 0x80090331, status code 0x80. Reason: Unable to initialize SSL support. The client and server cannot communicate, because they do not possess a common algorithm The reason for this is that you may have disabled SSL 3.0 or TLS 1.0 on either the client side or SQL Server machine.
Why is MY SQL Server unable to communicate?
Reason: Unable to initialize SSL support. The client and server cannot communicate, because they do not possess a common algorithm The reason for this is that you may have disabled SSL 3.0 or TLS 1.0 on either the client side or SQL Server machine.
Why is my server using the same TLS as my agent?
Allow agent and server to both use the same TLS algorithms. This is often caused by the agent profile only having TLS 1.0 checked and the agent operating system only allowing TLS 1.2. Reference Microsoft article: https://technet.microsoft.com/en-us/library/dn786418.aspx