Custom Query (8117 matches)

I was working fine with just the previous versión of filezilla as son as I have updated to this last version 3.9.0.2 I start to get get next error: receiving a directory list it fails by timeout. the server is working well the failure happens in different directories ramdomly, that is, sometimes it Works fine in directory aaaa but other times not

it Works fine using regular commands from a cmd window

I have observed the same problemin an old versión but it was fixed in last versions (sorry that I can not be more precise)

Estado: Conectando a 213.165.71.109:21... Estado: Conexión establecida, esperando el mensaje de bienvenida... Respuesta: 220-FileZilla Server version 0.9.34 beta Respuesta: 220-written by Tim Kosse (Tim.Kosse@…) Respuesta: 220 Please visit ​http://sourceforge.net/projects/filezilla/ Comando: USER ftpuser Respuesta: 331 Password required for ftpuser Comando: PASS * Respuesta: 230 Logged on Comando: SYST Respuesta: 215 UNIX emulated by FileZilla Comando: FEAT Respuesta: 211-Features: Respuesta: MDTM Respuesta: REST STREAM Respuesta: SIZE Respuesta: MLST type*;size*;modify*; Respuesta: MLSD Respuesta: UTF8 Respuesta: CLNT Respuesta: MFMT Respuesta: 211 End Estado: Conectado Estado: Recuperando el listado del directorio... Comando: CWD /SoftwareRecibido Respuesta: 550 CWD failed. "/SoftwareRecibido": directory not found. Comando: PWD Respuesta: 257 "/" is current directory. Comando: TYPE I Respuesta: 200 Type set to I Comando: PORT 192,168,1,35,62,225 Respuesta: 200 Port command successful Comando: MLSD Respuesta: 150 Opening data channel for directory list. Respuesta: 226 Transfer OK Estado: Directorio listado correctamente Estado: Recuperando el listado del directorio... Comando: CWD TauroPlatform Respuesta: 250 CWD successful. "/TauroPlatform" is current directory. Comando: PWD Respuesta: 257 "/TauroPlatform" is current directory. Comando: PORT 192,168,1,35,62,249 Respuesta: 200 Port command successful Comando: MLSD Respuesta: 150 Opening data channel for directory list. Respuesta: 226 Transfer OK Error: Conexión superó el tiempo de espera Error: Error al recuperar el listado del directorio

We have a virus scanning proxy here. Upon download, it will fetch the file, scan it and then transfer it to FTP client.

While the file is fetched, the FTP client doesn't see anything. This triggers a timeout. FileZilla has a maximum timeout of 999 seconds. For files of several hundred megabytes or slow FTP servers, this timeout is too low.

A workaround is to set the timeout not via the settings GUI dialog, but change it directly in the filezilla.xml config file.

Please remove the artificial limit of 999 seconds when conguring the timeout via GUI allow to disable timeout completely. I understand that under normal circumstances having timeouts is good and 999 is unresonalby high. But we have special circumstances here. Thank you.

The user successfully logs in. But then, nothing... the directory listing cannot be retrieved... the timeout is reached.

When this happens, in addition to the messages that are already being displayed in the status log textarea at the top of the application, the end-user should get a pop-up with information.

The pop-up should say something about transfer modes, and it should say that the firewall of the server may be blocking incoming connections.

The well-known CSF firewall that almost everyone uses with WHM/​cPanel installs has a TCP_IN that does not include the 30000:50000 range.

FileZilla is such a well-known client that, again and again, our customers kept running into this issue. We've been telling them for years to use WinSCP and to avoid FileZilla. I've personally told many customers to avoid FileZilla because it doesn't work properly. Clearly, WinSCP can do something that FileZilla cannot.

You have to make sure that end-users understand what's going on, and that they can ask their server administrator to open that TCP_IN port range.

Even if - hypothetically - what I'm writing above is nonsense, and I don't understand FTP or passive/active modes at all, there's still a problem. I'm the system administrator of several servers with up to a thousands accounts. Only today I figured out I can "fix" FileZilla for customers by changing CSF settings. If only the first FileZilla end-user who contacted me could've told me.