Peanut shells and Windows2003 the graphic tutorial for establishing an FTP server _ server

Windows 2003 Standard Edition, Windows 2003 Enterprise Edition, Windows XP Professional, Windows SQL Server, Windows xp-based Ad vanced Server and the default installation of Windows Professional are all equipped with IIS. IIS is not installed by default during the installation of the system and can be installed by adding a removal program after the installation of the system.

IIS is a set of integrated system components for WEB, FTP and SMTP servers launched by Microsoft, bundled in the server system above the NT core. This paper provides FTP services to the Internet through Windows2003 IIS components and peanut shell dynamic Domain name resolution software.
First step: Install Windows 2003 IIS in FTP Component
Select the file Transfer Protocol (FTP) service in the Add/Remove Programs--windows Component Wizard of Control Panel-Application server--internet Information Services (IIS). The following figure:


After you select the service you want to install, the Installation Wizard prompts you to insert the Windows 2003 installation disc, and when you insert the installation disk, you are prompted to install it, and FTP in IIS is quickly installed automatically.
The second step: Establish the network communication Section, for the established FTP Service settings Dynamic Domain name Resolution service configuration
1. Download peanut shell Dynamic Domain name resolution software and install.



2. Run peanut shell software, click "Registered Oray Passport", according to pop-up Registration Passport window prompts for registration. After the registered Oray passport is completed, use the registered Passport name and password to fill in the peanut shell software for landing.

3. Apply for a free domain name as "web site" for Internet access to FTP services

4. According to the prompts to activate the last step of the application of the free domain name Peanut shell Dynamic DNS service




This time, peanut shell software has been online, we have applied for the free domain name has been bound to the current public network IP address, the Internet can be applied to the domain name directly to the current public network IP, if your host is connected to the router or proxy server, please refer to the intranet site documentation. Below we continue to build the FTP service.
Step Three: Configure FTP Server

Open Control Panel--Administrative Tools--internet Information Services (IIS) Manager--ftp site. (Of course, you can enter the inetmgr into the manager in the run) we see that there are no subwebs or virtual sites in the FTP site, the next step is to configure



In the IIS FTP component, FTP each site can only correspond to one port, each site can only correspond to one global catalog. Permission order can be understood as a site >= virtual path, if you need to establish an anonymous access to the FTP service and the need to authenticate the FTP service, I am afraid to establish two sites, using 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 to Control Panel--management tools--Computer Management--Local Users and Groups--users (you can also run the Compmgmt.msc command into the admin interface). Here two new users are "test", "test1", do not need to give any permissions, after the establishment of the completion of the user process.



Enter Internet Information Services (IIS) Manager default FTP Site properties
"Allow anonymous connections" is not selected in the security account, otherwise anyone can connect to your global catalog via FTP.
In the directory of the FTP site directory selected to the external service file directory of the parent directory, if you do not want to this site under the subweb has 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, TEST and test1 account corresponding to the D:\TEST, D:\TEST1 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 test and test1 users we just created to the FTP directory respectively. Before a lot of friends asked, why Microsoft's FTP can not set the account number, 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 test--choose test corresponding access directory and give permissions-complete
Found it, actually. The virtual directory alias is the user login name, corresponding to the user in the user table. 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.







Using the same method, the Test1 user is mapped to the D:\TEST1 of the FTP directory by creating a virtual directory. We have completed the process of building the entire IIS FTP component, and we can start testing the FTP server.
Testing during testing to facilitate the use of Windows 2003 self-contained FTP commands

If you are not familiar with the FTP command, you can refer to the Oray Community's FTP command interpretation. Or install the FTP client to test.
Well, FTP has been established, quickly send your peanut shell domain name and login permission to share files with your friends.
This article belongs to oray.net original, if you need to reprint, please specify the source, thank you