View Connection Server cannot communicate with Horizon Agent on a Linux virtual machine.


  1. On the Linux machine, open the Horizon Agent log file.


  2. Look for messages that indicate the hostname of the View Connection Server instance cannot be resolved.

    For example:

    2015-01-31T09:21:33.516Z DEBUG <JMS Handler for:svohraUb12x6> [JmsManager] 
         Using connection broker 
    2015-01-31T09:21:33.518Z DEBUG <JMS Handler for:svohraUb12x6> [JmsManager] 
         Unable to resolve hostname for
  3. Make sure the DNS service is configured properly on the Linux machine.

    The steps for configuring DNS vary depending on the Linux distribution and release. For instructions, consult the documentation for your Linux distribution.

    As a workaround, you can manually add the View Connection Server FQDNs to the /etc/hosts file on the Linux machine. However, this method is not recommended for production use. The proper solution is to configure the DNS service so that the Linux machine can resolve the View Connection Server FQDNs.

    After you take these steps, ping the View Connection Server hostnames to verify that they can be resolved. For example:


  4. If the problem continues, make sure that the system hostname of the Linux machine is resolvable.

    For example, on CentOS you might take the following steps:

    1. Open a terminal window and run the hostname command.

      The machine's hostname is displayed.

    2. Open the etc/hosts file and add the hostname.
      nano /etc/hosts 
      # Add the hostname: <your hostname> 
    3. Ping the hostname to verify that it can be resolved.
      ping <your hostname>



If you specify the DNS server on the Linux machine by manually editing the /etc/resolv.conf file, the setting might become lost in some Linux distributions. The setting is preserved if you specify the DNS server in the /etc/hosts file. For complete instructions for configuring DNS and the hostname, consult the documentation for your Linux distribution and release.