Re: FTP commands issue

Hi, Mark,
Using the Windows FTP client to access OS/400 or IBM i FTP server, the issue is, FTP protocol wants to open another port from the FTP server back to the FTP client for sending "data" (a "back channel.")  This is typically blocked by a Windows firewall on your PC or another firewall in your router, wireless access point, etc.).
Go into the OS/400 or IBM i FTP client on any reasonably current IBM i, e.g. type "FTP localhost" or "FTP '127.0.0.1'" and sign-on with your userID/pwd, then type "Help" and press Enter.  Then put the cursor next to "PASV" and "SENDPasv" and press Enter, and read all about it.
(AFAIK, the Windows FTP client does not support PASV mode.)
Use a better FTP client like FileZilla - sourceforge.net/projects/filezilla/
Or try using WinSCP - winscp.net/eng/index.php (Windows only).
HTH,
Mark S. Waterbury
On Friday, February 9, 2024 at 10:38:42 AM EST, mlazarus <mlazarus@xxxxxxxxxxxx> wrote:

Steve,

1) This is on a new partition.

2) If I connect locally (meaning via a 5250 session: FTP LOCALHOST,
which is set to 127.0.0.1), those commands work fine under the same user ID.

  -mark

On 2/8/2024 8:11 PM, Steve McKay wrote:

Security software on IBM I?  WRKREGINF and check the FTP exit points.

Check for authority failures in QAUDJRN ( journal type T  AF).

Thanks,

Steve McKay
205-585-8424
samckay1@xxxxxxxxx


On Thu, Feb 8, 2024 at 7:08 PM mlazarus<mlazarus@xxxxxxxxxxxx>  wrote:

   

    I am running into a situation where an FTP session to a client's i,
where some commands work and others fail.

- Connection is via a VPN.
- FTP client is the basic Windows FTP.EXE, run in a DOS box.
- I'm able to connect and sign in using a QSECOFR level profile.
- Basic commands like CD, LCD, BIN, PWD work fine.
- Commands that access data like LS, DIR, GET, PUT have up the session
for a while and then times out:

ftp>  ls
200 PORT subcommand request successful.
425 Not able to open data connection.

- According to the network admin all ports for my connection are open.
- FTP to other machines from this PC work fine.

    Any idea what might be causing this?  Or how to debug it?  TIA.

    -mark