RE: timeout on ldap_simple_bind_s()

> -----Original Message-----
> From: [email protected] [mailto:[email protected]] 
> Sent: Friday, September 11, 2009 5:37 PM
> To: Xu, Qiang (FXSGSC)
> Cc: [email protected]
> Subject: Re: timeout on ldap_simple_bind_s()
> 
> 
> 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.

From the following command: 
======================================================
C:\Documents and Settings\Administrator>netstat -an |find /i "listening"
  TCP    0.0.0.0:21             0.0.0.0:0              LISTENING
  TCP    0.0.0.0:135            0.0.0.0:0              LISTENING
  TCP    0.0.0.0:445            0.0.0.0:0              LISTENING
  TCP    0.0.0.0:1027           0.0.0.0:0              LISTENING
  TCP    13.198.98.16:139       0.0.0.0:0              LISTENING
  TCP    127.0.0.1:1039         0.0.0.0:0              LISTENING
  TCP    127.0.0.1:14147        0.0.0.0:0              LISTENING
  TCP    [::]:135               [::]:0                 LISTENING       0
  TCP    [::]:445               [::]:0                 LISTENING       0
  TCP    [::]:1027              [::]:0                 LISTENING       0
======================================================
It is confirmed that port 389 is not open.

> 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.

So, in this case, can you explain why ldap_simple_bind() still blocks? Isn't there a way to unblock it?

Thanks,
Xu Qiang