6.0

Table Of Contents
Table 54. Ports Opened During View Connection Server Installation (Continued)
Protocol Ports View Connection Server Instance Type
AJP13 TCP 8009 Standard and replica
HTTP TCP 80 Standard, replica, and security server
HTTPS TCP 443 Standard, replica, and security server
PCoIP TCP 4172 in;
UDP 4172 both
directions
Standard, replica, and security server
HTTPS TCP 8443 Standard, replica, and security server.
After the initial connection to View is made, the Web browser on a client device
connects to the Blast Secure Gateway on TCP port 8443. The Blast Secure Gateway
must be enabled on a security server or View Connection Server instance to allow
this second connection to take place.
HTTPS TCP 8472 Standard and replica
For the Cloud Pod Architecture feature: used for interpod communication.
HTTP TCP 22389 Standard and replica
For the Cloud Pod Architecture feature: used for global LDAP replication.
HTTPS TCP 22636 Standard and replica
For the Cloud Pod Architecture feature: used for secure global LDAP replication.
Configuring a Back-End Firewall to Support IPsec
If your network topology includes a back-end firewall between security servers and View Connection
Server instances, you must configure certain protocols and ports on the firewall to support IPsec. Without
proper configuration, data sent between a security server and View Connection Server instance will fail to
pass through the firewall.
By default, IPsec rules govern the connections between security servers and View Connection Server
instances. To support IPsec, the View Connection Server installer can configure Windows firewall rules on
the Windows Server hosts where View servers are installed. For a back-end firewall, you must configure the
rules yourself.
NOTE It is highly recommended that you use IPsec. As an alternative, you can disable the View
Administrator global setting, Use IPsec for Security Server Connections.
The following rules must allow bidirectional traffic. You might have to specify separate rules for inbound
and outbound traffic on your firewall.
Different rules apply to firewalls that use network address translation (NAT) and those that do not use
NAT.
Table 55. Non-NAT Firewall Requirements to Support IPsec Rules
Source Protocol Port Destination Notes
Security server ISAKMP UDP 500 View Connection
Server
Security servers use UDP port 500 to
negotiate IPsec security.
Security server ESP N/A View Connection
Server
ESP protocol encapsulates IPsec
encrypted traffic.
You do not have to specify a port for
ESP as part of the rule. If necessary,
you can specify source and destination
IP addresses to reduce the scope of the
rule.
Chapter 5 Installing View Connection Server
VMware, Inc. 57