I wondered if anyone else had come across this before?
I have a small test network running Horizon View 5.3.1. I have 1 connection server and 1 security server paired. I have no issues with my security server sitting in my DMZ for use with remote access. The issues start when I try to connect to the connection server when I'm on the internal network. When using the latest version of the Windows View client (running on Windows 8.1 x64) and tryping in the FQDN of the connection server, I simply get an error right away saying 'Couldn't connect to server'. If I use the IP address then it works fine, but obviously is of no use as I can't verify the cert.
I've come accross issues in the past with using DNS shortnames (which also doesn't work) but I'm not concerened as I want to use FQDNs anyway.
I've checked DNS and everything seems fine. If I ping the connection server's FQDN I get a reply, all other servers are accessible via their FQDN and HTML access works fine using the FQDN and my certs check out OK.
This only seems an issue in the Windows View client. If anyone has any ideas I'd be very grateful.
Thanks
Pete