> For the complete documentation index, see [llms.txt](https://docs.plenit.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.plenit.com/docs-en/productos/remote-desktop/how-to/how-to-connect-to-remote-desktop-via-site-to-site-vpn.md).

# How to Connect to the Remote Desktop Environment via site-to-site VPN

Connect the Remote Desktop server to the customer's office network through a VPN tunnel: add the VPC network card and the static route to the remote network.

So that the Remote Desktop environment can reach the client's office network without exposing anything to the internet, you connect it through a site-to-site VPN tunnel. This guide covers the missing part on the Remote Desktop server side, once the tunnel already exists: adding the VPC network card and the static route to the remote network.

This is the topology we arrive at: the server goes out to the internet through the Standard network (its default route) and reaches the office network through the VPC network via the tunnel, thanks to a static route.

<figure><img src="https://files.readme.io/3811c0a232740315e25e3ab7c1db90c40b76b896f5d2d1b90b839a4ca5ae55f2-diagram-dos-suscripciones-er.png" alt=""><figcaption></figcaption></figure>

> #### 👍 What you get
>
> The Remote Desktop server communicating with the office network through the VPN tunnel, with its network card in the VPC and the static route to the remote network.

### Before you begin

This guide assumes that the VPN tunnel is already set up. You need to have before:

* An active Remote Desktop subscription. If you don't have one yet, set it up with the [Remote Desktop Quick Start.](https://docs.plenit.com/docs-en/productos/remote-desktop/quickstart.md)
* A network **VPC** with its associated TIER. The process is in [Server networks.](https://docs.plenit.com/docs-en/productos/servers/concepts/networks.md)
* A **site-to-site VPN tunnel** already created, in [How to create a site-to-site VPN tunnel.](https://docs.plenit.com/docs-en/productos/servers/how-to/how-to-create-a-site-to-site-vpn-tunnel.md)

> #### 📘 Where to see the VPN configuration
>
> The tunnel configuration (public IPs of both ends, networks, and TIER) is in the Servers subscription, in the VPN subsection. It will serve as a reference for the static route data in Step 2.

### Step 1. Add the VPC network card to the server

Go to the server tab that was deployed with the Remote Desktop environment: **Servers → edit server → Network Cards**. Click to add a new network card.

{/\* 📸 SCREENSHOT 1 · Server Network Cards · add new card \*/}

![Add a new network card to the server](https://reemplaza-url/escritorio-remoto-vpn-s2s-01.png)

In the wizard, select the **VPC (TIER) network** you want to connect and continue. If there is only one network available, just continue; if there are several, choose the correct one before continuing.

{/\* 📸 SCREENSHOT 2 · TIER network selection · continue \*/}

![VPC network selection and confirmation](https://reemplaza-url/escritorio-remoto-vpn-s2s-02.png)

When finished, the server has two interfaces: the **Standard (INT)** network as the default, and the new **VPC (TIER)**.

{/\* 📸 SCREENSHOT 3 · server with its two network cards \*/}

![Server with the new VPC network card](https://reemplaza-url/escritorio-remoto-vpn-s2s-03.png)

> #### 🚧 The default route still goes out through the Standard network
>
> The server keeps its default outbound path through the Standard network gateway. For it to reach the office network through the tunnel, you need to add a static route that goes through the VPC network gateway. That is Step 2.

### Step 2. Add the static route to the office network

Connect to the server (via RDP, web console, etc.), open **CMD as administrator** and add a persistent route that directs traffic from the remote network through the VPC gateway:

```shell
route -p add <OFFICE_NETWORK> mask <MASK> <VPC_GATEWAY> METRIC 1
```

For example, to reach the office network `192.0.2.0/16` through the VPC gateway `10.0.0.254`:

```shell
route -p add 192.0.2.0 mask 255.255.0.0 10.0.0.254 METRIC 1
```

{/\* 📸 SCREENSHOT 4 · CMD with the route -p add command executed \*/}

![Static route added from CMD](https://reemplaza-url/escritorio-remoto-vpn-s2s-04.png)

> #### 📘 One route for each remote network
>
> If the tunnel provides access to several remote networks, add one static route for each one.
>
> The option `-p` makes it persistent, so it survives server restarts.

### Conclusion

Connecting Remote Desktop over site-to-site VPN, once the tunnel exists, is two steps: give the server a foothold in the VPC network with a new network card, and tell it how to reach the office with a persistent static route to the VPC gateway.

With that, the environment reaches the client's network through the encrypted tunnel, without exposing the service to the internet. Remember to add one route for each remote network it needs to reach.


---

# 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.plenit.com/docs-en/productos/remote-desktop/how-to/how-to-connect-to-remote-desktop-via-site-to-site-vpn.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.
