Filezilla disconnects, cuteFTP doesn't; same router-why?

[khopek]

I suggest a quick poll of readers of this thread. If you're on the current version of Filezilla (3.0.11) and you have another ftp client available on the same machine do you:

a) experience persistent connection with Filezilla.
b) experience automatic disconnect after a few minutes with Filezilla but no disconnect with alternate ftp program
c) experience automatic disconnect after a few minutes with both Filezilla and with your alternate ftp
program
d) experience something else (fill in the blank) ___________________________________________________________

please mention your OS and machine type

cu

I don't have another ftp client but...
I have three different machines I use on a daily basis:
1. Dell Vostro w/ Windows XP Home
2. Dell Dimension 3000 w/ Windows XP Professional
3. Compaq Presario Laptop w/ Windows Vista

I have 2 different hosts I connect to and
a) persistent connection only with v2.2.29
b) 'status: Disconnected From Server' message after file transfer and a few minutes later 'error: Disconnected From Server' message.(v3.0.11 only).
c)n/a but as I'm doing this I've had both versions open and v2.2.29 is still connected while v3.0.11 has disconnected 4 times.

P.S. I DID go to my first host as my first attempt to get things fixed naturally assuming it was them...

[botg]

Set debug mode to three in the settings. If you see "Trace: CRealControlSocket::OnClose()" in the message log, it is definitely not FileZilla's fault.

[kmoth]

The only difference with FileZilla 3 and other clients is the usage of keepalive commands, which are just bandwidth hogs, they are not needed on proper servers, routers and firewalls. Fix your servers, routers and firewalls, I will not waste any effort with broken third party components.

look at you! you answered a question with a logical explanation.
i'm proud of you man. you've come a long way!

k.

[khopek]

Set debug mode to three in the settings. If you see "Trace: CRealControlSocket::OnClose()" in the message log, it is definitely not FileZilla's fault.

Okay. This is what I have from the File Transfer to the 'status: Disconnected From Server'...

Response: 226-File successfully transferred
Response: 226 0.000 seconds (measured here), 260.60 Mbytes per second
Trace: CFtpControlSocket::TransferParseResponse()
Trace: CFtpControlSocket::SendNextCommand()
Trace: CFtpControlSocket::TransferSend()
Trace: CTransferSocket::OnClose
Trace: CTransferSocket::TransferEnd(1)
Trace: CFtpControlSocket::TransferEnd()
Trace: CFtpControlSocket::ResetOperation(0)
Trace: CControlSocket::ResetOperation(0)
Trace: CFtpControlSocket::ParseSubcommandResult(0)
Trace: FileTransferSubcommandResult()
Trace: CFtpControlSocket::ResetOperation(0)
Trace: CControlSocket::ResetOperation(0)
Status: File transfer successful
Status: Disconnected from server
Trace: CFtpControlSocket::ResetOperation(66)
Trace: CControlSocket::ResetOperation(66)

[botg]

Your log seems truncated at the end. A couple of more lines in the beginning would be helpful as well.

[khopek]

Your log seems truncated at the end. A couple of more lines in the beginning would be helpful as well.

Nope that was all of it...untill I got the 'error: Disconnected From Server' then I got two more lines, one being the one you mentioned...

p.s. Disconnecting isn't as frequent today as it has been up until yesterday, but I'm still not exactly sure what I should do to fix it. My one host just moved me to a new server (for many unrelated issues), for about the 4th time, but they don't think there is a problem...

[JakeS]

Hey guys, you know. I don't think it's filezilla's fault. I've just checked my filezilla which I kinda left connected to a server since I compiled FileZilla on my linux. I just checked it. it's not had one disconnection since I connected it. which to me. tells me that it's something you guys either configured wrong. or the server is disconnecting you. by the way, you know it's possible cuteFTP could be automatically re-connecting you without telling you? I've never used cuteFTP however. but it's possible.

I'm with botg on this one. it is not filezilla's fault. btw build date of my filezilla: 2008-06-16

also. guys. try telling filezilla to use keep alive commands. which is what cuteFTP could be doing without telling you.

Settings > Connection > FTP > Send Keep Alive Commands

Although I don't have this enabled. but some servers need it otherwise They will automatically disconnect you from the server at a set time which the server is configured to disconnect you.

Anywho enough said.

~Cya

[boco]

Yeah, but even keep-alive does not save you from No-transfer-timeouts, because that timer is only reset if you actually transfer a file. Now listen: Filezilla 3 does never ever use the browsing connection for any transfers (unless you set the connection limit in the Site Manager to 1). Filezilla 2 had a feature to transfer files smaller than n bytes (1024 by default) on the browsing connection. That could be the reason why v2 stays connected while transferring files, Filezilla 3's browsing connection is truly idle.

Maybe it would be possible to 'rotate' connections, e. g. when a transfer finishes the browsing connection is changed to a data connection, and the data connection (which just finished transferring a file) to the new browsing connection (with fresh timer). Of course that wouldn't be helpful with large transfers taking a lot of time, but for the casual transfer of small-ish files.

[kylegetsspam]

