Hi Warning: Wild guessing ahead:
> When my FTP client ... So you have the client on your side. > But, admin.quiksilver.com is 66.161.40.76, not 172.20.10.50. Note, this IP is a private address, which is not even suppost to be routed. > ... FTPSClient ... And that is using ftpS. So I guess the Server itself actually HAS 172.20.10.50 and is behind some NAT router, which inspects protocolls to replace the internal ip 172.20.10.50 with the external one 66.161.40.76. I also suppose, this works fine for FTP and external systems never see the internal address. However, FTPS is SSL-encrypted and as such the NAT-router cannot change or even see, what's inside the packet. So you get the original reply. There is nothing you can do about that, except if you can reconfigure the server. SFTP doesn't play well behind nat routers, if not configured especially. For example pure-ftps has an option to specify another ip address for answers as that one and to ignore the servers ip address. The only other option would be to enable the nat router to decrypt the ssl connection, which would be both very cpu-consuming and insecure. Regards, Steffen
smime.p7s
Description: S/MIME cryptographic signature
