Listed in the Win 2003 operating system wonderful question and answer four

Windows Server 2003 is one of the most popular server operating systems. Although it provides powerful network service functions, and is easy to use, how to remotely force shutdown, but it also has many problems in many aspects, today I will explain the four questions and answers of Win 2003 operating system for everyone, I hope to Windows Server Users of 2003 are a little reference and reference.

How to remotely shut down

Q: The LAN server I manage is Windows Server 2003, and the clients are all windows 2000. How can I forcibly shut down a designated computer remotely in a LAN?

A: There are many ways to implement it. Here is the Windows Server 2003 built-in "management" function to explain the implementation process.

Right-click and click the "My Computer" icon, select the "Manage" item, right-click in the pop-up "Computer Management" window and click "Computer Management" (local ), select the "Connect to another computer" in the pop-up menu, and enter the IP address of the computer to be closed in the pop-up dialog box. In the "Computer Management" window, the "Computer Management (Local)" item is automatically switched to the "Computer Management (Remote IP Address)" item, select the item and right click to enter its properties panel. “Advanced” tab settings interface, click the "Start & Restore" section of the "Settings" button, click on the “ Shutdown & rdquo; button in the pop-up panel. Then in the pop-up "Shutdown" setting panel, first select the "Operation" section "Turn off the power" item (if supported), and then select "Forced application to close" "some" After the item (possibly losing data), click the “OK" button to remotely shut down the specified computer system and power.

Unable to send a message to the server

Q: My LAN is composed of the server Windows Server 2003 and the client Windows 2000. I found that the client user cannot use the "Net Send" command. The server sends the message, but the server can use the "Net Send" command to send a message to the client user. Why is this?

A: In order to avoid being harassed by some mischievous messages, it is closed in Windows Server 2003. The message receiving service. Therefore, the server cannot receive the message from the client. The solution is to double-click the “Services” item in the “Administrative Tools” box, double-click the “Messenger” item in the pop-up service list window, and set “Enable Type” in the pop-up Properties window. “Auto & rdquo;, set “service status” to “start”

Error when starting web service

Q: My company's server is Windows Server 2003. When I start the web service in IIS 6.0, the system pops up "Address already in use" error message. After checking the log, I found that there is "Event ID: 115", "Source: w3svc", what is the cause of this? How to solve it?

Answer: First of all, you must understand IIS 6.0 It has been separated into three modules, namely http.sys, w3svc and w3core. Among them, http.sys is a kernel mode port listener and request receiver, w3svc is used to configure http.sys, and w3core is a web application loader. Knowing this, it is easy to see that w3svc configuration http.sys error. Based on the error information and experience, it is initially determined that the TCP port 80 that may be bound by the Web server is being used by a service or application (such as MSProxy). We can use the following solution:

First use the Netstat -ano command to see who is using the PID on port 80, and then check the PID through the task manager (in the task manager, enter "process" Tab settings interface, and then click “ view → select column & rdquo; menu item, check the PID item in the pop-up dialog box) is the application, find out after disabling or uninstalling the service that is using port 80 or Application, then re-enable the Web site.

Cannot create a new user in the domain

Q: Why can't I create a new user in the new domain of Windows Server 2003? I looked at it and found that the prompt message is "The password does not meet the requirements …… & rdquo; How to solve it?

In Windows Server 2003, there are certain requirements for the password setting of the domain. If the complexity of the password does not meet the requirements of the domain password setting, the user will not be successfully established. A standard password complexity requirement is: a. does not contain all or part of the user account name; b. the length is at least six characters; c. at least one uppercase English letter and one lowercase English letter, and 0~9 One number. In addition, you can have non-alphabetic characters (such as !, $, #, %). Based on this, it can be known that a standard password should be “sHYZHONG77”.