It sounds like you've narrowed it down a fair bit -- and that your problem isn't really FTP, if your observations actually match reality. (Always a concern...so much time wasted...shudder...)
Are we talking about a TCP/IP timeout exception? That won't be affected by delays in crypto, etc. That would indicate a loss of TCP/ IP connectivity. If your data connection is in state ESTABLISHED, then it's not a connection timeout. If it's not an application-level timeout (which I don't recall FTP having, but it's been a while), then it would mean that nothing is getting through -- perhaps a NAT or firewall issue? I've seen NAT/Firewall issues block data connections even for passive FTP, though I don't know just how. I really hesitate to suggest it, but maybe you want to use a tool like tcpdump? It should at least help narrow down the problem. On Feb 3, 2:52 pm, mericksonj <mericks...@gmail.com> wrote: > @Ryu > I am using runFTP from the market place as well as andFTP, droidFTP, > Padersync, and esfile explorer. All show the same syptoms from the > FTP server point of view, but give different error messages in andoid > if they don't just hang there frozen. > > @Bob > Thanks for the replies Bob! > > FTP is the protocol of choice for many, many, reasons, and I know the > SSH port forwarding works where PC clients are able to connect > properly. I admit it is not elegant, but it works with commonly > available (read: free) server and client software, and meets my > security requirements. > > I do rely on passive mode FTP data transfers so that the client > doesn't need to start a listener, but the server is only configured to > allow one (or few) TCP port option (all FTP passive replies have the > same IP/PORT) to establish the data connection that will be encrypted > as well. > > The FTP server is logging debug messages and it does show the data > connection is open (netstat on both the server and android EMU also > show an established TCP connection). > > I do believe that it is close to working on android, except that > something lags (possibly due to the delay with crypto processes) and > then the timeout exception occurs, but I don't know enough aobut the > DALVIKVM or the client software to look into it deeper myself. > > If you can point me at additional tools I can use to further > troubleshoot I would appreciate it. > > Thanks! > --James -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
