> Hi, > > I changed my scripts as you recommended. It still doesn't work. Here is the > script and the debug output. The strange thing is when I do the commands > interactively it works. > > open mainframe.levob.nl > user xxxx xxxx > set ftp:passive-mode off > set ftp:ssl-allow off > debug 9 > ls > bye > EOF > > > ---- Connecting to mainframe.levob.nl (192.168.1.9) port 21 > <--- 220-FTPSERVE IBM VM V2R4 at ESAREL22.LEVOB.NL, 10:23:53 EST THURSDAY > 06/26/03 > <--- 220 Connection will close if idle for more than 5 minutes. > ---> USER xxxx > <--- 331 Send password please. > ---> PASS xxxx > <--- 230 xxxx logged in; working directory = VMSYSU:SYSOWFTP.FTPFILES > ---> PWD > <--- 257 "VMSYSU:SYSOWFTP.FTPFILES" is working directory > ---> CWD > VMSYSU:SYSOWFTP.FTPFILES/VMSYSU:SYSOWFTP.FTPFILES/VMSYSU:SYSOWFTP.FTPFILES > <--- 550 SFS directory name format may be wrong; directory remains SFS: > VMSYSU:SYSOWFTP.FTPFILES > ls: Access failed: 550 SFS directory name format may be wrong; directory > remains SFS: VMSYSU:SYSOWFTP.FTPFILES > ---> QUIT > ---- Closing control socket
Well, there it fails not about passive mode. Look: it seems lftp is dazzeled because of the PWD result. Because of that, it does something really funny when trying to do "ls": CWD VMSYSU:SYSOWFTP.FTPFILES/VMSYSU:SYSOWFTP.FTPFILES/VMSYSU:SYSOWFTP.FTPFILES which results in this message from your FTP server: 550 SFS directory name format may be wrong; directory remains SFS: VMSYSU:SYSOWFTP.FTPFILES Seems that's FTPSERVE from IBM dazzles lftp hum ;-)
