Guest User!

You are not Sophos Staff.

Thread Info
  • State Suggested Answer
  • Locked Locked
  • Replies 23 replies
  • Answers 2 answers
  • Subscribers 12 subscribers
  • Views 60635 views
  • Users 0 members are here
Options
Suggested
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Problems with Auth. server

Edgar_Quintana

Hi,

I´ve a UTM 125 and two AD servers and I´d like to integrate this device with de AD

I tried to configure  like that:

DN : CN=ldap user,OU=Administrador,DC=xxxx,DC=NET but with those parameters,

Server exists and accepts connections, but  bind to xxxxxxx  failed with this BIND  and Password

Any idea?

Regards and thanks



This thread was automatically locked due to age.
Parents
  • 0

    Personally, I try to avoid spaces in names, like "ldap User".
    Does the ldap user account have proper privileges? It has to have permissions to query for account information.
    Although the documentation states that Bind DN may be empty, I always populate it with the root of the directory, i.e. DC=xxxx,DC=NET.
    What errors, if any are you seeing in the Client Authentication Daemon log when you run the test?

Reply
  • 0

    Personally, I try to avoid spaces in names, like "ldap User".
    Does the ldap user account have proper privileges? It has to have permissions to query for account information.
    Although the documentation states that Bind DN may be empty, I always populate it with the root of the directory, i.e. DC=xxxx,DC=NET.
    What errors, if any are you seeing in the Client Authentication Daemon log when you run the test?

Children
No Data