KBI 311013 New Feature: Remote Trusted Agent With Reversed TCP Connection


Argent Advanced Technology 3.1A-1407-A and later


Wednesday, 23 July 2014


Customer installs Remote Trusted Agent to monitor remote network that either has slow link or blocked by firewall

By default, Remote Trusted Agent initiates TCP connection to exchange information with the Main Engine

This default architecture has the minimum configuration on network, because customer only needs to open up a single port firewall at Main Engine to allow all the Remote Trusted Agents to connect

But this network configuration is not always available

For example, some organization only allows connection being initiated by server at main network to connect to any server at DMZ

In this case, the default installation of Remote Trusted Agent will not work

Argent AT 3.1A-1407-A implements Remote Trusted Agent with reversed TCP connection

In such architecture, it is the Main Engine that initiates the TCP connection and connects to the Remote Trusted Agent

Customer runs Argent AT setup to install such a Remote Trusted Agent

The only difference is to make sure the option ‘Connect From Main Engine To Remote Component‘ is checked

After the Remote Trusted Agent with reversed TCP connection is installed, Argent AT Main Engine won’t discover this Trusted Agent automatically as usual

This is because the installed Trusted Agent does not initiate the TCP connection; it simply sits there waiting for Main Engine to contact instead

Customer needs one more extra step to connect to such a Remote Trusted Agent

Customer will be prompted for the Remote Trusted Agent to connect

After successful connection, the Trusted Agent can be used as usual

Technical Background



Upgrade to Argent AT 3.1A-1407-A or later