View Connection Server Communication error. Horizon View 7.1.0.5170113 + Firmware 5.5.1

@jrod

What is the exact version of your Horizon View 7?

Zero clients connecting to Horizon versions 7.0.x (0, 1, 2 and 3) and 7.1 do not have this issue. And any 5.x and 4.8.x firmware version will work.

Only Horizon 6.2.4 requires firmware 5.5.1. I think that Horizon 6.2.4 is, chronologically, the latest Horizon released version (mid-April 2017).

Please provide more info. Upload PCoIP log files from the time issue occurred.

Slaven

Horizon View 7.1.0.5170113

Attached is the Dell 5030 zero client log.

zeroclientlog.txt

Snippet from the debug log on the View Connection Server:

[PooledProcessor] Problem processing HTTP connection: Received fatal alert: internal_error 2017-05-23T10:20:55.801-07:00 DEBUG (2510-2334) <pool-1-thread-1>

[PooledProcessor] Problem processing HTTP connection from /10.6.140.31:59291: javax.net.ssl.SSLException: Received fatal alert: internal_error 2017-05-23T10:20:55.907-07:00

[PooledProcessor] Problem processing HTTP connection: Received fatal alert: internal_error 2017-05-23T10:20:55.982-07:00

[PooledProcessor] Problem processing HTTP connection from /10.6.140.31:56936: javax.net.ssl.SSLException: Received fatal alert: internal_error

Keep in mind that the Horizon desktop client and even our older Wyse D90P's successfully connect.

There are no load balances in between the zero client and the View connection server.

What have I tried to resolve this issue?

• Generated a new certificate for the VCS (View Connection Server)
• Installed both CA cert and VCS certificates on the Zero client
• Disabled Secure Gateway for PCOIP
• Enabled TLS 1.0 on the VCS
• Rebuilt View Connection Server!
• Attempted to connect directly to VMware Access point with same result.
• Upgraded the Zero client from multiple versions of Firmware version 4 to 5.5.1
• Set Zero client to Max Compatibility for SSL
• Reset zero client to factory default
• Attempted to use a different Zero Client (Same model and Frimware version)
• Granted Everyone Full access to the Certificate on the View Connection server in case it's a permission issue with the Certificate
• Disabled the Firewall
• Created an ANY Any Rule for Windows Firewall
• Verified Compatible Ciphers are being utilized by Server as client by looking at Wireshark SSL conversation
• Ensured Cert is not a V3 certificate

Perhaps it's a bug in 5.5.1?

@Slaven

I installed a test Horizon View 6.2.4 instance and am confirming that Firmware 5.5.1 does connect to it from the same Zero client that CANNOT connect to Horizon View 7.1.0.5170113

Read the above line again please. I now firmly believe there is a bug that NEEDS TO BE FIXED BY TERADICI DEVELOPERS with Teradici Firmware 5.5.1 and Horizon View 7.1.0.5170113

Hi @jrod,

I am currentlying using a ZC with FW 5.5.1 and it is connecting to a VCS 7.1.0 build 5170113 so it does not appear to be a compatibility issue. The log line

"0d,00:29:24.75> LVL:1 RC:xFFFFE238 MGMT_SSL :tera_mgmt_ssl_open_connection: SSL_negotiateConnection() failed: Unknown Error"

Error code "FFFFE238" corresponds to "(ERR_CERT_INVALID_KEYUSAGE, -7624) // FFFFE238". Can you verify that the certificates used on your VCS is supported?

Thanks,

Jack.