Advanced configuration of FTP server in IIS in Windows

When it comes to FTP servers, everyone may think of software such as Serv-U and vs-FTP. In fact, Microsoft's built-in FTP service in IIS is enough. If you don't believe it, please read below.

Implement management of multiple users

First, you need to cancel "Site Properties/Allow anonymous connections", as shown in Figure 1.




Then go to "Computer Management/Local Users and Groups", create a new group, here it is created as FTPuser, then create a new user FTP01, then modify the properties of FTP01, add it to the FTPuser group, and remove the system default users group. Create folders FTP01 and FTP02 in the NTFS formatted partition (here, drive d), and then set security permissions, as shown in Figure 2.




Also set the permissions of the folder FTP02 to FTP02 Full Control. Of course, different permissions can be assigned to different users according to the actual situation. Go back to IIS Manager, select an FTP site "New/Virtual Directory/Next", enter FTP01 in the alias, select "Next", select the FTP01 directory just created as the path, select "Next", and also create a new virtual directory FTP02, the path points to the FTP02 directory. Note here: the alias, directory name and user name must be exactly the same.

Test it: Take the IP address as 192.168.0.16 as an example. Enter FTP://192.168.0.16 and press Enter. You will be prompted to enter the user and password. Enter FTP01 and its password to enter successfully. At this time, you can only enter the FTP01 virtual directory. , you can upload a file and then check on the server which directory it is placed in to determine. Similarly, if you log in with FTP02, you will enter the FTP02 directory. Users are restricted to their own directory and cannot enter other people's directories. Security is still guaranteed. If the user needs to be able to change the password by himself, he only needs to uncheck the option shown in Figure 3 when creating the user.

Tips:
How to change the FTP account password on the client side:
At the command prompt enter:
FTP 192.168.0.16
Enter user name, enter password, enter quote “site pswd old password new password”
Advantages of this method: Combining NTFS permissions and disk quotas can well achieve diversified management of multiple users.
Disadvantages of this method: Since the FTP user password is transmitted in clear text on the network, it is not very secure. Unfortunately, the built-in FTP service of IIS does not support SSL, which is not as good as Serv-U.

[Cut-Page]

Implementing the link function in Serv-U <br /> This is achieved using the path resolution principle, which can be regarded as a hidden function of MS-FTP. First, create a folder named tools under the root directory of the FTP site (here the d drive). In the IIS manager, create a virtual directory named tools under the FTP site. The path points to "Tools" under the f drive. Table of contents. Note that the name of the virtual directory here must be consistent with the name of the folder created in the root directory of the site.

When logging in on the client, you cannot use FTP01 or FTP02 to log in, because after logging in, they go directly to the corresponding subdirectory under the site root directory. At the same time, they cannot go back to the site root directory, so they can only create new users. Here I created an FTP03 user. After logging in, I found that in addition to the FTP01 and FTP02 directories, there are other directories. However, the permissions for the FTP01 and FTP02 directories were set previously, so FTP03 cannot access them. It just knows the existence of these directories. . Click on the tools directory and you will find that it automatically points to the "Tools" directory under the server's f drive.

Advantages of this method: The link function is implemented without third-party tools, which is especially useful when multiple drives are available. If you want to link to a complete partition, then create a folder in the site root directory with the same name as the drive letter.

Disadvantages of this method: additional users need to be created. If users like FTP01 want to browse content on other disks, it will be difficult.

Automatically update FTP site directory and file list

Windows has a very useful command tree that can show its talents here. If the root directory of the FTP site is d, we only need to create a batch file with the following content tree /f /ad: >d:FTP.txt

Then add a task schedule to run every hour. It is worth noting that after adding a task, advanced settings must be performed, as shown in Figure 4.

After setting it up in this way, when users log in, they can first download the FTP.txt file to the local computer to see if there are updates. This can save users time searching for updates in one directory after another, especially when the network speed is slow. To expand this, you can save more user time. You still need to rely on another useful Windows command, fc, to write the following batch file FTP update.bat:
tree /f /ad: >d:FTPnew.txt
fc /L d:FTP.txt d:FTPnew.txt >d:FTP update list.txt

Then run the FTP.bat written earlier, and then run the FTP update.bat. At this time, you can view the FTP update list.txt. If there is an update, it will start with ***** and end with *****. It points out which directory has been updated and lists the updated file names. Is it more clear? Users only need to download the FTP update list.txt first to view it. Of course, the user has already browsed this FTP site. Just browse and download FTP.txt for the first time. If you think that the file FTPnew.txt should not appear in the root directory of the site , or you can point to other locations when editing commands.

