Server is a high-performance computer. As a node of the network, it stores and processes 80% of the data and information on the network. Therefore, it is also known as the soul of the network. When it comes to FTP server, I think most people are familiar with it, but many people don't know how to configure FTP server. In fact, it's very simple. If you don't understand it, please take a look at the FTP server configuration tutorial of Win2003 system I sorted out!
Method / step:
1. First, in the start menu, select management tools and click Internet Information Service (IIS) manager.
2. Open the Internet information services (IIS) manager.
3. Select FTP site, right-click, select new, and click FTP site (f).
4. Enter the FTP site creation wizard page and click next.
5. Enter the name in the description box and click next.
6. Use the default value on this page and click Next directly.
7. Use the default selection and click next.
8. Click "browse (R)" to select the directory and click next.
9. Enter the FTP site access permission interface, check write (W), and click next.
10. Finally, click Finish to complete the FTP site creation wizard.
Supplement: server introduction
Servers, also known as servers, are devices that provide computing services. Since the server needs to respond to service requests and process them, generally speaking, the server should have the ability to undertake services and ensure services.
The composition of the server includes processor, hard disk, memory, system bus, etc., which is similar to the general computer architecture. However, due to the need to provide highly reliable services, it requires high processing capacity, stability, reliability, security, scalability, manageability and so on.
In the network environment, according to the different types of services provided by the server, it is divided into file server, database server, application server, web server, etc.
Related reading: what are the server FAQs
1. System blue screen, frequent crash, restart, slow response
The of the server is very similar to our ordinary computer, whether it is hardware structure or running system. Therefore, just like our computers, they may be infected with viruses, crash, blue screen, restart and other failures due to system vulnerabilities, software conflicts and hardware failures, and slow response due to too much garbage cache information.
2. The remote desktop connection exceeds the maximum number of connections
Since the server allows 2 connections by default, if you forget to log off after logging in and directly close the remote desktop, the server recognizes that the login is still on the server side. In this case, the most common is to restart the server. However, if it is the peak period, the loss caused by restarting the server is obvious. At this time, you can use the mstsc / console command to forcibly log in. Open the "run" box and type "mstsc / V: xxx.xxx.xxx.xxx (server IP) / console" to forcibly log in to the remote desktop.
3. How to clean up files that cannot be deleted
In this case, it may be that the file is still running. You can restart and delete it, or run CMD, enter the name of the folder arrtib-a-s-h-r you want to delete, and finally enter the name of the folder del wants to delete. It cannot be recovered after running this command. Please use it with caution.
4. Hidden trouble of system port
For the server, the first thing is to ensure stability and security. Therefore, we only need to ensure the most basic functions of the server, just like the sound card is prohibited by default. We don't need too many functions and port support. For example, some unnecessary and high-risk ports can be blocked. For some necessary and risky ports, such as ports 3389 and 80, we can set them as non-special secret ports by modifying the registry, so that the security hidden dangers of server ports no longer exist.