The problem is, however, that while most routers and firewalls may not be configured properly, most of the time there's nothing you can do about it. I work at a small webdev company and FileZilla 3.0+ will disconnect from all the client servers I've used thus far after a few minutes. Whether or not it's FileZilla's or the server's fault is not the issue -- what really matters is that it's highly frustrating and unfixable in most cases.

I, too, have experienced what many have in this thread. Same computer and same server yet older versions of FileZilla (2.2.32 is what I used, I believe) will remain connected for a looong time. An hour or more from what I've experienced. Like someone else said earlier, I don't know how long it'll stay connected because I've never been disconnected. 3.0+ will disconnect some 10 to 15 times in the span of an hour. I've also experienced this on my home machine on various servers. 3.0+ has simply refused to stay connected to every server I've ever used.

For me this is unacceptable. I can't control other company's hardware and software setups, so I use what remains connected. In this case, all of 3.0+'s new features and fixes are made null and void by its inability to remain connected... whatever the cause. Like I said, it doesn't matter why this happens; it only matters that it happens at all and it's really, really annoying.

My $0.02.

[boco]

Tried the 'keepalive' feature yet?

[da chicken]

I think you're missing what botg's asking for. Part of what upset him was the semantics of "filezilla disconnects" and "filezilla gets disconnected" which, well, he didn't handle all that well. The difference is subtle to anybody who isn't in networking, and he got angry instead of making it clear what he meant. (IMO)

If you have a problem and it's repeatable, set your diagnostics to level 3 and post the full logs. If you have errors, *post some information about them*. Don't just say "OMG IT'S BORKEN FIX IT PLZ". What is the make and model of your network hardware? What OS servers are you connecting to? What FTP daemon? Is it FTP? SFTP? Did it just start with v3.0.11? Was 3.0.10 just fine? What about the most recent nightly? Fire up a network capture program and watch what happens to the packets when the connection dies.

If he can't repeat the error, then there is no error. If there is no error, he can't fix it. If he can't fix it, then it's not his problem.

[boco]

If he can't repeat the error, then there is no error. If there is no error, he can't fix it. If he can't fix it, then it's not his problem.

This is true for about 90% of the posts here.

[borbely]

I'm very grateful for this program (thank you, developer!!).

I am still using v2.2.18. Last week installed the newest version on a computer I was using temporarily and got frustrated because I kept getting disconnected by my server, after just a few minutes idle time.

In case it helps folks trying to adjust settings on the NEW version, here's what FileZilla says under File-->Settings-->Connection, by default, in v2.2.18:

- Enable the Keep Alive System
- Send Keep Alive commands like "PWD", "REST 0", "TYPE A", "TYPE I" at random intervals between [15] and [30] seconds.
- Timeout Detection: If zero bytes are transfered within [30] seconds, assume that the connection timed out and disconnect.
- Retry Settings: When disconnected from server during transfer, wait [5] seconds between login attempts and try again up to [5] times.

Here's the log for just signing in and doing nothing for about 15 minutes. Looks like FileZilla is sending the Keep Alive commands, but my server knocks me off anyway after maybe 5 minutes. Then Filezilla reconnects me 5 more times -- so I get something like a 30-minute idle time.

