This includes the Teradici 4.8 firmware which is certified to be supported by Horizon View 6.2. The longer term permanent solution would be to upgrade all your thin and zero clients to the latest version. Keep in mind that this should only be a temporary solution. SSL Certificate - Subject Common Name Does Not Match Server FQDN port 4172/tcp over SSL SSL Certificate - Signature Verification Failed Vulnerability port 4172/tcp over SSL Cause. Instructions on how to enable the above protocols can be found on KB2130798.

This fixed the problem for us and the fix will be in place until we can be sure that all clients are on the latest firmware version. If you’re running clients with a firmware version below 4.8 then you will most likely run in to this problem after upgrading to Horizon View 6.2.Īnother temporary work around is to explicitly enable TLS 1.0, 1.1 and 1.2 on your connection servers and your desktop pools (your ‘gold’ base image). The problem is that the more preferred ciphers are not supported on Teradici firmware versions below 4.8.

This issue hit a small portion of our Teradici/10ZiG zero clients. The problem occurs because some weaker encryption ciphers that were available in Horizon View 6.1 are now disabled in Horizon View 6.2 hence the session negotiation failed and/or incompatible cipher error messages. SSL session negotiation failed or The Zero Client may not be compatible with the host session negotiation cipher setting. If you’re upgrading from an earlier version of VMware Horizon View to version 6.2 then you may see clients fail to log-in with error messages that follow similar verbage:

Certificate error with teradici pcoip