Opened 14 years ago

Closed 12 years ago

Last modified 6 years ago

#958 closed Bug report (outdated)

Strange Timeouts after login

Reported by: marcecj Owned by:
Priority: normal Component: FileZilla Client
Keywords: Cc: marcecj, peleiades, bugreports, gblightyear, blacksnownight
Component version: Operating system type:
Operating system version:

Description

I've been using FileZilla for a while, but early this
year (March or so), during the same version (2.12/13),
I believe, I started getting problems with sudden,
unexpected timeouts.

It usually happened right after I logged in and did
something (like create a new folder, move a file or
switch to a different folder). I also got timeouts
during uploads, always when FileZilla sent the
keep-connection-alive-comands.

I uploaded two files, each with a different example
from the log window.

I hope I'm not repeating a bug, but none of the titles
I looked at resembled anything I encountered (they are
often vague, anyway, like 'buggy upload' and such...).

Attachments (2)

log_new.txt (2.9 KB) - added by marcecj 14 years ago.
Log form today (30. Sept. 2005)
log_old.txt (3.9 KB) - added by marcecj 14 years ago.
Log from several months ago

Download all attachments as: .zip

Change History (10)

Changed 14 years ago by marcecj

Attachment: log_new.txt added

Log form today (30. Sept. 2005)

Changed 14 years ago by marcecj

Attachment: log_old.txt added

Log from several months ago

comment:1 Changed 14 years ago by marcecj

Sorry, I forgot to mention I tried it with 2.16 and it still
happens.

comment:2 Changed 14 years ago by marcecj

And yes, I contacted the server admin (at least I think he's
admin) and he just keeps telling me to use other software.

comment:3 Changed 12 years ago by peleiades

I am having similar problems since moving to 3.0.1. The timeouts occur on various servers, and do not occur on my other machine running a 2.x version of FileZilla client. Please advise if this is being looked at and/or fixed sometime soon. Thank you, Peleiades

comment:4 Changed 12 years ago by bugreports

Same problem here since moving from 2.2.32 to 3.0.3

comment:5 Changed 12 years ago by gblightyear

My Experience:
login via server manager
Navigate through Server File system
after changing directory to 1st, 2nd, max. 3rd level, the connection stops while calculating time difference.

Status: Berechne Zeitzonenabweichung des Servers...
Befehl: MDTM SyncToyDirectoryId.txt

[Language German]
The only way to cancel this is to cancel the connection to the server and connect again. Then it's passing all levels and transfers without hanging.

Now I found settings for more informations in the logging. Next Time this happens I have more infos.
Regards

comment:6 Changed 12 years ago by gblightyear

My Experience:
login via server manager
Navigate through Server File system
after changing directory to 1st, 2nd, max. 3rd level, the connection stops while calculating time difference.

Status: Berechne Zeitzonenabweichung des Servers...
Befehl: MDTM SyncToyDirectoryId.txt

[Language German]
The only way to cancel this is to cancel the connection to the server and connect again. Then it's passing all levels and transfers without hanging.

Version: 3.0.9.2, same problem with old Version 3.0.8.1
Now I found settings for more informations in the logging. Next Time this happens I have more infos.
Regards

comment:7 Changed 12 years ago by blacksnownight

Same problem here.

Example
Status: Resolving address of blacksnownight.de
Status: Connecting to 82.210.20.13:21...
Status: Verbindung hergestellt, warte auf Willkommensnachricht... (Conected Waiting for Welcomemessage)
[LAG for about 10 Seconds]

But when I connect via Telnet or CMD FTP it also waits about 10 Seconds for 220 Message from the Server.
So this could also be a bug of the Server and not of the Client.
I also experienced this on a few other servers. Maybe a spread Serverprogramm causes this bug.

comment:8 Changed 12 years ago by Tim Kosse

Resolution: outdated
Status: newclosed

If original issue still happens with 3.x, it is definitely caused by a broken server or a malicious router or firewall.

Note: See TracTickets for help on using tickets.