From 2c744d7924426c1f28e33098c323e6d55d827218 Mon Sep 17 00:00:00 2001 From: RustDesk <71636191+rustdesk@users.noreply.github.com> Date: Thu, 24 Apr 2025 22:04:23 +0800 Subject: [PATCH] Updated FAQ (markdown) --- FAQ.md | 8 ++++++++ 1 file changed, 8 insertions(+) diff --git a/FAQ.md b/FAQ.md index 7faf2c3..ae3973a 100644 --- a/FAQ.md +++ b/FAQ.md @@ -948,6 +948,14 @@ 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. +> +> 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.