> 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/es/knowledge-base/troubleshooting-articles/remote-desktop-manager-virtual-channels-are-not-allowed-in-restrictive-environments.md).

# Los canales virtuales de Remote Desktop Manager no se permiten en entornos restrictivos

Resuelva las restricciones de canales virtuales de Remote Desktop Manager en entornos restringidos añadiendo los canales RDMJump, RDMCmd y RDMLog a la lista blanca.

### Canales virtuales

Los canales virtuales son vías de comunicación establecidas entre un cliente y una sesión remota para facilitar la transmisión de datos. Remote Desktop Manager utiliza tres canales virtuales para las sesiones RDP con el fin de saltar y ejecutar comandos: ***RDMJump***, ***RDMCmd*** y ***RDMLog***.

Estos canales virtuales pueden estar restringidos en entornos donde no se permiten los canales virtuales.

### Solución

Se deben crear excepciones en los entornos para añadir los canales virtuales de Remote Desktop Manager a la lista blanca.


---

# 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 dynamically 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/es/knowledge-base/troubleshooting-articles/remote-desktop-manager-virtual-channels-are-not-allowed-in-restrictive-environments.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 `build a script that syncs our docs to a CMS` 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.