I have configured an account collector for Active Directory in RSA Via 7.0.0.
After providing the connection details, when I clicked on Test Connection, I got the following error message :
com.aveksa.common.ConnectException: there is an error establishing a connection with the LDAP directory. Please confirm the setting are correct
Please see the attched screenshot
Hi Boris,
Thank You for quick response. But here in customer environment, LDAP browser is not installed..i have told them to install it.
But i run this command from virtual machine :
host -t srv _ldap._tcp.DOMAINNAME
in my case it is host -t srv _ldap._tcp.DC01
got the following :
; ; connection timed out; no servers could be reached
is there any other way round to check the connection to AD?
You can use ldapsearch (from your Linux)
ldapsearch -x -LLL -h [host] -D [user] -w [password] -b [base DN] -s sub "([filter])" [attribute list]
Here is an example from my box:
ldapsearch -x -LLL -h dc.demo.local -D cn=administrator,cn=users,DC=DEMO,DC=local -w Mypassword -b "dc=demo,dc=local" -s sub "(objectClass=user)" givenName
ldapsearch -x -LLL -h DC01 -D crm.test -w *** -b "CN=Customer R Manager,OU=DFM Systems Accounts,DC=dfm,DC=ae" -s sub "(objectClass=user)" givenName
It showed me the message:
Cannot connect to the LDAP server
Do you have ping to your host (DC01)?
If not, maybe you can check with the customer what is the correct host?
Yup even tried ping DC01
ping: unknown host DC01
I suggest you verify with the customer the correct host
Yes verified and again customer gave the wrong credentials...
Looks like DC01 is not a known host in neither your configured DNS server nor the local hosts file. Make sure the hostname is resolvable, or use the IP address of the AD server instead.
Thanks Mostafa...yup DC01 was not resolvable. Used IP address and it worked.
Thank You again
Could you please confirm the Hostname? i guess, DC01 is not correct host. becuase if it would have been issue with username / password issue, it would have given you "invalid credential issue", but here its not. Please check your hostname, and re-try, thanks!
Hello Hemant,
yes DC01 is not the correct host.. Used IP address and also credentials provided were also not correct.
Now everything resolved.
Thank YOU
You could try pinging by IP. You can check the DNS on most systems using nslookup <name> where the name should match the FQDN.
Hi Mayanka,
Using the same user credentials (username and password), try to connect to that host outside of Aveksa.
You can download and install Apache Directory Studio to test it.
If it does work there as well, it might be that you are using incorrect credentials or the host is not correct.
If it works, it might be a secure connection that must be establish, and for that, you will have to install an SSL certificate in your Aveksa server to make the handshake with the host certificate. Also, that will require to use a different port, from 389 to 636
Regards
Armel Lupapi
Using the same credentials as in your screenshot, were you able to connect successfully using an AD browser (e.g. Apache Directory Studio)?