Can you provide us additional details about the environment?
- What version are the connection servers?
- What version of the horizon client?
- Is this internal or external connections?
- Is tunneling enabled?
- Are security servers or UAG in use?
- Which display protocol is used?
I can provide some of the info.
Not sure if you mean version of windows server(Server 2012 R2) or the version of Vmware(7.5)
Horizon client version is 4.10.0 build-11021086
External connections. We also have a VPN that connects to the internal network and it works fine outside our network when using th eVPN tunnel.
Connecting to the Web portal works fine. It is only the Horizon Client that is failing.
We have a security Server
Display Protocol is PCoIP
Tunneling is enabled
I am talking about VM Horizon client 4.10 version. I am unable to connect my VDI using 4.10 version installation in any computer.
I don't see it as fixed, not sure if I have to tweak some setting to make it work.
Horizon Client 4.10 should be able to connect to a Horizon 7.5.0 environment without any adjustments.
This could be a firewall issue. Which display protocol is the pool configured for along with the Horizon Client?
I am able to connect my VDI using 4.9 version of client without any firewall issues and I am connecting from home so I don't think firewall will be an issue here.
Any other thoughts?
Are you first connecting to a VPN and then just pointing the Horizon Client to one of the internal connection servers?
I was searching round the internet for an answer to this as we have had some users come in with Ipads not working with Horizon and pinned it down to the 4.10 client.
On checking the notes it seems that they have disabled TLS1.0 with v4.10 so if you are running an older version VMWare Horizon View Admin (older than 6.2.1 according to the linked thread) then the clients will not be able to connect.
I thought I would update this thread as this was the top search result for me and had to dig deeper for the linked thread
Yeah TLS was only disabled on the client side with this update so old clients will still work