In Internet Information Services (IIS) 6.0, changes to the IP restriction list of an FTP site are not applied until you restart the FTP service.
For example,
suppose that you deny all users permission to access an FTP site, and then you allow a particular IP address to access the site. When you then use the
ftp command to try to access the site, you may receive an error message that resembles the following:
530 Connection refused, unknown IP address.
421 Service not available, closing control connection.
Connection closed by remote host.
However, after you restart the FTP service, the command-line interaction resembles the following:
Connected to ftp.servername.domain
220 Microsoft FTP Service
User: domain\user
331 Password required for domain\user.
Password:
230 User domain\user logged in.
In IIS 6.0, changes to the IP restriction list are applied only after you restart the FTP service.
However, the FTP service will re-read and apply changes to the IP restriction list if you change one or more of the following settings:
- MD_FTP_LOG_IN_UTF_8
- MD_USER_ISOLATION
- MD_SHOW_4_DIGIT_YEAR
- MD_ALLOW_REPLACE_ON_RENAME
- MD_ANONYMOUS_ONLY
- MD_ALLOW_ANONYMOUS
- MD_MSDOS_DIR_OUTPUT
- MD_MAX_CLIENTS_MESSAGE
- MD_BANNER_MESSAGE
- MD_GREETING_MESSAGE
- MD_EXIT_MESSAGE
For a full description of the FtpLogInUtf8 Metabase property, visit the following Microsoft Web site:
In IIS 7.0, you do not have to restart the FTP service for changes to the IP restriction list to take effect. The new FTP Publishing Service for IIS 7.0 also supports changing the IP restriction list without restarting the FTP Service. To obtain the new FTP Publishing Service, visit the following Microsoft Web site: