Hello,
The problem:
Our smart tunnel tech does not appear to be forwarding traffic from our new view client. I am wondering what kind of configuration changes should be considered to enable such a connection. The error returned when searching for hostname is along the lines of hostname not found. The error when searching for IP is related to timeout.
Background info and specs:
We are in the process of upgrading our View Connection Servers from 5.2 to 6.2. As a part of the upgrade we want to upgrade our Horizon View clients to use version 3.5.0. To make it easier on vendors and remote PCs we also prefer to ThinApp our Horizon View Client with ThinApp 4.7.3. We currently have a Cisco ASA supporting a SSL VPN Portal with "Smart Tunnel" technology. The ASA is currently on firmware 9.3.3 in production but we have access to version 9.5 in test.
Preferred connection scenario:
User > PC > VMware View Client (ThinApp'd) > Cisco ASA Smart Tunnel > View Connection Server > Virtual Desktop
.exes running from the ThinApp view client:
It seems the ThinApp version of the View Client is only launching VMware-view.exe.
.exes running from the full/thick view client:
- VMware-view.exe
- ftnlsv.exe
- vmwsprrdpwks.exe
- ftscanmgr.exe
Is there anything else to consider when configuring either the thick or ThinApp view client to work with the Cisco SSL VPN Portal and Smart Tunnel? We should have ports configured in the firewall as connecting with the same view client does work with the port forwarder feature of the SSL VPN Portal.