How to avoid 421 Connection closed, timed out?

[newcyberian]

We are a CD/DVD replication company and we use filezilla intensively for uploading disc image files to our manufacturing plant. But we always got the 421 Connection closed, time out and then the Error: Disconnected from server error messages, even the uploading status bars are still moving.

Is there a way to set the time out much longer, say forever?

Thanks in advanced!

[botg]

This message comes from the server. Please contact the server administrator and ask him to configure the server in a more sane way.

[newcyberian]

Thanks for the hint.

But if we use command line we never see the message. Of course the down side of command line is we cannot see the uploading speed. Using IE by dragging the file over would not have the problem either.

The funny thing is even it said the connection had been disconnected, but the uploading process was still going on until it was completed.

[botg]

Transfer and browsing connections are independent.

[boco]

I'm pretty much sure commandline uses only the primary connection, thus it doesn't time out. IE may do the same.

[Virgi]

hi

i've the same problem.

i've not understood how i can leave it.

sorry for my bad english but i'm italian.

Before Filezilla, i used anothere ftp transfer software and i hadn't this problem, so it is not a server problem. Even because i've 3 sites in different servers and i've the same problem in every one.

Bye!

[Virgi]

some help?

[boco]

some help?

Try to enable keep-alive. Settings...-Connection-FTP-Send FTP keep-alive commands.

[Virgi]

thank you but i have the same problem.

After 600 seconds, it time out.

[boco]

If it's a No-transfer timeout keep-alive doesn't work. Transfer a file within the 600 seconds and the timeout should be reset.

edit: No that doesn't work, as Filezilla uses secondary connections for the transfers.

[bognorphotographer]

Command: STOR royalfestivalhallsamkemp.mov
Response: 150 Opening BINARY mode data connection for royalfestivalhallsamkemp.mov.
Response: 421 Connection timed out - closing.
Error: Connection closed by server
Status: Resolving address of nycftp.gettyimages.com
Status: Connecting to 206.28.73.49:21...
Status: Connection established, waiting for welcome message...
Response: 220 Serv-U FTP Server v5.2 for WinSock ready...
Command: USER footage
Response: 331 User name okay, need password.
Command: PASS **********
Response: 230 User logged in, proceed.
Status: Connected
Response: 421 Connection timed out - closing.
Error: Connection closed by server




Why is this happening?, have tried both active a passive get this message,
Connecting to probe.filezilla-project.org

Response: 220 FZ router and firewall tester ready

USER FileZilla

Response: 331 Give any password.

PASS 3.5.3

Response: 230 logged on.

Checking for correct external IP address

IP 92.20.74.86 jc-ca-he-ig

Response: 200 OK

PREP 6311

Response: 200 Using port 6311, data token 1285734554

PORT 92,20,74,86,24,167

Connection lost

Connection closed

[boco]

First: Never hijack others' threads, especially if they are very old (4 years in this case).

The 421 timeout does not affect transfers normally. You see that on servers with a ridiculously low timeout value set (Yes, it's not a bug, it's a feature). You should be able to see a pattern if you enable timestamped logs in the settings.

There are two levels:
1. Idle timeout. You can counter this one by enabling keep-alive in FileZilla settings. However, since FileZilla automatically reconnects on the next action, keep-alive shouldn't be required.

2. No-transfer timeout. This one is only reset through a transfer. Since FileZilla never does transfers on the browsing connection, there's no way of preventing that type of timeout. The only action preventing it may be retrieving a directory listing.