IIS 5.0 ======= - On IIS 5.0 the Passive FTP Port range is controlled via a registry key
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Msftpsvc\ParametersPassivePortRange REG_SZ 5500-5525
IIS 6.0 ======= - On IIS 6.0 the Passive FTP port range is controlled via a metabase key
adsutil.vbs set /MSFTPSVC/PassivePortRange "5500-5525"
IIS 7.0 ======= - IIS 7.0 has two FTP services available
1. Classic FTP Service ------------------------------------- - The classic FTP service is similar to IIS 6.0 and requires IIS 6.0 Metabase compatibility to be installed - Here the Passive FTP port range is controlled via the metabase key
- Similar to IIS 6.0
2. FTP7 Module -------------------------- - This is an OutOfBand Module that is shipped as an addon - FTP7 module is used when SSL over FTP is required - Here the Passive FTP port range is controlled via an entry in applicationHost.config - You can also set this using the IIS Manager UI
Global Level (Server name) > FTP Firewall Support > Data Channel Port Range
Passive FTP uses a range of ports to transfer data. This can be a problem because the port range that
I was searching for a way to limit port range on IIS5.0 to run server behind cisco firewall for like a year and was told that there is no such thing.
Ya de regreso por españa aprovecho para comentar un truquillo que he aprendido estos días sobre como
Very Useful and Awesome comparison.
I've tried this on my company's IIS7. The settings does not take effect even after restarting IIS. I had to go into services, fully STOP the "Microsoft FTP Service" and then START it again. Then only it starts honoring the port range.
Hopefully this may help someone confused over why the settings does not work.