> 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/server/de/knowledge-base/troubleshooting-articles/the-remote-server-returned-an-error-400-bad-request.md).

# The remote server returned an error (400) Bad Request

Behebt die Meldung „remote server returned an error 400 Bad Request“ in Remote Desktop Manager durch Reduzierung der Anzahl der AD-Gruppen oder Erhöhung der IIS-Header-Größenlimits.

Sie erhalten den folgenden Fehlermeldungsdialog, wenn Sie versuchen, sich mit Remote Desktop Manager an der Devolutions Server-Instanz zu authentifizieren.

```
The remote server returned an error (400) Bad Request
```

### Lösung

Es gibt zwei verschiedene Lösungen für dieses Problem:

* Reduzieren Sie die Anzahl der AD-Gruppen, in denen das Benutzerkonto Mitglied ist. Wir sind uns bewusst, dass es aufgrund des Aufbaus der AD-Struktur meistens nicht möglich ist, die Anzahl der AD-Gruppen zu reduzieren.
* Erhöhen Sie die Einstellungen für die Registrierungseinträge ***MaxFieldLength*** und ***MaxRequestBytes*** auf dem Server. Weitere Informationen dazu, wie Sie diese Werte erhöhen können, finden Sie im folgenden Microsoft-Artikel. <https://support.microsoft.com/en-us/help/2020943/http-400-bad-request-request-header-too-long-response-to-http-request>


---

# 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/server/de/knowledge-base/troubleshooting-articles/the-remote-server-returned-an-error-400-bad-request.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.
