Skip to content

Network Connectivity Issues

The Anyware Connector provides some diagnosic checks that can be used to troubleshoot the cause of issues you may be experiencing. Run the following command:

sudo /usr/local/bin/cas-connector diagnose

This command can also be used to verify that your Connector has been correctly configured. The diagnostic checks cover Remote Workstation connectivity and Active Directory connectivity.

The following table lists the flags associated with this command:

Flag Description
--rw The Remote Workstation FQDN
‑‑ad Verify connectivity to currently configured Active Directory server
‑h --help help for diagnose
--debug This flag can be run if you initial install of the Connector fails. It provides a detailed output of the Connector installation. This is useful for self-troubleshooting or to provide to the Teradici support team when logging a support ticket.

Common Installation Issues with the Connector

For information on issues relating to failed Connector installations, Teradici has a KB article that details troubleshooting steps for common issues related to installing the Connector, see here.

Remote Workstation Connectivity Check

This command will attempt to connect to the specified remote workstation on the ports required for establishing a PCoIP session. It checks to ensure that the PCoIP agent is running on the remote workstation.

Example command to diagnose remote workstation connectivity issues:

sudo /usr/local/bin/cas-connector diagnose --rw fqdn.of.my.rw

Check Passes

  • Your Connector is able to resolve the FQDN of the remote workstation and connect to it.
  • The PCoIP agent is running and responding on the remote workstation.

Check Fails

If the check fails it may be as a result of one or more of the following issues:

  • Firewall or network routing rules or restrictions may be in place.
  • A failure has occured and the FQDN of the remote workstation cannot be resolved.
  • The PCoIP agent on the remote workstation is not running or is unresponsive.
  • There may be an issue with the DNS name. For more information on this, and how to potentially resolve this issue, see DNS Name Resolution Configuration on RHEL/Rocky Linux.

Active Directory Connectivity Check

This command will attempt to connect to the Active Directory domain controller that was provided during installation using those same credentials.

Example command to diagnose Active Directory connectivity issues:

sudo /usr/local/bin/cas-connector diagnose --ad

Check Passes

  • The Connector is able to resolve the FQDN of the domain controller and authenticate to it.

Check Fails

If the check fails it may be as a result of one or more of the following issues:

  • Firewall or network routing rules or restrictions may be in place.
  • A failure has occured and the FQDN of the domain controller cannot be resolved.
  • The Active Directory server may be unresponsive.
  • The check was unable to authenticate to the Active Directory server.
  • There may be an issue with the DNS name. For more information on this, and how to potentially resolve this issue, see DNS Name Resolution Configuration on RHEL/Rocky Linux.