Single Node Network Flow
In a single node deployment, all network traffic flows through a standalone 12Port server. This configuration supports both user-initiated sessions and automated operations without the need for additional infrastructure.
Diagram Overview
The diagram above illustrates the network flow through a single 12Port node.
-
The blue rectangle represents 12Port Server
-
User Access via Browser Users connect to the server’s HTTPS port (typically
443
or6443
) to:- Navigate the tenant site, container, and asset hierarchy.
- Manage and configure tenant settings.
- Launch web-based remote sessions (SSH, RDP, VNC, Telnet, HTTP).
-
API Access for Automation Scripts, integrations, and automation tools use the same HTTPS port (
443
or6443
) to access the 12Port REST API. -
Job Execution The 12Port job pool executes jobs directly on remote endpoints using protocols such as:
- SSH
- WinRM and secure WinRMs
- LDAP(s)
- HTTP(s)
- Telnet
-
Native RDP Access Users can establish native RDP sessions using RDP clients (e.g., Microsoft Remote Desktop, Remote Desktop Connection Manager, MobaXTerm, etc) by connecting to the RDP Proxy port individually configured per tenant (typically
3300
,3301
, ...). -
Native SSH Access
- Users can initiate SSH sessions (including
ssh
,scp
,sftp
,exec
, or tunnels) using SSH clients (e.g., Shell, PowerShell, PuTTY, MobaXTerm, WinSCP, etc) by connecting to the SSH Proxy port individually configured per tenant (typically2200
,2201
, ...). - SSH connections also provide access to the 12Port terminal interface.
- Users can initiate SSH sessions (including