During large transfers BPFTP times-out and the transfer fails.
u may be using BPFTP through some sort of NAT server/proxy. In such cases with large file transfers what is happening is the control connection is not being used for a really long time, so the NAT server decides its no longer needed, and removes it from its table -- it doesnt close it at the client end or the server end, it merely forgets the link between the 2 so that the server & client can no longer communicate. The transfer still continues as before, there's only a problem when the transfer finishes and the server tries to tell BPFTP that it has finished -- it can't. There are a couple of ways to resolve the problem: #1) increase the timeout on the NAT server to at least 1 hr, or however long it takes to transfer the biggest file. #2) use BPFTP's workaround, enable "firewall keep alive". This can cause problems with some servers though, however it will prod the NAT server periodically to keep the connection alive.
During large transfers BPFTP times-out and the transfer fails.
u may be using BPFTP through some sort of NAT server/proxy. In such cases with large file transfers what is happening is the control connection is not being used for a really long time, so the NAT server decides its no longer needed, and removes it from its table -- it doesnt close it at the client end or the server end, it merely forgets the link between the 2 so that the server & client can no longer communicate. The transfer still continues as before, there's only a problem when the transfer finishes and the server tries to tell BPFTP that it has finished -- it can't. There are a couple of ways to resolve the problem: #1) increase the timeout on the NAT server to at least 1 hr, or however long it takes to transfer the biggest file. #2) use BPFTP's workaround, enable "firewall keep alive". This can cause problems with some servers though, however it will prod the NAT server periodically to keep the connection alive.