Note to Users of Microsoft IIS version 2.0 and 3.0 FTP Server:

The installation documentation for SafeTP Server NT/2000 directs you to reconfigure your legacy FTP server to listen on a new FTP port (e.g. port 351) so that the SafeTP Server proxy can occupy the well-known FTP port (port 21).  Unfortunately, it seems that the FTP server included with Microsoft IIS 2.0 and 3.0 has a bug related to the configuration of the FTP service port, so changing the port in the configuration settings is insufficient to actually cause the FTP server to listen on a new port. Luckily, this problem has apparently been corrected in newer versions of IIS.

Microsoft Knowledge Base Entry Concerning FTP port on IIS

If you have problems getting SafeTP NT/2000 to work over Microsoft IIS FTP, this is probably why. You can verify whether the IIS FTP server is correctly configured to listen on the new port by using ftp.exe to connect to the new port and verify that IIS FTP answers the connection.

Here's a summary of how to fix the problem:

You can change FTP server TCP port numbers by modifying the Systemroot\System32\Drivers\Etc\Services file or by changing their values in the Registry. The setting in the Services file takes precedence over the Registry setting in all cases. That is, by changing the Services file, you affect both the FTP client and the FTP server. By changing the Registry, you affect only the FTP server.

To change the TCP port in the Services file:

Note, this affects the default TCP ports on both the FTP client and the FTP server. Your FTP server now waits at port 351 for all FTP client requests and your FTP client connects only to an FTP server at port 351. To verify the new FTP port settings:

To change the Registry entry for FTP:

Back to SafeTP Home