Re: timeout on ldap_simple_bind_s()

Xu, Qiang (FXSGSC) wrote:
> Yes, 13.198.98.16 (Windows XP) is up and running. But how to check whether the port 389 is open? Any command to do this in Windows XP?

no idea, i dont use xp. cmd.exe then netstat maybe ?

>> 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, are you implying that if the server's port 389 is not open, the async bind would also block? Very probably, port 389 in 13.198.98.16 is closed, so what situation does the code fall into, in this case?

no i'm not implying that at all. if the host is reachable and the
port is closed connect() should fail very fast and you shouldnt
be getting a timeout.