Status: Connecting to fixourschools.net ...
Status: Connected with fixourschools.net. Waiting for welcome message...
Response: 220 ProFTPD 1.3.1 Server (ProFTPD) [216.35.196.59]
Command: USER howitis
Response: 331 Password required for howitis
Command: PASS ******
Response: 230 User howitis logged in
Command: FEAT
Response: 211-Features:
Response: MDTM
Response: AUTH TLS
Response: PBSZ
Response: PROT
Response: REST STREAM
Response: SIZE
Response: 211 End
Command: SYST
Response: 215 UNIX Type: L8
Status: Connected
Status: Retrieving directory listing...
Command: PWD
Response: 257 "/www/www" is the current directory
Command: CWD /www/www/COPydesk/
Response: 250 CWD command successful
Command: PWD
Response: 257 "/www/www/COPydesk" is the current directory
Command: TYPE A
Response: 200 Type set to A
Command: PASV
Response: 227 Entering Passive Mode (216,35,196,59,161,15).
Command: LIST
Response: 150 Opening ASCII mode data connection for file list
Response: 226 Transfer complete
Status: Directory listing successful
Command: REST 0
Response: 350 Restarting at 0. Send STORE or RETRIEVE to initiate transfer
Command: REST 0
Response: 350 Restarting at 0. Send STORE or RETRIEVE to initiate transfer
Command: TYPE A
Response: 200 Type set to A
Command: TYPE I
Response: 200 Type set to I
Command: PWD
Response: 257 "/www/www/COPydesk" is the current directory
Command: TYPE A
Response: 200 Type set to A
Command: REST 0
Response: 350 Restarting at 0. Send STORE or RETRIEVE to initiate transfer
Command: TYPE A
Response: 200 Type set to A
Command: TYPE A
Response: 200 Type set to A
Command: TYPE A
Response: 200 Type set to A
Command: TYPE A
Response: 200 Type set to A
Command: PWD
Response: 257 "/www/www/COPydesk" is the current directory
Command: PWD
Response: 257 "/www/www/COPydesk" is the current directory
Command: REST 0
Response: 350 Restarting at 0. Send STORE or RETRIEVE to initiate transfer
Error: Disconnected from server
Status: Waiting to retry... (5 retries left)
Status: Connecting to fixourschools.net ...
Status: Connected with fixourschools.net. Waiting for welcome message...
Response: 220 ProFTPD 1.3.1 Server (ProFTPD) [216.35.196.59]
Command: USER howitis
Response: 331 Password required for howitis
Command: PASS ******
Response: 230 User howitis logged in
Command: FEAT
Response: 211-Features:
Response: MDTM
Response: AUTH TLS
Response: PBSZ
Response: PROT
Response: REST STREAM
Response: SIZE
Response: 211 End
Command: SYST
Response: 215 UNIX Type: L8
Status: Connected
Command: TYPE I
Response: 200 Type set to I
Command: REST 0
Response: 350 Restarting at 0. Send STORE or RETRIEVE to initiate transfer
Command: REST 0
Response: 350 Restarting at 0. Send STORE or RETRIEVE to initiate transfer
Command: TYPE A
Response: 200 Type set to A
Command: TYPE A
Response: 200 Type set to A
Command: REST 0
Response: 350 Restarting at 0. Send STORE or RETRIEVE to initiate transfer
Command: TYPE A
Response: 200 Type set to A
Command: PWD
Response: 257 "/www/www" is the current directory
Command: PWD
Response: 257 "/www/www" is the current directory
Command: REST 0
Response: 350 Restarting at 0. Send STORE or RETRIEVE to initiate transfer
Command: TYPE I
Response: 200 Type set to I
Command: TYPE A
Response: 200 Type set to A
Command: REST 0
Response: 350 Restarting at 0. Send STORE or RETRIEVE to initiate transfer
Command: REST 0
Response: 350 Restarting at 0. Send STORE or RETRIEVE to initiate transfer
Response: 421 No transfer timeout (300 seconds): closing control connection
Error: Disconnected from server
Status: Waiting to retry... (4 retries left)
Status: Connecting to fixourschools.net ...
Status: Connected with fixourschools.net. Waiting for welcome message...
Response: 220 ProFTPD 1.3.1 Server (ProFTPD) [216.35.196.59]
Command: USER howitis
Response: 331 Password required for howitis
Command: PASS ******
Response: 230 User howitis logged in
Command: FEAT
Response: 211-Features:
Response: MDTM
Response: AUTH TLS
Response: PBSZ
Response: PROT
Response: REST STREAM
Response: SIZE
Response: 211 End
Command: SYST
Response: 215 UNIX Type: L8
Status: Connected
Command: TYPE I
Response: 200 Type set to I
Command: TYPE A
Response: 200 Type set to A
Command: TYPE I
Response: 200 Type set to I
Command: REST 0
Response: 350 Restarting at 0. Send STORE or RETRIEVE to initiate transfer
Command: TYPE I
Response: 200 Type set to I
Command: PWD
Response: 257 "/www/www" is the current directory
Command: TYPE I
Response: 200 Type set to I
Command: PWD
Response: 257 "/www/www" is the current directory
Command: REST 0
Response: 350 Restarting at 0. Send STORE or RETRIEVE to initiate transfer
Command: PWD
Response: 257 "/www/www" is the current directory
Command: TYPE I
Response: 200 Type set to I
Command: PWD
Response: 257 "/www/www" is the current directory
Command: TYPE A
Response: 200 Type set to A
Error: Disconnected from server
Status: Waiting to retry... (3 retries left)
Status: Connecting to fixourschools.net ...
Status: Connected with fixourschools.net. Waiting for welcome message...
Response: 220 ProFTPD 1.3.1 Server (ProFTPD) [216.35.196.59]
Command: USER howitis
Response: 331 Password required for howitis
Command: PASS ******
Response: 230 User howitis logged in
Command: FEAT
Response: 211-Features:
Response: MDTM
Response: AUTH TLS
Response: PBSZ
Response: PROT
Response: REST STREAM
Response: SIZE
Response: 211 End
Command: SYST
Response: 215 UNIX Type: L8
Status: Connected
Command: PWD
Response: 257 "/www/www" is the current directory
Command: PWD
Response: 257 "/www/www" is the current directory
Command: REST 0
Response: 350 Restarting at 0. Send STORE or RETRIEVE to initiate transfer

[boco]

Contact server admin and demand sane timeouts.

Filezilla 3 has keep-alive, look in the settings.

[novozhilov]

Programmer упрямец (Russian)
It would be easy for him to code more-efficient "unorthodox" way of keeping up connection, but he wants his program to be more clean and tidy It is only a pity if you have some poor poor hosting providers - and there are many.

For me, Filezilla now is unfortunately quite useless.
When I edit file outside the program and then want to upload it a bit later, must reconnect and change directory on server again.
Requires too much time.

I guess the lack of dirty keep-up connection is great loss for many users. But forget it

Пока!