Sample setup for the target servers located behind a SOCKS proxy server


The following diagram shows a sample setup in which the remote (target) servers that you want to manage are on a different network from the TrueSight Server Automation system. An Application Server communicates with the remote servers through your SOCKS internet protocol proxy server. The PsExec server, which is required to communicate with a Windows target server, is also present behind the SOCKS proxy server.

SOCKSSetUp.png

The different ports and protocols through which the Application Server, SOCKS proxy server, and PsExec server communicate in this setup are as follows:

Port

Protocol

Source

Destination

22

SSH (TCP)

SOCKS proxy server

Agentless device

139-445

NETBIOS (TCP)

PsExec server

Agentless device

4750

RSCD (TCP)

SOCKS proxy server

RSCD agent

The following ports need to be open on various computers in a set up in which the remote (target) servers that you want to manage are on a different network from the TrueSight Server Automation system:

  • 22
  • 139
  • 445
  • 4750

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*

TrueSight Server Automation 23.2