Five tips for managing Windows servers remotely

Management of a server is not a simple thing, in addition to the "Top ten Webmaster Server Tools" I mentioned yesterday, we may also encounter some puzzling problems and errors, today, I will introduce some moonlight blog in peacetime management encountered and summed up the five Windows 2003 Server management skills, hope to be helpful to everyone.

　　1. Terminal protocol error

If you edit some Chinese in a remote terminal with Notepad or another editor, the server prompts "due to a protocol error, the session will be interrupted." Please try connecting to the remote computer again. Then you connect to this server, and the protocol error continues to occur, and then the exit is interrupted.

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

　　2, FileZilla not connected to IIS FTP

Use FileZilla to connect to IIS FTP service, sometimes login successfully, but there is a message "Read directory List failed", then please confirm that the server has opened 20 and 21 ports, if opened, the local FileZilla transfer mode to "active" can be changed.

　　3. Reboot the server periodically

Relatively large site, perhaps due to system resource constraints, running for a period of time after the resource load is very large, then we may consider to automatically restart the server every day, automatically restart the server can be used, this can use the task plan to complete, click the attachment-System Tools-task planning, add a task, The shutdown program is automatically executed daily, shutdown is a shutdown program with Windows Server 2003, using the command "Shutdown-r-f-t 5" (where the R parameter indicates a reboot of the server, and the F parameter indicates that the system processes and applications are forced to shut down. The T parameter is used to specify the time when the system shuts down for automatic restart, and the server system shuts down even when it encounters a system process that cannot be shut down.

　　4. IIS cannot send mail with its own SMTP

Windows Internet Information Services (IIS) comes with an SMTP (Simple Mail Transfer Protocol) service, but after it is installed, send a message prompting error message "Unable to Relay for user (at) domain.com." This may be a problem with the default mail relay settings, select SMTP-Access-Relay restrictions, select only the following tables, and then restart SMTP.

　　5, prevent others to send spam

When SMTP is opened on the server, it may become a victim of external spam if it is not restricted, and the simplest limit is to turn off mail delivery port 25 on the server. In the TCP/IP protocol properties, select the Advanced-option-TCP/IP Filter property to disallow TCP 25 ports.

The above is the Moonlight blog summed up some of the effective management of the server's tips, although you may have mastered many of these skills, but there are a lot of server management skills waiting for you to sum up, if you have some new tricks or tips, please leave a message to tell me below us, Believe that these problems you may have encountered in peacetime.