Re: File Transfers

On Thu, Jan 13, 2005 at 08:37:53AM -0700, Peter Millard wrote:
> ----- Original Message -----
> From: "Marc Lewis" <[email protected]>
> > Transfers work if both clients are set to manually use the proxy server in
> > Exodus.  If, however, Exodus is set to discover the proxy server from the
> > server, the transfer sort of starts but doesn't actually work.  The sender
> > starts sending data out until the proxy server's recieve queue is full, and
> > the recieving client says the transfer is complete immediately.  The result
> > is a hung sending client and the reciever has a zero length file.
> 
> Using auto-discover vs. manual just determines whether or not the proxy is
> discovered by disco'ing the server or not. In manual mode, Exodus always
> uses the jid specified in the options dialog. This shouldn't matter once the
> transfer starts. Could this be a network problem timing out connections for
> some reason? It sounds like bytes just stop (which I've never seen before).
> 
> pgm.

I'm sure its not a network timeout.  I just double checked and tested my
theory against jabber.org.  Using the same configuration, two clients
behind two different NAT routers on two different subnets, both set to
auto-discover the file transfer transport.

They both seem to discover the Jabber.org proxy server.  The sender starts
its transfer, gets about 64K of the file sent and hangs.  The reciever
starts the transfer and then immediately says the transfer is complete and
gives the option to open the file or close the window.  The file that was
recieved is 0 bytes long.

It really appears to be a bug in Exodus.  This is v0.9.0.0 on both sides,
one computer is running Windows 2000 Pro SP4, and the other is running XP Home
SP1.

 - Marc

-- 
Marc Lewis
Network Administrator
Blarg! Online Services, Inc.
http://www.blarg.net/~marc