- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎08-11-2015 12:34 AM
Hello,
We have received "LDAP response read timed out" message from one of the LDAP integration we have done.
When we tried to connect to server manually (Connection test), alternatively it is giving message 'Connection Successful" and 'LDAP response read timed out".
Can someone suggest anything on this case?
Note: We are not using SSL and below are our properties set currently.
Also we are not able to browse through the LDAP directory as well when message shows 'connection succesfull"
Berny Alvarado, Mike Allen, Pradeep Sharma , Mark Stanger , Brad Tilton (Cloud Sherpas)
Your help is appreciated.
Solved! Go to Solution.
- Labels:
-
Integrations
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎08-14-2015 07:22 AM
Hello Berny,
Here is the resolution of the case.
There was an issue with one of the Domain Controller, it was in hung state.
Also, DCs were in load balancing state, hence alternate connection and failure message were being received.
Now issue has been solved, thank to Joao Rodrigues who had suggested and worked on HI support case we registered.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎08-11-2015 08:51 AM
You're welcome Deepak!
Yeah, often if you're getting an "Invalid credentials" is truly because the password entered is incorrect. When in appearance you can establish a connection but you cannot browse through the LDAP structure it's often because of the privileges of the account or because the Starting Directory was not correctly set.
Indeed, let me know how it goes.
Take care buddy!
Thanks,
Berny
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎08-11-2015 10:39 AM
Hi Berny,
We had implemented this integration 5 months ago and it was working nice till yesterday night.
All of a sudden, the first error code which got registered in the system was 49 (invalid credentials) and then started the series of error code 10000. So even I suspect the issue might be with account only.
Anyways, I tried with the first step of yours but dint worked (remove attibutes / filters). So currently I am waiting for a response from AD team only before I jump on to next steps of troubleshooting.
I will surely keep posted on this. Seems a weird issue for me (Alternate success and failure).
Have a nice time ahead friend.
Thanks
Deepak
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎08-14-2015 07:22 AM
Hello Berny,
Here is the resolution of the case.
There was an issue with one of the Domain Controller, it was in hung state.
Also, DCs were in load balancing state, hence alternate connection and failure message were being received.
Now issue has been solved, thank to Joao Rodrigues who had suggested and worked on HI support case we registered.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎08-14-2015 07:26 AM
Awesome! Thanks for sharing the root cause and how it was solved.
Thanks,
Berny