Re: FTP error cannot connect -- MIDRANGE-L

One other possibility, although I'll call it a remote one, do you or the
vendor have any packet rules set up on IBM i? Yes you have everything but
a statefull firewall inside IBM i. In many of my customers they have asked
that the IBM i only be able to FTP to/from specific places inside the
network and then only from specific IP addresses out to the gateway. We
accomplish that with packet filters (look exactly like IPTABLES to be
honest) . It's really easy to set up and maintain, but it can be a
landmine if it's not documented properly.

Jim Oberholtzer
CEO/Chief Technical Architect
Agile Technology Architects

On Tue, Aug 1, 2017 at 1:57 PM, Versfelt, Charles <CVERSFELT@xxxxxxxxx>
wrote:

(Sorry forgot to change the subject line first send.)

We have a process that sends files via FTP and been trying to FTP to an
outside vendor, and we have been getting this message:
Cannot connect to host (ip address) at address . Try again later.

This only happens when connecting to the FTP server from the iSeries.
Other systems (not iSeries) such as a PC can connect.
Both our operations manager and the people at the vendor's site seem
unable to determine what to do.

FTP does work going from our iSeries to other locations. It's this one
vendor's system where we have an issue.

Now, here's the weird part:
We're working on the implementation. The vendor has two systems, a test
and a production system.
The production system is where we first encountered the problem. FTP was
working fine on the test system.
While trying to find the problem, and I was able to get a connection by
doing FTP 'the_url.com'
That is, until last Tuesday. Then, all of a sudden, the test system also
got the "cannot connect... try again later" error.

The vendor says nothing changed with the test server on their end.
The operations manager says nothing changed on our end either.
He's put in some time trying to research the problem.

I don't know if the problem is happening on the vendor's site, on our
iSeries, or in the firewalls in between.
I don't even know how to figure out where the problem is happening.

We are able to ping both the test site and the production from the iSeries.
I hope someone can steer us in the right direction on what to do.

This email message has been scanned for viruses and malware by Mimecast.
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxx for any subscription related
questions.

Help support midrange.com by shopping at amazon.com with our affiliate
link: http://amzn.to/2dEadiD