IIS Web site FTP configuration

Open the program-the Administrative Tools--internet Information Services (IIS) Manager--ftp the site (or enter inetmgr into the manager at run).
In the IIS FTP component, FTP each site can only correspond to one port, each site can only correspond to one global catalog. The permission order can be understood as a site >= virtual path, and if you need to establish an anonymous access FTP service and an FTP service that requires authentication, you need to set up two sites and use two different ports. First of all, we set up a need to authenticate the FTP site, so that the Internet landing FTP service requires authentication in order to obtain a trust with the FTP server connection. Access programs--management tools--Computer Management--Local Users and groups--users. Here create a new user Aamm, do not need to give any permissions, after the establishment of the completion of the user process.
Enter the Internet Information Services (IIS) Manager Default FTP Site property "Allow anonymous connections" is not selected in the security account, otherwise anyone can connect to your global catalog via FTP. The FTP Site directory in the home directory is selected to the parent directory of the external service file directory, and if you do not want the subweb under this site to have write permission, then write permission does not need to be selected. If there is a subweb under this site that requires write access, then the global site FTP permissions must be written, and if you feel insecure, you can transfer the FTP directory data to an empty partition or a subdirectory. For example, the Aamm account corresponds to the D:\aamm directory, then the FTP global Site directory must be d:\.

Now that the FTP service interface has been serviced to the Internet, no user can actually access the resources from your FTP access. We need to map the Aamm user we just created to the FTP directory. Before a lot of friends asked, why Microsoft FTP can not set up the account number of places, can only set anonymous or not anonymous. Actually, it's OK, but it's a little bit of a trick. Right-click FTP Default Site--new--Virtual directory--virtual directory alias input aamm--select Aamm corresponding access directory and give permissions-complete virtual directory alias is the user login name, corresponding to the user table in the user. We can set up FTP users through the system to correspond to different sites of the FTP subweb directory. Of course, a user can correspond to multiple paths, which we need to use FSO permissions to control.






Here we can start testing the FTP server.
Test during the testing process to facilitate the use of Windows 2003 FTP commands with your own. If the extranet link does not succeed:
1. open Windows Firewall;
2. C:\windows\system32\inetsrv\inetinfo.exe The core program of IIS into the "exceptions" set by the firewall;
3. In the firewall set "advanced-local connection-settings" in the FTP to cancel the check.
Done.