|Subject:||Re: Timeout with Connect|
|Posted by:||Remy Lebeau (TeamB) (firstname.lastname@example.org)|
|Date:||Fri, 7 Nov 2003|
"Marcus Mönnig" <usenet-november…@40tude.com> wrote in message
> Anyone has any ideas how this could possibly happen?
You're receiving a WinSock timeout, not an Indy timeout. WinSock itself has
its own internal timeouts. Asking Indy to wait 120 seconds is being pretty
generous, WinSock will usually time itself out long before then.
Timeout with Connect posted by Marcus Mönnig on Fri, 7 Nov 2003