Probably because Server 2012 supports FTPS – I remember speaking to the PM on the IIS team about this at the time, and Microsoft invested a fair amount of time and effort into developing FTPS (including contributing the RFC for the equivalent of Host header support for FTPS)
Cheers Ken From: ozdotnet-boun...@ozdotnet.com [mailto:ozdotnet-boun...@ozdotnet.com] On Behalf Of Richard Carde Sent: Friday, 18 October 2013 8:25 PM To: ozDotNet Subject: Re: [OT] FTP client problems Or SFTP (not to be confused with FTPS) which works flawlessly through firewalls, is easy to reverse publish and is secure. I don't understand why Server 2012 still doesn't do it. -- Richard Carde Ph: +44 7956 356 226 On 18 Oct 2013, at 04:22, Grant Maw <grant....@gmail.com<mailto:grant....@gmail.com>> wrote: Just a side-comment - maybe we're luddites here, but we use FTP all the time to get things from A to B. Every single day. I know it's old, but it's still useful. On 18 October 2013 09:46, Greg Keogh <g...@mira.net<mailto:g...@mira.net>> wrote: >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
