Opened 21 years ago

Last modified 11 years ago

#500 closed Bug report

VAX compatibility

Reported by: anonymous Owned by:
Priority: normal Component: Other
Keywords: Cc: Tim Kosse
Component version: Operating system type:
Operating system version:

Description

Hi,

We have an ancient VAX cluster that still operates some
vital equipment. Data is retrieved via FTP. The VAX runs a
very ancient FTP program that does not support many
modern features like passive mode. To date, it remains the
only machine with which Filezilla will not work. Filezilla
manages to log on to the machine, but fails to get the
directory listing. The VAX returns an error.

Is this a bug in Filezilla? Or do I have to make some
changes to the program? I have tried many things in
settings, but no combination has been successful.

I am running version 2.2.1a.

Thanks.

Payam

PS Both the client and server are fabulous programs. I
love them both. PM

Change History (7)

comment:1 by Tim Kosse, 21 years ago

Could you please post the message log of FileZilla with
enabled debug information? (Enable everything on the debug
page in the settings dialog)

comment:2 by anonymous, 20 years ago

Logged In: NO

We have the same Problem on a Micro VAX
here the log:
FileZilla started (12/17/2003 12:31:23)
Status: Verbinden mit 2.1.80.20...
Trace: FtpControlSocket.cpp(707): OnConnect(0) OpMode=1
OpState=-1 caller=0x00e9bdf0
Status: Verbunden mit 2.1.80.20. Warten auf Willkommens
Mitteilung...
Trace: FtpControlSocket.cpp(578): OnReceive(0) OpMode=1
OpState=-1 caller=0x00e9bdf0
Antwort: 220 VAX FTP Server (Version 3.0) Ready.
Befehl: USER lh75gh
Trace: FtpControlSocket.cpp(578): OnReceive(0) OpMode=1
OpState=0 caller=0x00e9bdf0
Antwort: 230 User logged in.
Status: Verbindung hergestellt
Trace: FtpControlSocket.cpp(3001): ResetOperation(1)
OpMode=1 OpState=-2 caller=0x00e9bdf0
Trace: FtpControlSocket.cpp(846): List(FALSE,0,"","",1)
OpMode=0 OpState=-1 caller=0x00e9bdf0
Status: Verzeichnisinhalt wird abgeholt...
Befehl: PWD
Trace: FtpControlSocket.cpp(578): OnReceive(0) OpMode=4
OpState=0 caller=0x00e9bdf0
Antwort: 257 $DISK1:[LH75GH] is current directory.
Trace: FtpControlSocket.cpp(846): List(FALSE,0,"","",0)
OpMode=4 OpState=0 caller=0x00e9bdf0
Trace: FtpControlSocket.cpp(1003): Can't parse path!
caller=0x00e9bdf0
Trace: FtpControlSocket.cpp(3001): ResetOperation(4)
OpMode=4 OpState=0 caller=0x00e9bdf0
Fehler: Dateiliste konnte nicht empfangen werden
Befehl: REST 0
Trace: FtpControlSocket.cpp(578): OnReceive(0) OpMode=0
OpState=-1 caller=0x00e9bdf0
Antwort: 502 REST is unimplemented.
Befehl: TYPE I
Trace: FtpControlSocket.cpp(578): OnReceive(0) OpMode=0
OpState=-1 caller=0x00e9bdf0
Antwort: 200 TYPE set to IMAGE.
Befehl: TYPE I
Trace: FtpControlSocket.cpp(578): OnReceive(0) OpMode=0
OpState=-1 caller=0x00e9bdf0
Antwort: 200 TYPE set to IMAGE.
Befehl: TYPE A
Trace: FtpControlSocket.cpp(578): OnReceive(0) OpMode=0
OpState=-1 caller=0x00e9bdf0
Antwort: 200 TYPE set to ASCII.
Befehl: TYPE A
Trace: FtpControlSocket.cpp(578): OnReceive(0) OpMode=0
OpState=-1 caller=0x00e9bdf0
Antwort: 200 TYPE set to ASCII.
Befehl: TYPE I
Trace: FtpControlSocket.cpp(578): OnReceive(0) OpMode=0
OpState=-1 caller=0x00e9bdf0
Antwort: 200 TYPE set to IMAGE.
Trace: FtpControlSocket.cpp(769): DoClose(0) OpMode=1024
OpState=-1 caller=0x00e9bdf0
Trace: FtpControlSocket.cpp(3001): ResetOperation(4100)
OpMode=1024 OpState=-1 caller=0x00e9bdf0
Status: Verbindung getrennt

comment:3 by anonymous, 20 years ago

Logged In: NO

