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/workbench/tools.md.
🎉 JumpServer v5.1.1 is available. See what's new →
  • v5

    • Tools

    Tools runs network diagnostics from the JumpServer server to a destination address. Use it to check whether JumpServer can reach an asset, a host, or a service before you troubleshoot a failed connection.

    Figure 1: The Tools page with the Ping tab

    Prerequisites

    • The Tools in the Workbench feature is enabled by an administrator. Without it, the Tools entry does not appear in the Workbench navigation.
    • Your role grants access to the system tools.

    Administrators can also use the Tools page under System Settings, which adds a basic server-information tab.

    Run a test

    1

    Select a diagnostic tab, for example Ping.

    2

    Enter the destination address or host name. Some tabs require an additional port or port list.

    3

    Click Test. The command output streams into the Output terminal.

    4

    Click Stop to interrupt a test that is still running. Closing or refreshing the page also ends the test from the browser side.

    The page shows the current Server time above the form. This is the time on the JumpServer server that runs the diagnostic, not the local time of your browser.

    Tab reference

    TabFieldsUse
    PingDestination addressCheck basic ICMP reachability and latency to a host
    TelnetDestination address, destination portCheck whether a specific TCP port accepts connections
    NmapDestination address, destination portsScan one or more ports on a host
    TracerouteDestination addressShow the network path and hops to a host

    Depending on the release, a Tcpdump tab may also be available for packet capture. The tabs shown are controlled by the server configuration, so a tab that appears in one deployment may not appear in another.

    Notes

    Note

    Tests run from the JumpServer server or its containers, not from your browser. A successful test proves that JumpServer can reach the target; it does not prove that your workstation can reach it, or that the target's login configuration is correct.

    Tip

    Use Ping first to confirm the host is reachable, then Telnet on the service port. If both succeed but a connection still fails, check the asset account, authorization, and access policies rather than the network.