On Sat, 19 Feb 2005 11:26:16 +0000, Jonathan Share <[EMAIL PROTECTED]> wrote: > On Fri, 18 Feb 2005 22:43:50 -0600 (CST), Steven M. Schweda > <[EMAIL PROTECTED]> wrote:
> > > My best guess is that it is failing to open the tcp connection but > > > looking for a more specific answer if possible. > > > > The "seconds 0.00," message seems to come from run_with_timeout() in > > MSWINDOWS.C, so it's a Windows-specific thing (with which I have no > > experience), but it looks a little like you might (somehow) be > > specifying a time limit of zero seconds, which may not be enough time > > for the connection to form (or for anything else, for that matter). > > > > Is this of any help?: > > > > -T, --timeout=SECONDS set all timeout values to SECONDS.\n\ > > I'll try it and see what happens. > I'm still waiting for some new data from my client after adding the timeout parameter to my script but I have been thinking....could these symptoms be caused by an iptables entry DROPing the incoming packets? Thanks Jon > > > > This advice may not be worth much, but the price is reasonable. > > > > Any advice is greatly appreciated this issue is baffling us. > > Thanks, > Jon > > > ------------------------------------------------------------------------ > > > > Steven M. Schweda (+1) 651-699-9818 > > 382 South Warwick Street [EMAIL PROTECTED] > > Saint Paul MN 55105-2547 > > > > ------------------------------------------------------------------------ >
