For AI agents: the complete documentation index is available at https://www.jumpserver.com/docs/llms.txt, the full documentation bundle is available at https://www.jumpserver.com/docs/llms-full.txt, and this page is available as Markdown at https://www.jumpserver.com/docs/features/system-settings/appearance-tools/tools.md.
๐ŸŽ‰ JumpServer v5.1.1 is available. See what's new โ†’

System Tools

System Tools provides a set of network diagnostics that run from the JumpServer host. Use it to check whether an asset is reachable before you troubleshoot a connection, and to confirm which port or route is failing.

Overview

ToolPurpose
pingCheck whether a host responds to ICMP, confirming basic reachability and latency.
telnetTest whether a specific TCP port accepts a connection, for example SSH on port 22 or RDP on port 3389.
nmapScan a host for open ports and identify exposed services.
tcpdumpCapture traffic on the JumpServer host to inspect packet loss or protocol errors.
tracerouteShow the network path to the target and locate the hop where connectivity breaks.

Run a diagnostic

1

In the right area of the top navigation bar, click .

image
2

In the left menu, click System Tools.

3

Select the tool tab you need.

4

Enter the target address, and a port when the tool requires one.

5

Run the command and review the output. The server time banner at the top of the page shows the clock used by the command.

Figure 1: System Tools page

Enable the tools in the workbench

The Basic tab contains a single option, Tools in the workbench. When it is enabled, the same diagnostics are also available to users from the Workbench tools page, which lets operators check connectivity without entering System Settings.

1

Open the Basic tab.

2

Select Tools in the workbench.

3

Click Submit.

Note

The commands run on the JumpServer server, not in the user's browser. Traffic therefore originates from the JumpServer host network and is subject to the same routing, firewall, and proxy rules as any other JumpServer connection. Tools that are not installed in the runtime image, or that lack the required kernel capabilities, are not available even when the feature is enabled.