Re: FTP commands issue

If you can FTP from your local machine to the client server but cannot
connect from a Windows box to the client's server, that sounds like FTP is
not open on the firewall from the Windows machine to the client's server.

The firewall may explicitly permit FTP traffic from your IBM i to the
client but not from the Windows box. You would want to look at all
firewalls between you and the client, not just your local firewall.

Thanks,

Steve McKay
(205) 585-8424
samckay1@xxxxxxxxx



On Fri, Feb 9, 2024 at 9:38 AM 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

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription related
questions.