Jerry,
Does their sFTP server respond to ICMP (ping) packets? If so, what do you
get when you try to ping the sFTP server hostname (sftp-dev.com) from both
machines? Does your IBM box correctly translate the name to the IP you
expect it to be? Does the IP address match on both the IBM box and the
machine that uses WinSCP? Even if PING isn't allowed, it's good to see what
the hostname translates to with DNS.
Have you tried connecting directly without a hostname, and instead
specifying the IP address of the sFTP server?
Did you try an SSH connection on port 22 just for kicks?
Are the two machines you mentioned on different networks/subnets/vlans? Any
difference in network addressing may lead to an additional stop at a
different router/firewall, which could affect your network traffic.
I would compare trace route results between the two machines you mentioned:
Machine A using WinSCP (if windows, use TRACERT), and Machine B running on
IBM i (use TRACEROUTE). If there are differences in router hops, I would
want to make sure that the network admins aren't dropping network traffic
along the way.
Next thing I would do is verify that your network admin isn't restricting
outbound traffic on port 23 from your IBM box. Your remote endpoint partner
says they are using port 23 for SSH and Telnet, but that doesn't necessarily
mean they are running it on the same box. They may have those services
running on different boxes, and they like to use port 23 for SSH, I guess?
Just thinking out loud...
------------
Jacob
------------
-----Original Message-----
From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of
midrange-l-request@xxxxxxxxxxxxxxxxxx
Sent: Wednesday, December 7, 2022 5:45 PM
To: midrange-l@xxxxxxxxxxxxxxxxxx
Subject: MIDRANGE-L Digest, Vol 21, Issue 1430
date: Wed, 7 Dec 2022 15:30:35 -0800
from: Jerry Draper <midrangel@xxxxxxxxxxxxx>
subject: Re: sFTP times out
We are only using SSH at this point because we need to receive the partner's
SSH fingerprint and write it to our known_hosts file.
We aren't even getting that far.
Feels like some kind of network issue.
Jerry
On 12/7/2022 1:44 PM, Jack Woehr wrote:
Ah, well, if I understand what you're trying to do, you should
probably try the sftp command and not the ssh command that you're
showing in the original posting.
midrange.com
