LDAP response read timed out : Issue

Deepak Ingale1 · ‎08-11-2015

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.

Deepak Ingale1 · ‎08-14-2015

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.

View solution in original post

shashankjoshi · ‎08-11-2015

This is seems to be customized error code

but unfortunately no further info.is available on wiki.

i guess this is not servienow issue. check the settings in active directory. and ask active directory admins to change the setting as below

Go to Administration > Users > User Directories
Edit the LDAP directory
Increase the value of Read Timeout

just give it a try...

Regards,

Shashank J

Deepak Ingale1 · ‎08-11-2015

Hello Everyone,

Kindly provide some info if any one knows about this issue.

bernyalvarado · ‎08-11-2015

Hi Deepak, here goes some thoughts of things you will like to check:

a) Just to isolate the troubleshooting scope... try to establish the connection and browse through your LDAP without using any attributes and/or filters

b) Make sure that your Login Distinguished Name user is correctly setup. I always recommend using a user's distinguished qualified name

c) Make sure that the user you're using to connect has read access in the LDAP Server

d) Make sure that the Starting Directory is correctly setup

e) Make sure your server is accessible by doing a ping using the LDAP port in use

I hope this is helpful!

Thanks,

Berny

Deepak Ingale1 · ‎08-11-2015

Hi Berny,

Thank you for suggestions.

I will follow those steps and will keep you posted about the progress.

I already had asked for issue to check from AD team since before getting those errors, there was a another error code 49 - Invalid credentials was submitted by system. So I suspect there might be an issue with account password / expiry / lockout or firewall.