4.6

Cause
The connectivity problems between a desktop and a View Connection Server instance can occur for different
reasons.
n
Lookup failure on the desktop for the DNS name of the View Connection Server host.
n
The ports for JMS, RDP, or AJP13 communication being blocked by firewall rules.
n
The failure of the JMS router on the View Connection Server host.
Solution
n
At a command prompt on the desktop, type the nslookup command.
nslookup CS_FQDN
CS_FQDN is the fully qualified domain name (FQDN) of the View Connection Server host. If the command
fails to return the IP address of the View Connection Server host, apply general network troubleshooting
techniques to correct the DNS configuration.
n
At a command prompt on the desktop, verify that TCP port 4001, which View Agent uses to establish JMS
communication with the View Connection Server host, is working by typing the telnet command.
telnet CS_FQDN 4001
If the telnet connection is established, network connectivity for JMS is working.
n
If a security server is deployed in the DMZ, verify that exception rules are configured in the inner firewall
to allow RDP connectivity between the security server and desktop virtual machines on TCP port 3389.
n
If secure connections are bypassed, verify that the firewall rules allow a client to establish either a direct
RDP connection to the desktop virtual machine on TCP port 3389, or a direct PCoIP connection to the
desktop virtual machine on TCP port 4172 and UDP port 4172.
n
Verify that exception rules are configured in the inner firewall to allow connections between each Security
Server and its associated View Connection Server host on TCP port 4001 (JMS) and TCP port 8009 (AJP13).
Connection Problems Due to Incorrect Assignment of IP Addresses to Cloned
Desktops
You might not be able to connect to cloned desktops if they have static IP addresses.
Problem
You cannot use View Client to connect to cloned desktops.
Cause
Cloned desktops are incorrectly configured to use a static IP address instead of using DHCP to obtain their IP
addresses.
Solution
1 Verify that the template for a desktop pool on vCenter is configured to use DHCP to assign IP addresses
to desktops.
2 In the VMware Infrastructure Client, clone one virtual machine manually from the desktop pool and verify
that it obtains its IP address from DHCP correctly.
VMware View Administration
288 VMware, Inc.