Nowadays, there are many FTP lists on the forum. Manual maintenance is really troublesome. As long as the FTP update list.txt is placed in a Web path or a virtual directory is specially created to point to the directory where the FTP update list.txt is located, then we can The browser directly browses this file. Because the IE browser can directly parse the txt file, it will not prompt for download. In order to make it more convenient for viewers, you can also add FTP update.bat. The complete FTP update.bat content is as follows:
tree /f /ad: >d:FTPnew.txt
fc /L d:FTP.txt d:FTPnew.txt >d:FTP update list.txt
echo update time >> d:FTP update list.txt
date /t >> d:FTP update list.txt
time /t >> d:FTP update list.txt

Then add a scheduled task and execute this batch file every hour, so that the viewer not only sees the updated content, but also knows the update time, and the next update time can be calculated by himself. If you frequently log in to this FTP site, you can also add this address to your favorites. You can know whether the server has been updated without logging in to FTP. If you are interested, you can visit http://test.yuanlin.cn/FTP list update.txt to see the effect.

The tools mentioned above are all built-in with Windows, and no third-party tools are used. In fact, there are still many places in Windows worth exploring.

[Cut-Page]

Implementing the link function in Serv-U <br /> This is achieved using the path resolution principle, which can be regarded as a hidden function of MS-FTP. First, create a folder named tools under the root directory of the FTP site (here the d drive). In the IIS manager, create a virtual directory named tools under the FTP site. The path points to "Tools" under the f drive. Table of contents. Note that the name of the virtual directory here must be consistent with the name of the folder created in the root directory of the site.

When logging in on the client, you cannot use FTP01 or FTP02 to log in, because after logging in, they go directly to the corresponding subdirectory under the site root directory. At the same time, they cannot go back to the site root directory, so they can only create new users. Here I created an FTP03 user. After logging in, I found that in addition to the FTP01 and FTP02 directories, there are other directories. However, the permissions for the FTP01 and FTP02 directories were set previously, so FTP03 cannot access them. It just knows the existence of these directories. . Click on the tools directory and you will find that it automatically points to the "Tools" directory under the server's f drive.

Advantages of this method: The link function is implemented without third-party tools, which is especially useful when multiple drives are available. If you want to link to a complete partition, then create a folder in the site root directory with the same name as the drive letter.

Disadvantages of this method: additional users need to be created. If users like FTP01 want to browse content on other disks, it will be difficult.

Automatically update FTP site directory and file list

Windows has a very useful command tree that can show its talents here. If the root directory of the FTP site is d, we only need to create a batch file with the following content tree /f /ad: >d:FTP.txt

Then add a task schedule to run every hour. It is worth noting that after adding a task, advanced settings must be performed, as shown in Figure 4.

After setting it up in this way, when users log in, they can first download the FTP.txt file to the local computer to see if there are updates. This can save users time searching for updates in one directory after another, especially when the network speed is slow. To expand this, you can save more user time. You still need to rely on another useful Windows command, fc, to write the following batch file FTP update.bat:
tree /f /ad: >d:FTPnew.txt
fc /L d:FTP.txt d:FTPnew.txt >d:FTP update list.txt

Then run the FTP.bat written earlier, and then run the FTP update.bat. At this time, you can view the FTP update list.txt. If there is an update, it will start with ***** and end with *****. It points out which directory has been updated and lists the updated file names. Is it more clear? Users only need to download the FTP update list.txt first to view it. Of course, the user has already browsed this FTP site. Just browse and download FTP.txt for the first time. If you think that the file FTPnew.txt should not appear in the root directory of the site , or you can point to other locations when editing commands.

Nowadays, there are many FTP lists on the forum. Manual maintenance is really troublesome. As long as the FTP update list.txt is placed in a Web path or a virtual directory is specially created to point to the directory where the FTP update list.txt is located, then we can The browser directly browses this file. Because the IE browser can directly parse the txt file, it will not prompt for download. In order to make it more convenient for viewers, you can also add FTP update.bat. The complete FTP update.bat content is as follows:
tree /f /ad: >d:FTPnew.txt
fc /L d:FTP.txt d:FTPnew.txt >d:FTP update list.txt
echo update time >> d:FTP update list.txt
date /t >> d:FTP update list.txt
time /t >> d:FTP update list.txt

Then add a scheduled task and execute this batch file every hour, so that the viewer not only sees the updated content, but also knows the update time, and the next update time can be calculated by himself. If you frequently log in to this FTP site, you can also add this address to your favorites. You can know whether the server has been updated without logging in to FTP. If you are interested, you can visit http://test.yuanlin.cn/FTP list update.txt to see the effect.

The tools mentioned above are all built-in with Windows, and no third-party tools are used. In fact, there are still many places in Windows worth exploring.