On Wednesday, 07/02/2008 at 07:05 EDT, "Schuh, Richard" <[EMAIL PROTECTED]> wrote: > Thanks for the tip. I will give it a try.
Not "PASV". That's the name of the verb that flows. You want "passive" (applying only to the VM FTP client). If you're using some other client, check its documentation. But I don't think it will help. If a firewall is going to block a data transfer, it does it at the the beginning, not the end, of the session. I, too, suspect that the control connection was idle for too long and the firewall or the remote server got upset. The fix is to lengthen the maximum idle time in the firewall or server. (The VM FTP server has a default of 300 seconds.) If it's killing a control connection that has an active data connection associated with it, that would be a bug. Note that that does not prevent a firewall from having its own idle session detection. The only solution to *that* problem is for the FTP server to send "progress" messages (intermediate results) every n seconds or m bytes. Alan Altmark z/VM Development IBM Endicott
