ESP Workload Automation

Back to discussions
Expand all | Collapse all

FTP Download Error - 501 PORT IP is not same as ....... Download failed:

  • 1.  FTP Download Error - 501 PORT IP is not same as ....... Download failed:

    Posted Dec 20, 2017 08:39 AM

    I am trying to download a file from a vendor FTP using native FTP in CA (DE) and getting the following error.  The spool shows the connection was successfully established. Any ideas/suggestions?

     

    501 PORT IP is not same as ***.xx.***.250.

    Download failed: "PORT is unsuccessful"

    Logged out



  • 2.  Re: FTP Download Error - 501 PORT IP is not same as ....... Download failed:
    Best Answer

    Posted Dec 20, 2017 11:31 PM

    Kumar,

    This is because of the Active mode used for FTP. The "PORT" command is part of the Active mode connection and it requires the FTP Client (CA WA DE Agent / job) to share its IP Address to the external FTP Server. It's probably that your CA WA Agent is sharing its local address (intranet) with the FTP server, but connects using its external IP address (***.xx.***.250) and FTP server does not like the mismatch (external vs local).

    If your vendor supports Passive FTP mode, then update the following System Agent parameter in the agentparm.txt file on the CA WA Agent that runs the FTP job and restart the System Agent.

    ftp.passive=true

    From DocOps:

    • ftp.passive
      Specifies whether the agent FTP client uses a passive mode connection, as follows:
      • true
        Indicates that the agent uses a passive mode connection.
      • false
        Indicates that the agent uses an active mode connection.

      Default: false

      Note: We recommend that you set the value to true under any of the following conditions:
      • The agent uses IPV4 and the FTP server uses IPV6 for communication.
      • The FTP server resides beyond the firewall.
      • The FTP server opens a listening port for the data channel.

     

     

    Thanks,

    Chandru