mirror of
https://github.com/rustdesk/rustdesk.git
synced 2025-05-11 10:26:19 +02:00
Updated FAQ (markdown)
parent
097a00b626
commit
2c744d7924
1 changed files with 8 additions and 0 deletions
8
FAQ.md
8
FAQ.md
|
@ -948,6 +948,14 @@ Solution: Please change scope from one to sub.
|
|||
|
||||
<img width="572" alt="image" src="https://github.com/user-attachments/assets/b2ac168d-5bb5-4afc-a24f-65e63828a6fc" />
|
||||
|
||||
> I got "I/O error: User not found" error when using some user names
|
||||
>
|
||||
> The issue was caused by the LDAP configuration missing the correct username attribute. As a result, we were only able to log in using the display name instead of the sAMAccountName.
|
||||
>
|
||||
> It happened to work for the "cc" account because the display name and sAMAccountName were identical. In my case, however, the display name was "AA BB" while the sAMAccountName was "aa", and I had only been attempting to log in using the sAMAccountName, which is why my user couldn't be found.
|
||||
>
|
||||
> I’ve now updated the configuration to use sAMAccountName as the username attribute, and everything is working as expected.
|
||||
|
||||
# Rendezvous errors with running RustDesk server on Windows
|
||||
|
||||
> User: For around 40% of the customers we have, when we connect via RustDesk, we keep getting Rendezvous errors.
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue