> 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/troubleshooting-articles/microsoft-rdp-automatic-logon-issues.md).

# Microsoft RDP automatic logon issues

Microsoft RDP automatic logon issues in Remote Desktop Manager are fixed by enabling Network Level Authentication, Public mode, or checking credential settings.

Sometimes the automatic logon does not function and your credentials are requested by the remote system. Here are some steps to help identify the issue. Support for automatic logon was introduced on Windows 2003/XP, so ensure you are trying to connect to these or later versions. Windows 2000 does not support the automatic login.

### RDP Sessions connect successfully when in External mode, but not in Embedded mode.

This issue may be caused by a bad authentication negotiation because in some cases Single Sign On (SSO) requires Network Level Authentication (NLA). It can happen when prompting for credentials and when using automatic logon.

Check the ***Activate network level authentication NLA (SingleSignOn)*** in the ***Connection*** tab of your session.

{% hint style="info" %}
You might also have to check the ***Public mode*** option in the ***Advanced*** tab to make it work.
{% endhint %}

### The connection was denied because the user account is not authorized for remote login

Enabling the ***Public mode*** option in the ***Advanced*** tab resolves the issue.

### Ensure credentials are entered properly

Remote Desktop Manager allows for advanced credential management. Depending on your choice of: ***Custom***, ***Linked (vault)***, ***Embedded*** or ***Inherited*** ensure the credentials are properly entered.

{% hint style="warning" %}
Ensure that ***Always ask password*** is not checked.
{% endhint %}


---

# 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/troubleshooting-articles/microsoft-rdp-automatic-logon-issues.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.