Ok, so we have an in-house MFT product we use for sftp transfers.
The sftp runs in PASE on the i

Works great and we work with many external vendors.
All have been smooth in initial setup and connection tests.

However, we are now working with one that is quite challenging.

From our dev/qa lpars we can connect to their uat/prod sftp server.
From our prod lpar we cannot connect to either. Though last week we
connected one time to their uat from our prod but cannot anymore. And
never have connected our prod to their prod.

We have diligently been working with our internal network team along with
their technical team to determine why we cannot connect.
They are on an aws virtual sftp solution in which the only configuration
they can apply is the whitelisting of our IP address which they have
already done. (same ip address we have provided other vendors that require
whitelisting and works with them)
We ask them to ensure that the same privileges are in place for our prod as
that are in place for our dev/qa lpars since those are able to connect.
They said they have.
Still no luck in connecting.

Method of connecting via sftp from from our dev/qa

- IBM i PASE


spawn sftp -vvv -o PreferredAuthentications=password -oport=22
user@xxxxxxxxxx

OpenSSH_6.9p1




Reading configuration data
/QOpenSys/QIBM/ProdData/SC1/OpenSSH/etc/ssh_config

ssh_connect: needpriv 0

Connecting to domain.net [xxx.xx.xxx.xxx] port 22.

Connection established.

<additional log details continue>



Method of connecting via sftp from our prod (with same ssh_config file)

- IBM i PASE


the log only produces this...


spawn sftp -vvv -o PreferredAuthentications=password -oport=22
user@xxxxxxxxxx

OpenSSH_6.9p1




Reading configuration data
/QOpenSys/QIBM/ProdData/SC1/OpenSSH/etc/ssh_config

ssh_connect: needpriv 0

Connecting to domain.net [xxx.xx.xxx.xxx] port 22.



this type of log has proven to be a whitelisting issue in the past with
other vendors which allows us to overcome the connection challenge once
whitelisting is in place.



So clearly shows our attempt to establish the connection.


Can anyone advise me on what we have to do to get this to work?


Does our log provide evidence it is at least making it to their IP address
to initiate a connection?


How can we troubleshoot this further knowing the remote end has no real
technical expertise in place to help us troubleshoot this?



TIA


Jay

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2022 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.