Create a Post
cancel
Showing results for 
Search instead for 
Did you mean: 
zhangchuang
Contributor
Jump to solution

Successfully connected, but could not get login DNFill it manually in the LDAP Account Unit object

Hi ,

I am currently encountering a problem. When I enable the identity awareness feature blade to connect to the user's AD domain, the prompt 'Successfully connected, but could not get login DNFill it manually in the LDAP Account Unit object' appears. I have changed my administrator account and the problem still persists.

The version I am currently using is the R81.20 T24 patch. May I ask where to troubleshoot this situation?

0014.png

0 Kudos
1 Solution

Accepted Solutions
zhangchuang
Contributor

Hi ,

I have opened the case and will solve the problem. This is because the client's server version is windows server 2022, and we solved it by using Identity Collector.

View solution in original post

0 Kudos
4 Replies
_Val_
Admin
Admin

Did you try filling in the logon DN manually, as the message suggests?

0 Kudos
zhangchuang
Contributor

Hi ,

I have opened the case and will solve the problem. This is because the client's server version is windows server 2022, and we solved it by using Identity Collector.

0 Kudos
kamilazat
Advisor

Did TAC tell you why this was the case? With earlier MSAD versions (<2022) this process was pretty straightforward. Did you manage to get an explanation as to what changed?

0 Kudos
zhangchuang
Contributor

SK179821 has relevant instructions

Leaderboard

Epsum factorial non deposit quid pro quo hic escorol.

Upcoming Events

    Tue 07 Oct 2025 @ 09:30 AM (CEST)

    CheckMates Live Denmark!
    CheckMates Events