Hello, got a response back from the mainframe team.
It looks like it might be related to a public to private address switching that isn't working in filezilla?
Quote:
Darren,
This is a known issue that was discovered during the ClearText project several years ago.
Due to how FTPS works with the Ephemeral Ports and the data connection, the private address gets sent from the Mainframe FTPS Server to the FTPS Client.
FileZilla is one of the FTPS client products that does not know how to handle this. WS_FTP Pro does handle it though.
At this time, the only way to resolve this for FileZilla is to put the public address, instead of the private address, on the mainframe.
To do that would require a project be started as it effects the mainframe, Firewalls and more.
This is a known issue that was discovered during the ClearText project several years ago.
Due to how FTPS works with the Ephemeral Ports and the data connection, the private address gets sent from the Mainframe FTPS Server to the FTPS Client.
FileZilla is one of the FTPS client products that does not know how to handle this. WS_FTP Pro does handle it though.
At this time, the only way to resolve this for FileZilla is to put the public address, instead of the private address, on the mainframe.
To do that would require a project be started as it effects the mainframe, Firewalls and more.
It looks like it might be related to a public to private address switching that isn't working in filezilla?