Xu, Qiang (FXSGSC) wrote:
13.198.97.16 is a working AD that can answer LDAP bind/search requests. 13.198.98.16 is just another PC, but not an AD. In order to simulate the network down situation, the LDAP server is intentionally pointed to the wrong one, 13.198.98.16, and that causes a blocking effect.
i'm sure i understand how are you trying to simulate network down situation pointing your client to a different server/host. is the 13.198.98.16 host down ? if it is up and running check if it has the port you are connecting to [ eg 389 ] open.
The problem is, even I set a timeout value with ldap_result(), it still doesn't work. ldap_simple_bind() behaves almost the same as ldap_simple_bind_s(). :-(
async bind has two stages where it can block. the first one when connect() is in progress and the second one when its writing the bind request itself to that connection. _______________________________________________ dev-tech-ldap mailing list [email protected] https://lists.mozilla.org/listinfo/dev-tech-ldap
