Some errors you might get if you don’t follow all the steps below:
Local policy on server does not allow TLS secure connections
Hostname didn’t match any configured ftp site.
1) First create a self signed server certificate.
2)
To allow web publishing via Secure FTP do this.
OR
To setup a strand-alone FTP server do this.
Only I’d recommend setting “require SSL” and encrypting all data, not just the login credentials.
3) RESTART THE “Microsoft FTP Service” in the services control panel for changes to take effect!
Not all IIS7 FTP changes take place, even if the FTP service is restarted from the admin control panel.
For example setting the Firewall Data Port Range and possibly the External Firewall IP Address requires that the “Microsoft FTP Service” service be restarted before it will take effect. I spent ridiculous amounts of time trying to figure this out among other things.
I used Core FTP as the client:
Username format FTPSiteHostname|Username
For example: ftp.somedomain.com|someuser
Check PASV
Connection: AUTH TLS
Check SSL Listings
Check SSL Transfer
Check Windows SSL
The username syntax is *VERY* important, don’t forget it!
To read (and see) how Passive and Active FTP work go here.
