So AWS assigns their ip's based on an internal private ip and an external (kind of nat'd) ip - both dhcp. While you said this wasn't your problem - a very quick fix is to add an Elastic IP to the instance and force the FTP server to use that IP - usually works by default.
Or you can use the dynamic external ip muck about for ages to get the passive settings working on the AWS side via the software - which when you reboot the instance it'll change - rinse/repeat. From: "[email protected]<mailto:[email protected]>" <[email protected]<mailto:[email protected]>> Reply-To: ozDotNet <[email protected]<mailto:[email protected]>> Date: Friday, 18 October 2013 10:46 AM To: ozDotNet <[email protected]<mailto:[email protected]>> Subject: Re: [OT] FTP client problems >You do need a higher end firewall though. I didn't want to confuse matters previously, but now things have calmed down I can add that the offending server is actually inside an Amazon AWS server instance. I turned off the Windows firewall ages ago, but Amazon have their own "Security Group" feature where you say which inbound/outbound ports are open. I'm not sure why they have such a "meta firewall" as it just confuses things for customers. It turns out that this feature was irrelevant to our problem anyway. The other good news is that the chap writing the Borland C++ code found a passive switch which lets his ftp operations work perfectly. I'm still going to urge him over to http instead. Greg K
