> For the complete documentation index, see [llms.txt](https://docs.devolutions.net/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.devolutions.net/rdm/knowledge-base/how-to-articles/automatically-detect-and-bypass-jump-host-for-direct-connections-in-local-network.md).

# Automatically detect and bypass jump host for direct connections in local network

Configure Remote Desktop Manager to automatically detect local hosts and bypass the jump host for direct connections on the same network.

A jump host acts as a gate between two trusted networks, allowing access, but only with the permission of the jump host.

However, in the case of maintaining multiple connections through a jump host on the same network, the current procedure requires disabling the jump host or resorting to the direct connection (without jump host) alternative. Learn how to bypass the jump host below.

1. Go to the ***Properties*** of your entry.
2. Click on ***Connect if unable to ping/port scan*** under ***Connection – VPN/SSH/Gateway – General – Connect***.
3. Click ***OK*** to save and close the window.

Remote Desktop Manager automatically tests if the host responds, if not the VPN opens.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.devolutions.net/rdm/knowledge-base/how-to-articles/automatically-detect-and-bypass-jump-host-for-direct-connections-in-local-network.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.