misalignment in download queue

[snadir]

When I download a large number of files the queue is wrong. I used version 3.1.1.1.

The error occurs randomly in different files. In the image green entries are still correct, the red no longer!

[snadir]

Error in queue

[Tim Kosse]

What exactly do you mean by "no longer correct"?

[snadir]

as you can see on the picture, the green entries have the same path, on server and on pc.
in the red frame they have "spontaneously" postponed! the folder-structure is confused!
btw: I clicked the root-folder and "add to queue". the rest has made filezalla itselfs

btw2: sry for my bad english :-)

[Alexander Schuch]

The "to" and "from" directories do not match anymore. For "Einführung in das Übersetzen" directories, the subdirectory "WIN2000" is got added and the second item in the red border has a "DISK4" subdirectory removed.

[snadir]

exactly, and the second item is also in "Einführung in das Übersetzen", not in "Drucker". This night, I'll check it with an open FTP-Server, maybe it is reproducible.

[Tim Kosse]

Can you reliably reproduce the problem?

If you run the network configuration wizard, does the test at the end succeed?

[Tim Kosse]

Please try the upcoming 2008-08-19 build from ​http://filezilla-project.org/nightly.php

[snadir]

in build 2008-08-19 it's become worser,

as it's shown on screen, the bug begins with an entry, which is filled locally and not on the server

it is reproducible, but at moment only on this server (it's the closed ftp from my university, so i cannot give you access)

could a debug info helps you?

[Tim Kosse]

If you run the network configuration wizard, does the test at the end
succeed?

[snadir]

it's not successful:
Connecting to probe.filezilla-project.org
Response: 220 FZ router and firewall tester ready
USER FileZilla
Response: 331 Give any password.
PASS 3.1.1.1
Response: 230 logged on.
Checking for correct external IP address
Retrieving external IP address from ​http://ip.filezilla-project.org/ip.php
Checking for correct external IP address
IP 91.66.213.84 jb-gg-cbd-ie
Response: 200 OK
PREP 2184
Response: 200 Using port 2184, data token 1129251753
PORT 91,66,213,84,8,136
Response: 502 Port mismatch. Tainted by router or firewall.
PORT command tainted by router or firewall.
Connection closed

i try it with static ports and open them at my router and deactivated my firewall, but same error.

but this is only necessary for active connections, isn't it? data transfers from and to ftp-serer works fine, file listing too. so i don't understand the problem?! :-(

by the way: upnp in filezilla could be usefull! :-)

[Tim Kosse]

Some router or firewall is actively sabotaging the connection and most likely causing the queue mix-up.

[snadir]

in other words: you don't want to fix that or have no idea where the bug is?

until now i've tested it after 3 routers, netgear WNR834B, fritz!box 7170 and 3130. and one time without router. and the result is the same. do you mean, all these routers are "buggy"? but ony in combination with filezilla? i don't think so.

and i've tested the trial version of ws_ftp, there are maybe mandy bugs, but the downloadquere is correct.

is it quite difficult to double check an entry before adding it to quere?

greetings

[Tim Kosse]

There is no point in analyzing a complex problem if there's a malicious router or firewall that's actively sabotaging the connection.

Fortunately for you, somebody else has reported the same problem and his network configuration wizard test was successful. Try the latest nightly.

[snadir]

behind both fritz!boxes the test was successful, behind "no router", too. in this case, it couldn't depend on a "bad router"

firewall is offline, by the way. (when it's online it's KIS 2009, with "allow activities" for filezilla)

which build? the one which will come today or from yesterday?

[Tim Kosse]

The latest.

[snadir]

wonderful, it semms to bee fixed, congats!

would you explain me, where the bug came from? it woulb be interesting, if my router is buggy or not. and could you gife me the number of the other bug-report please?

thanks so far