Force IP Address Functionality - Bug?
I was working with one of our clients to establish their FTPS connections with our system. From our testing environment things worked well but when the attempt to connect to our produciton hosts the data channel could not be established. We found this issue was with the passive reply. In the testing environment our server returns a public IP address. In the production setting an internal, private address is sent.
The WinSCP session config initally had the Force IP Address set to Off in the advanced settings. When we set that to On the connection to the production server worked, but the connection to the test server then failed to establish the data channel.
I would think this is a bug (though perhaps a situation not anticipated in design). If the server returns the same IP address as the initial connection for the control channel and Force IP Address is set on shouldn't that work?
The WinSCP session config initally had the Force IP Address set to Off in the advanced settings. When we set that to On the connection to the production server worked, but the connection to the test server then failed to establish the data channel.
I would think this is a bug (though perhaps a situation not anticipated in design). If the server returns the same IP address as the initial connection for the control channel and Force IP Address is set on shouldn't that work?
