4.6

Solution
n
Check that the following network ports are opened on the firewall for the security server or View
Connection Server host.
Port Description
TCP 4172 From View Client to the security server or View Connection Server host.
UDP 4172 Between View client and the security server or View Connection Server host, in both directions.
TCP 4172 From the security server or View Connection Server host to the View desktop.
UDP 4172 Between the security server or View Connection Server host and the View desktop, in both directions.
n
In View Administrator, enable the PCoIP Secure Gateway and make sure that the PCoIP External URL is
configured correctly.
a Click View Configuration > Servers.
b Select the security server or View Connection Server instance and click Edit.
c Select Use PCoIP Secure Gateway for PCoIP connections to desktop.
The PCoIP Secure Gateway is disabled by default.
d In the PCoIP External URL text box, make sure that the URL contains the external IP address for the
security server or View Connection Server instance that View clients can access over the Internet.
Specify port 4172. Do not include a protocol name.
For example: 100.200.300.400:4172
e Make sure that both the PCoIP External URL and secure tunnel External URL are the addresses that
client systems use to reach this host.
For example, if you configure a View Connection Server host, do not specify the PCoIP External
URL for this host and the secure tunnel External URL for a paired security server.
f Click OK.
n
If the user is connecting through a web proxy that is outside of your network, and the proxy is blocking
a required port, direct the user to connect from a different network location.
n
Make sure that both the security server and the paired View Connection Server instance are View 4.6 or
later.
Connection Problems Between Desktops and View Connection Server Instances
You might experience connection problems between desktops and View Connection Server instances.
Problem
If connectivity between a desktop and a View Connection Server instance fails, you see one of the following
messages in the event database.
n
Provisioning error occurred for Machine Machine_Name : Customization error due to no network
communication between the View agent and Connection Server
n
Provisioning error occurred on Pool
Desktop_ID because of a networking problem with a View
Agent
n
Unable to launch from Pool Desktop_ID for user User_Display_Name : Failed to connect to Machine
MachineName using Protocol
Chapter 15 Troubleshooting View Components
VMware, Inc. 287