on 03-05-2015 2:42 PM
Hello Experts,
We have an PI adapter (ftp adapter) configured to send files to a remote ftp server, we have a firewall between PI and remote server. Configuration was done using the following Configuring the Receiver FTP Adapter - Configuring the File/FTP Adapter in Integration Directory/PCK...
Remote server has an IP address that we have configured on firewall with a range of port numbers that we can connect through to on remote server.
The FTP transfers happen in the following manner
1) FTP adapter makes connection to remote host, exchanges userid/password, remote server sends acknowledgement = Works
2) FTP adapter issues PASV command = Works
3) Remote Server responds back with new IP address and port number (the IP address is potentially garbage) = Works
4) PI FTP Adapter attempts to connect on new IP address and port number (IP address is garbage, so it doesn't go anywhere) = Doesn't Work
5) PI FTP Adapter bails out after a timeout.
Has anyone found a solution to this ? is there a way to get PI to use a specific IP address when it issues a PASV command in the FTP adapter.
Is there a way to force PI to continue to use the original IP address that was used to connect to remote host.
I have tried searching on SDN and found the following links:
They don't resolve my problem.
PS: If I login into PI box at unix level and try to use FTP client to directly login into remote server using ftp <remote server> , it works, it also allows me to transfer files using PASSV mode.
Regards,
Siddhesh
Hi Siddesh ,
Not sure with this , ( May be will help you )
Can you check whether the following is enabled in the FTP interface configuration in the PI ( By default it is enabled , you may disable )
strictHostnameChecking
1591971 - Added property strictHostnameChecking
Thanks ,
Manu
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello Manu,
We asked the Third Party hosting the Remote FTP server to amend the FTP server parameters so that it returns the correct IP, which was always going to be plan A.
But I thought the note you provided may have resolved the problem anyways, however since the issue is fixed we didn't apply the note.
So I am marking your suggestion as answered for future reference for others,Thank You.
Regards,
Siddhesh
Hello Manu,
I checked the note again, applied it for checking whether it resolves the issue, unfortunately it doesn't.
The query is about forcing the adapter to use the OLD IP instead of the new one if the FTP server is responding with a wrong IP.
The flag, only stops PI from generating any certificate errors, it doesn't force the adapter.
For future references, I am unmarking this question as answered, but thanks anyways for your reply.
Regards,
Siddhesh
Hi, Siddhesh,
I see the date of your question. Did you get an answer to this? I have the same problem and cannot find a solution by Googling.
Thank you.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi
I think you have to check your firewall setting on both sides, One of the port getting blocking while access from SAP.
Is this any exceptions?
BR
SS
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello Sriram,
I think you haven't understood the question.
FTP protocol mandates that the FTP client makes 2 connections with FTP server:
1. Login Connection - For exchange of authentication and general connectivity
2. Data Connection - For transfer of files, this connection can be done in two modes, Active and Passive (Google this for more information)
In Passive mode, the client issues a PASV command, the FTP server returns two values in a data packet (IP, Port number) this response means, the FTP server is ready to accept data connection from client on the provided IP and Port.
The IP being returned by FTP server (on invocation of PASV command) sometimes is garbage IP instead of its own IP, which is typical behavior of FTP servers when PASV mode is invoked.
However, most FTP clients (like FileZilla, LFTP) are programmed to ignore this garbage IP and use the original IP/hostname that was supplied for by us for initiating data connection.
So, my question is it possible to force PI to use the original IP.
Regards,
Siddhesh
User | Count |
---|---|
61 | |
9 | |
7 | |
6 | |
6 | |
6 | |
5 | |
5 | |
5 | |
5 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.