Five tips for Remote Windows Server Management

Managing a server is not easy, except for the "server tool software for Top Ten website administrators" I mentioned yesterday, we may also encounter some inexplicable problems and errors. Today, I will introduce some of the five Windows 2003 Server management skills that the moonlight blog has encountered and summarized during normal management, hope to help you.

1. Terminal Protocol Error

If you use notepad or another editor to edit some Chinese characters on a remote terminal, the server will prompt "the session will be interrupted due to a protocol error. Connect to the remote computer again ". Then, connect to the server, and the server will be interrupted and exited.

Solution: if there are two administrator users on the server, log on with another administrator user, and then disconnect from the error, or use another user to restart the server. If there is only one administrator user, try to modify the local display to the minimum resolution, such as 800X600, and then connect to the Remote Desktop. If you can connect, immediately log off the current user.

2. FileZilla cannot connect to IIS's FTP

When FileZilla is used to connect to the FTP service of IIS, sometimes the logon is successful, but the message "failed to read the Directory List" appears. At this time, check whether ports 20 and 21 are enabled on the server. If yes, modify the transmission mode of the local FileZilla to "active.

3. Regularly restart the server

A large website may have a high resource load after running for a period of time due to system resource restrictions. In this case, we may consider automatically restarting the server every day and automatically restarting the server for use, you can use the task scheduler to complete this task. Click the attachment-System Tools-task scheduler and add a task to automatically execute the shutdown program every day. shutdown is the built-in shutdown program of Windows Server 2003, run the "shutdown-r-f-t 5" command (the r parameter indicates restarting the server, and the f parameter indicates forcibly disabling system processes and applications, t parameter is used to specify the time when the system shuts down the countdown) to enable automatic restart. Even if the server system encounters a system process that cannot be shut down, it is forced to shut down.

4. The SMTP provided by IIS cannot send emails.

Windows Internet Information Service (IIS) comes with an SMTP (Simple Mail Transfer Protocol) service, but after it is installed, it sends an email with the error message "Unable to relay for user () domain.com ". This may be due to a problem with the default Mail Relay Settings. Select SMTP-access-relay restriction, select "only the following table exists", and then restart SMTP.

5. prevent spam from being sent by others

After SMTP is enabled on the server, it may become a victim of external spam without any restriction. The simplest restriction is to disable the mail sending port 25 on the server. in the TCP/IP protocol attribute, select "advanced"> "TCP/IP filtering attribute". TCP port 25 is not allowed.

The above are some tips for effectively managing servers summarized by the moonlight blog. Although you may have mastered many of these skills, there are still many skills for server management, if you have some novel tips or tips, please leave a message below to tell us that you may have encountered these problems.