Try TT Now

TTM Network Administration

Configuring the Remote Client

Overview

A Remote Client connects to a Remote Host Daemon situated on the TT network. To configure the Remote Client, you use the Daemon Setup dialog box in Guardian on the Remote Client (i.e., the machine that hosts X_TRADER).

Configuring the Remote Client

When setting up a TT application for a remote connection, in Guardian's Daemon Setup dialog box, you must:

  • Enter the external IP address of the Remote Host Daemon to which X_TRADER connects.
  • If you configure your Remote Client to support failover, you must also enter the IP address of the backup Remote Host Daemon.
  • If a NAT firewall separates a Remote Host Daemon and the Remote Client application, ensure that the IP address fully resolves to the Remote Host Daemon.
  • If different from 10200, enter the port to which the Remote Client connects. If a NAT firewall separates the Remote Host Daemon and client application, ensure that the port fully resolves to the Remote Host Daemon.
  • If you use a non-primary NIC for your TT communications, bind the TTM Daemon to it.
  • If you do not want TTM to compress data, disable data compression.
    Note

    TT recommends that you use the default setting and have TTM compress its data before sending it over the Internet or other network.

To configure the Remote Client:

  1. To open Guardian, double-click the TT icon in the system tray.
  2. On the Config menu, click Daemon Setup.

    The Daemon Setup dialog box appears.

  3. In the Remote Proxy Daemon section, in the IP Address (1) box, enter the external IP address of the Remote Host Daemon to which you want the Remote Client to connect.
  4. If you want to setup failover, in the Remote Proxy Daemon section, in the IP Address (2) box, enter the external IP address of the backup Remote Host Daemon.

    The Remote Client attempts to connect to this backup Remote Host Daemon if it cannot connect or loses a connection to the Remote Host Daemon whose IP address you entered in this step.

  5. If the Remote Host Daemon uses a port other than 10200, in the Remote Proxy Daemon section, in the Port box, drag to select 10200 and then type the port number that the Remote Host Daemon uses.
  6. If you do not want to use compression, click to remove the checkmark from Enable Compression.

    If your Remote Client compresses data, the Remote Host Daemon to must also compress data (this is its default behavior). For further details, refer to Compressing Data.

  7. To save your changes, click OK.

    A Guardian prompt appears stating that for your changes to take effect, you must stop and restart all relevant processes.

  8. Click Yes.

Example Setup

The following example of a Daemon Setup dialog box illustrates that the Remote Client is:

  • Set to connect to a Remote Host Daemon whose:
    • External IP address is 100.248.40.200
    • External port number is 10200.
  • Set up for failover: the IP address of the backup Remote Host Daemon is 100.248.40.201.

All of the other settings that the Remote Client uses are default.

Connectivity Problems

At startup, if you receive the following Guardian prompt box, then the TT application cannot connect to the Remote Host Daemon on the remote network.

Connectivity problems can arise for several different reasons, including:

  • Your settings are incorrect. In this case, open the Daemon Setup dialog box, and verify that all settings (IP addresses, ports, and interfaces) are correct. If you could previously connect, call the host site to determine if the Remote Host Daemon settings have changed.
  • You are not connected to the internet or network. In this case, check that your connection is active.
  • Your VPN is down. This scenario is only valid if you are using or need to use a VPN to connect to the Remote Host Daemon.
  • The ports are not open on the firewall or intermediary routers. Check to make sure that the remote application uses a port that is open and available on the firewall.
  • The IP address is not properly translated through a NAT firewall. Verify that the IP address used by the Remote Client revolves to the Remote Host Daemon (i.e., that the Remote Client connects to the Remote Host Daemon’s external IP address).