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
2 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

Leaderboard

Epsum factorial non deposit quid pro quo hic escorol.

Upcoming Events

    Tue 30 Apr 2024 @ 08:00 AM (CDT)

    Central US: What's New in R82?

    Tue 30 Apr 2024 @ 03:00 PM (CDT)

    EMEA: CPX 2024 Recap

    Wed 01 May 2024 @ 02:00 PM (EDT)

    South US: HTTPS Inspection Best Practices

    Thu 02 May 2024 @ 11:00 AM (SGT)

    APAC: What's new in R82

    Tue 30 Apr 2024 @ 08:00 AM (CDT)

    Central US: What's New in R82?

    Tue 30 Apr 2024 @ 03:00 PM (CDT)

    EMEA: CPX 2024 Recap

    Wed 01 May 2024 @ 02:00 PM (EDT)

    South US: HTTPS Inspection Best Practices

    Thu 02 May 2024 @ 11:00 AM (SGT)

    APAC: What's new in R82
    CheckMates Events