Custom Query (8171 matches)

Filters
 
Or
 
  
 
Columns

Show under each result:


Results (532 - 534 of 8171)

Ticket Resolution Summary Owner Reporter
#811 Non repsonsive server Tim Kosse robske75
Description

When hammering the FTP server on a local host (127.0.0.1) with wrong logins, the server becomes non-responsive after 12 attempts. I see the '(not logged in)' text in the server log when a user logs on, but the server never returns the password prompt ans stalls for this connection completely.

Valid users cannot log on anymore as well.

#827 No FTP possible with MVS / z/OS ( HFS ) Tim Kosse jwinckelmann
Description

With FileZilla 2.2.12 and some older versions I'm unable to to transfer data to and from our z/OS mainframe with HFS file system. I think the directory is formatted incorrectly as it contains brackets which is not allowed, like '/u/test/(test.txt)'. It worked correctly with ealier versions of FileZilla, I don't know which version is the first version containing this errror. Here are some extracts of the log: Connecting to mvs2 ... Status: Connected with mvs2. Waiting for welcome message... Response: 220-FTPD1 IBM FTP CS V1R4 at MVS2, 13:33:22 on 2005-02-24. Response: 220 Connection will close if idle for more than 50 minutes. Command: USER xxxx Response: 331 Send password please. Command: PASS Response: 230 xxxx is logged on. Working directory is "xxxx". Command: FEAT Response: 211 no Extensions supported Command: SYST Response: 215 MVS is the operating system of this server. FTP Server is running on z/OS. Status: Connected Status: Retrieving directory listing... Command: CWD /u/ Response: 250 HFS directory /u/ is the current working directory Command: PWD Response: 257 "/u/" is the HFS working directory. Command: PORT xxx Response: 200 Port request OK. Command: TYPE A Response: 200 Representation type is Ascii NonPrint Command: LIST Response: 125 List started OK Response: 250 List completed successfully. Status: Directory listing successful Status: Retrieving directory listing... Command: CWD interaris Response: 250 HFS directory /u/interaris is the current working directory Command: PWD Response: 257 "/u/interaris" is the HFS working directory. Command: PORT xxx Response: 200 Port request OK. Status: Starting download of '/u/interisk(rias.wsdl)' Command: CWD '/u/interisk' Response: 250 HFS directory /u/interisk is the current working directory Command: PWD Response: 257 "/u/interisk" is the HFS working directory. Command: TYPE I Response: 200 Representation type is Image Command: PORT xxx Response: 200 Port request OK. Command: RETR '/u/interisk(rias.wsdl)' Response: 550 Command RETR fails: /u/interisk (rias.wsdl) does not exist. Error: Download failed

#875 Timeout in big directory delete Tim Kosse ah24199178
Description

Hello I am a very glad user of filezilla + filezilla server ! I've found a (little) bug : it is impossible for filezilla client to erase directories in filezilla server if this directiory is too big, if it contains many subdirectories and many files. Example : directory = image of WINDOWS-XP installation CD. Timeout on connexion duration stops this operation before it is complete. Timeout on connexion duration is not reinitialized at each operation (LIST ou DELE). To erase such big directories, it is necessary to proceed in several (many) smaller erase operations. Best regards.

Batch Modify
Note: See TracBatchModify for help on using batch modify.
Note: See TracQuery for help on using queries.