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

Trouble binding to Active Directory

Hi,

I am trying to connect a ASG 8.0 to our Active Directory. I am pretty sure I got the Bind DN right and the user has the proper right (Domain Admin). However, each time I hit the test button I get:

Error: Server exists and accepts connections, but bind to ldap://172.16.111.210:389 failed with this Bind DN and Password

In the log I see this:

name="Bind test failed. Method: adirectory, error: DENIED

Is there anything on the AD I have to set up in order for the ASG to be able to authenticate?

Thanks
Sascha

This thread was automatically locked due to age.

Parents

0 Peter D over 14 years ago

Hi Sascha,

no, there is nothing to do in the AD.

On the Tab Servers the following settings should work:

Server: of course your AD Server.
Port: usually 389

Bind DN: CN=administrator,CN=Users,DC=domain,DC=local
(You have to verify, if your account administrator really is in the OU "Users")
(DC=local can also be something else.. it's your domain suffix)

Password: ok... you should know [:D]

Usually it's a problem with the OU of the administrator account, as i said before.

I hope, i could help you..

Peter
Cancel
Vote Up 0 Vote Down

Cancel

Reply

0 Peter D over 14 years ago

Hi Sascha,

no, there is nothing to do in the AD.

On the Tab Servers the following settings should work:

Server: of course your AD Server.
Port: usually 389

Bind DN: CN=administrator,CN=Users,DC=domain,DC=local
(You have to verify, if your account administrator really is in the OU "Users")
(DC=local can also be something else.. it's your domain suffix)

Password: ok... you should know [:D]

Usually it's a problem with the OU of the administrator account, as i said before.

I hope, i could help you..

Peter
Cancel
Vote Up 0 Vote Down

Cancel

Children

No Data