What firmware are you running on the clients? If its really old this could be a possible explanation.
Latest is 4.5.
They are on latest 4.5.1.
Did you disable any ciphers or change any encryption settings?
What does the log say?
no I havent disabled/changed ciphers/encryption settings
2014-10-13T13:51:38Z> LVL:2 RC: 0 MGMT_VDM :INIT.INIT: Transition 1 into INIT.SECURITY_CHECK_INTERACTIVE
2014-10-13T13:51:38Z> LVL:1 RC:xFFFFE244 MGMT_SSL :tera_mgmt_ssl_open_connection: SSL_negotiateConnection() failed: Unknown Error
2014-10-13T13:51:38Z> LVL:1 RC:-500 MGMT_VDMCSI :tera_mgmt_ssl_open_connection failed (ssl_session_id: 0) 2014-10-13T13:51:38Z> LVL:1 RC:-501 MGMT_VDMCSI :tera_mgmt_ssl_close_connection failed (ssl_session_id: 0) 2014-10-13T13:51:38Z> LVL:2 RC: 0 MGMT_VDM :View Connection Server communication error. 2014-10-13T13:51:38Z> LVL:2 RC: 0 MGMT_VDM :INIT.SECURITY_CHECK_INTERACTIVE: Transition 6 into TEARDOWN
we have exactly the same issue here.
Our Teradici Device Logs Looks the same as the one from bickyz.
But on our side it is possible to use the VMware View Client to connect to the View Connection Broker and at least to Client, also the BLAST Connection works properly.
So the only issue we have is that a Connection is not possible trough the Zero Clients.
We tested it with both recommended Firmware Releases: 4.5.1 and 4.6.0,both of them showed the same Errors.
Has someone had the same issue and was able to resolve it? If so please be so Kind to enlight us with the solution or Workaround.
I would advise to open a support request with VMware to figure this one out.
It has been resolved
Our internal CA was using certificate with RSASSA-PSS for the signature algorithm; Zero Clients do not support this type of certificate. We changed it to issue SHA RSA instead.
And also on the Zero Clients make sure "Warn before connecting to untrusted servers" has been selected.
where we have to change this ? provide step by step info