Besides opening incoming HTTP ports in the firewall via “Global Rules”, the annoying thing for me to find was also adding an “Application Rule” for “Windows Operating System” on those same ports.
And this guy explains what’s necessary for FTP very nicely…
- in comodo > global settings > application rule – add 20,21 & 5000-6000 as allowed incoming TCP ports on “Windows Operating System”… you will also hopefully get prompted to allow svchost which is responsible for running the ftpsvc
- on internet router – forward ports 20,21 and 5000-6000
- in IIS FTP settings
- require SSL
- firewall support – put external wan address in
- firewall support at *SERVER* level (not site) – set ports 5000-6000
- point ftp site a folder
- create login for ftp and make sure it has access to folder
- Response: 530 User cannot log in, home directory inaccessible.
- Error: Critical error: Could not connect to server“
require explicit ftp over tls