We have the same Problem on a Micro VAX
here the log:
FileZilla started (12/17/2003 12:31:23)
Status: Verbinden mit 2.1.80.20...
Trace: FtpControlSocket.cpp(707): OnConnect(0) OpMode=1
OpState=-1 caller=0x00e9bdf0
Status: Verbunden mit 2.1.80.20. Warten auf Willkommens
Mitteilung...
Trace: FtpControlSocket.cpp(578): OnReceive(0) OpMode=1
OpState=-1 caller=0x00e9bdf0
Antwort: 220 VAX FTP Server (Version 3.0) Ready.
Befehl: USER lh75gh
Trace: FtpControlSocket.cpp(578): OnReceive(0) OpMode=1
OpState=0 caller=0x00e9bdf0
Antwort: 230 User logged in.
Status: Verbindung hergestellt
Trace: FtpControlSocket.cpp(3001): ResetOperation(1)
OpMode=1 OpState=-2 caller=0x00e9bdf0
Trace: FtpControlSocket.cpp(846): List(FALSE,0,"","",1)
OpMode=0 OpState=-1 caller=0x00e9bdf0
Status: Verzeichnisinhalt wird abgeholt...
Befehl: PWD
Trace: FtpControlSocket.cpp(578): OnReceive(0) OpMode=4
OpState=0 caller=0x00e9bdf0
Antwort: 257 $DISK1:[LH75GH] is current directory.
Trace: FtpControlSocket.cpp(846): List(FALSE,0,"","",0)
OpMode=4 OpState=0 caller=0x00e9bdf0
Trace: FtpControlSocket.cpp(1003): Can't parse path!
caller=0x00e9bdf0
Trace: FtpControlSocket.cpp(3001): ResetOperation(4)
OpMode=4 OpState=0 caller=0x00e9bdf0
Fehler: Dateiliste konnte nicht empfangen werden
Befehl: REST 0
Trace: FtpControlSocket.cpp(578): OnReceive(0) OpMode=0
OpState=-1 caller=0x00e9bdf0
Antwort: 502 REST is unimplemented.
Befehl: TYPE I
Trace: FtpControlSocket.cpp(578): OnReceive(0) OpMode=0
OpState=-1 caller=0x00e9bdf0
Antwort: 200 TYPE set to IMAGE.
Befehl: TYPE I
Trace: FtpControlSocket.cpp(578): OnReceive(0) OpMode=0
OpState=-1 caller=0x00e9bdf0
Antwort: 200 TYPE set to IMAGE.
Befehl: TYPE A
Trace: FtpControlSocket.cpp(578): OnReceive(0) OpMode=0
OpState=-1 caller=0x00e9bdf0
Antwort: 200 TYPE set to ASCII.
Befehl: TYPE A
Trace: FtpControlSocket.cpp(578): OnReceive(0) OpMode=0
OpState=-1 caller=0x00e9bdf0
Antwort: 200 TYPE set to ASCII.
Befehl: TYPE I
Trace: FtpControlSocket.cpp(578): OnReceive(0) OpMode=0
OpState=-1 caller=0x00e9bdf0
Antwort: 200 TYPE set to IMAGE.
Trace: FtpControlSocket.cpp(769): DoClose(0) OpMode=1024
OpState=-1 caller=0x00e9bdf0
Trace: FtpControlSocket.cpp(3001): ResetOperation(4100)
OpMode=1024 OpState=-1 caller=0x00e9bdf0
Status: Verbindung getrennt

Hans.Zeitler@…

comment:4 by Tim Kosse, 20 years ago

FileZilla can't parse the path returned by the server.

Can you please explain how that file system works?

$DISK1:[LH75GH] is the directory returned from the server.

$DISK1 is the drive the data is on. Does this always start with
$DISK or are other types possible, like $FLOPPY1 or something
similar?

[LH75GH] is the directory name. How are subdirectories
appended? Something like [dir.subdir] ? And to access a file,
do I have to write $DISK1:[dir]File or $DISK1:[dir]/File or
something else?

comment:5 by anonymous, 20 years ago

Logged In: NO

$Disk1: is a logical name like in Windows N: for a mapped
networkdrive
Logical names can be set individually.
$FLOPPY1 would also be possible.
devices are written without $, like HDX1:

also possible: node::device:[dir]file.text
length of (network)node max 6 chars

[dir.subdir] is right

relative: if actual dir is [dir] write [.subdir] for
access of the subdir
[-] is like ..\ in dos

DIRECTORY [*...] lists the actual and all subdirs

to access a file : $DISK1:[dir]File or
$DISK1:[dir.subdir1.subdir2]File

filename.filetype;fileversion
filename 1 to 39 chars,numbers, underscore or $
filetype separated with a dot 1 to 39 chars,numbers,
underscore or $
fileversion is a number
omitting the version takes the newest one.

DELETE deletes only a specific version of a file.
PURGE deletes all versions

wildcards: * 1 or more, % 1 char

Hans.Zeitler@…

comment:6 by anonymous, 20 years ago

Logged In: NO

$Disk1: is a logical name like in Windows N: for a mapped
networkdrive
Logical names can be set individually.
$FLOPPY1 would also be possible.
devices are written without $, like HDX1:

also possible: node::device:[dir]file.text
length of (network)node max 6 chars

[dir.subdir] is right

relative: if actual dir is [dir] write [.subdir] for
access of the subdir
[-] is like ..\ in dos

DIRECTORY [*...] lists the actual and all subdirs

to access a file : $DISK1:[dir]File or
$DISK1:[dir.subdir1.subdir2]File

filename.filetype;fileversion
filename 1 to 39 chars,numbers, underscore or $
filetype separated with a dot 1 to 39 chars,numbers,
underscore or $
fileversion is a number
omitting the version takes the newest one.

DELETE deletes only a specific version of a file.
PURGE deletes all versions

wildcards: * 1 or more, % 1 char

Hans.Zeitler@…

comment:7 by Tim Kosse, 20 years ago

Please try the latest test release from
​http://filezilla.sourceforge.net/FileZilla.exe

FileZilla did already support this type of directory structe. The
true problem was that your server did not put the path into
quotes in the reply to the PWD command.

Note: See TracTickets for help on using tickets.