From 7ef1cddebe71fed66a8af0721fec5bbf13de6767 Mon Sep 17 00:00:00 2001 From: RustDesk <71636191+rustdesk@users.noreply.github.com> Date: Wed, 23 Jul 2025 23:25:05 +0800 Subject: [PATCH] Updated FAQ (markdown) --- FAQ.md | 8 ++++++-- 1 file changed, 6 insertions(+), 2 deletions(-) diff --git a/FAQ.md b/FAQ.md index 49b5676..3af65f5 100644 --- a/FAQ.md +++ b/FAQ.md @@ -1144,12 +1144,16 @@ Solution: Please change scope from one to sub. image > 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. +> 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. +> +> ![image](https://github.com/user-attachments/assets/11c107df-16e8-4356-b347-af35c576e6ee) > > 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. +> I’ve now updated the configuration to use sAMAccountName as the `Username Attribute`, and everything is working as expected. # Unstable connection and "Failed to connect via rendezvous server: Please try later" on Windows server running RustDesk server