Configuring Gateways for Isolated Remote Access

Gateway Peer Nodes are required for enabling remote access session to isolated endpoints, specifically those that cannot be reached directly from the 12Port master node. By configuring a Peer Node to function as a Gateway, you can extend remote access capabilities beyond the local network.

This is especially valuable for Managed Service Providers (MSPs) and administrators managing assets across multiple environments, such as on-premises networks and cloud infrastructures.

Enabling Gateway Peer Nodes

This guide assumes that a functional Peer Node is already deployed and enabled for remote job execution within the isolated network. The next step is to extend this existing Peer Node to support Remote Access sessions through Gateway functionality.

Note: If a Peer Node has not yet been configured, refer to the Peer Node Configuration page. Once the Peer Node is fully configured, connected, and verified, return to this article to complete the Gateway setup.

1. Login with an Administrator account and navigate to Configuration > Peer Nodes.
2. Locate the existing Peer Node that will be extended and select Actions > Edit.
3. Toggle the Includes Gateway parameter.
4. Once enabled, the Gateway Address field will appear. Enter the hostname of the Peer Node, followed by port 4822.
   • Example: remote.contoso.com:4822
5. At the top of the configuration page, click Verify Trust (Gateway). Use the Establish Trust button to establish a trusted connection with the remote Peer Node.
6. After verification is successful, close the trust dialog and click Save to apply changes.

Testing Connectivity:

After enabling the Gateway feature, perform the following steps to validate the setup:

1. Go to the Asset Database and either locate or create an asset representing an endpoint in the isolated network.
2. From the asset's Manage > Peer Nodes page, confirm that the appropriate Peer Node is listed. If not, click Add to associate the Gateway enabled Peer Node with the asset or its parent container.
3. Initiate a remote access session by clicking the Access button for the asset. Confirm that the session connects to the isolate endpoint successfully.
4. After the session completes, go to the asset’s Reports > Sessions section.
5. Expand the session details and verify that the Gateway column displays the correct Peer Node address used in the earlier configuration.