> 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/details/redes-y-acceso.md).

# Networks and Access

Remote access and site-to-site VPN, ports, 2FA, and the technical reason for each access option.

The environment is based on the same network model as Servers. Here are the access and security options, with the criteria for choosing each one. For network types and their details, go to Servers Details.

* Network types and details: [Networks (Servers).](https://docs.plenit.com/docs-en/productos/servers.md)

### Access and security options

Each option solves a different problem. The combination determines how exposed the environment is.

| Option             | What it solves                                             | Where it is configured         |
| ------------------ | ---------------------------------------------------------- | ------------------------------ |
| 2FA                | That access does not depend only on the password           | Remote Desktop Subscription    |
| Remote access VPN  | That a user can log in privately from outside              | Environment network            |
| Site-to-site VPN   | Permanently connect an office network with the environment | Environment network and server |
| Ports and firewall | Define what remains accessible from the outside            | Server Subscription            |

> #### 📘 Remote access or site-to-site
>
> Use the remote access VPN when individual people are connecting from home or while on the move. Use the site-to-site when you want an entire office to reach the environment as if it were on the same network, without each user setting up their own VPN.

### Remote access VPN

| Aspect        | Detail                                                                     |
| ------------- | -------------------------------------------------------------------------- |
| Usage         | Private connection of users to the environment through an encrypted tunnel |
| Configuration | Enable the VPN on the network, create users, and configure the client      |

### Site-to-site VPN

| Aspect        | Detail                                                      |
| ------------- | ----------------------------------------------------------- |
| Usage         | Permanently connect the office network with the environment |
| Configuration | Add a network card and static routes on the server          |

### Best practices

* Enable 2FA for users whenever you can: it is the layer that most reduces the risk of a compromised access.
* Open only the ports you need in the firewall, and rely on the VPN for private access.
* If an entire office needs the environment, set up a site-to-site instead of a VPN per user.

### Known limitations

| Limitation   | Detail                                                                                  |
| ------------ | --------------------------------------------------------------------------------------- |
| L2TP and NAT | One concurrent session per private network; it is solved with an alternative VPN client |

<br>


---

# 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/details/redes-y-acceso.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.
