AD connection not working

HI All,

I am trying to connect to Active Directory but getting timeout error.

I have checked network connection, I am able to connect AD server from VA. I am also using AD server IP to connect and also i have checked AD server is up and running. I have also increased the timeout settings but still getting same error.

Any help on this will be appreciated.

Thanks,
Nikhlesh

Hi @nikhlesh21

Please check below topic solution, it seems similar to your error.

Timeout Error When Connecting SailPointNow to Active Directory

Hi @nikhlesh21 ,

Is your AD connection is through the IQService server or not, if it is through IQService server then check it is up or not.

You can also check you VA CCG Version in the cluster.

restart iqserver and then check test connection also have you validated certs as well?

As I said, I am already using AD IP server connect.

No, I have removed IQ service details to test the connection. Also, ccg version is also available.

Not using the IQ service and I am connecting on port 389.

Just to add, I was able to connect earlier but now we have to redeploy the VA since then not able to connect to any app through VA. Although network connection is fine and VA is connected with CCG version available.

hi Once you have redeployed VA you have to reconfigure the username, password. Did you try updating them and see?

Tried to update the VA password with default sailpoint as username, still same error.

I did not mean VA username and password. I meant on the AD source

any logs please? to check it

AD is now connected, I am not sure how but last action I did was to update the password of VA and configure VA again with ISC. Although at that time it was not connected but now it is.

You mean, if we reconfigure the VA then we need to update the AD service account username/password?

So, you updated VA username and password and reconfigured that in ISC and AD connection is working? May be you did not update it earlier and it caused the problem. I was asking to reenter the password in your AD source.

Not sure if that resolved it but that was last thing i did.

AD username pwd i had updated in source multiple times and also i changed the VA cluster once as well but nothing worked.

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.