An effective way to remotely reboot a server

1. Obtain the administrator privileges of the remote server.

The IP address of the net use server"Administrator password" /user:administrator

2. Use the shutdown command to remotely restart the server.

Shutdown r t 0 m server IP address.

In fact, the remote desktop function of Windows 2003 Server is very powerful, it can facilitate us to perform all kinds of operations, modify the configuration, and operate the server as if it were native. Of course, there is no problem with shutting down the computer, restarting the computer, logging out and other system operations. Therefore, the problem encountered by the above netizen should be the failure of the server itself, not the fault of the remote desktop itself.

According to this netizen's prompt, we can know that his session is interrupted after he completes the remote restart operation, which means that the server has begun to enter the preparation stage for the restart operation, but why did the subsequent restart operation fail? There is only one reason for this - that is, a program or process is preventing the restart operation from running, which means that the system is running some programs that cannot be automatically shut down, resulting in the restart not being completed smoothly.

So how to solve this problem? We can think of the symptoms encountered when we usually operate the computer, many times when we restart the computer or shut down the computer, there will be a "so-and-so program cannot be closed, please press the force close button or wait for a period of time and try to close the operation again", which is the same as the problem encountered by the netizen above. The difference is that you can directly click the "Force Close" button to complete the restart operation when operating on the machine, but on the server, because the remote desktop program will end before these difficult processes, we can't click the "Force Close" button to operate.

Knowing the root cause of the problem, we can solve it in two ways.

First of all, we should operate in the server room instead of remotely connecting to the server, and then perform a reboot operation on the server's console to see if there is a prompt message, if there is, delete the corresponding program according to the prompt, only after deleting the troublesome program can we ensure that the remote restart of the server is successfully completed.

This should not be the case.

The remote desktop connected to the 3389 can be completely shut down. It could be some of your programs. Reasons why Windows won't shut down. You can take a look at the progress.

Or fix the system.

It is recommended that you host the server to an IDC provider, and someone is in the computer room 24 hours a day, all year round.

Collective Ideas Network is a good choice for you.

Dude, I suggest you rebuild the system from the ground up.

Summary. A server is a type of computer that runs faster, has a higher load, and is more expensive than a regular computer. The server provides computing or application services to other client computers in the network, such as PCs, smartphones, ATMs and other terminals, and even large devices such as train systems.

Hello, it's an honor for me to answer your questions, it will take a little time to sort out the answers, please be patient

The server is a kind of backup computer, which runs faster, has a higher load, and is more expensive than ordinary computers. The server provides computing or application services for other client machines in the network, such as PCs, smartphones, ATMs and other terminal imitation models, and even large devices such as train systems.

If my answer is helpful to you, please give a thumbs up (comment in the lower left corner), look forward to your like, your efforts are very important to me, and your support is also the driving force for my progress. If you feel that I am satisfied with the answer of Fu Lu, you can click on my avatar for one-on-one consultation. Finally, I wish you good health and a good mood!

Here's how to fix the problem:

1. First of all, the user needs to open the bright side of the computer desk, then enter "mstsc", and then click the "OK" option;

2. Then the user needs to enter the IP address of the server in the pop-up "Remote Key Tribrato Desktop Connection" window, and then click the "Connect" button;

3. The user needs to enter the username and password of the server, and then click the "OK" option to connect to the server;

4. Then the user needs to click on the "Start" and "Run" options in the lower left corner of the remote desktop, enter "cmd", and then click the "OK" option;

5. Users need to enter "iisreset" in the pop-up window, and then click the "OK" option to let the remote server automatically restart and fail.

1. To operate on the computer, win key + R, enter mstsc, and then click OK.

2. In the pop-up "Remote Desktop Connection" window, enter the IP address of the server in the computer box, and then click the "Connect" button.

3. Enter the username and password of the server, and then you can connect to the server.

4. Click "Start" and "Run" in the lower left corner of the remote desktop, enter "cmd", and confirm.

5. In the pop-up window, directly enter "iisreset" and press enter to confirm.

6. As above, the server can be successfully restarted, as shown in the following figure:

Is the corresponding option in the service automatically enabled?

You can turn off the firewall temporarily by excluding it first. Turn on the remote connection function to allow any version of the operating system to connect.

Check that the telnet service is started properly.

In addition, there is a problem in 2008, that is, after restarting, when not logged in, it may not be possible to connect remotely, and it can be connected normally after logging in with the administrator, judging that it may be because the corresponding service is not started before logging in. It's not certain if it's normal at this time.

Yesterday I saw a good article on the Pacific Computer Network "Wuhan IDC Computer Room Remote Power Control Practical Case Analysis", which was written by Tang Hua, talking about how to restart the server manually without the computer room administrator in the state of server crash, but by remote hardware to wake up the server to turn on and off, restart and return to normal, I feel very inspired, I no longer have to trouble the computer room administrator to help me restart the server, no longer have to wait for the computer room administrator to lazily go over to restart, as long as the server crashes, Immediately you can reboot your own hardware back to normal,Whether the server is shut down or crashed,It's effective,It's really practical,Introduce it to everyone,I hope to add the essence。 The original text, please take a look at it and say that it doesn't work.,Are there any advantages and disadvantages?,I'm going to do this.,Launched the "server crash zero waiting for restart service",Please give some advice.,Do you think it's feasible?

Step 1: When the remote desktop service cannot be used smoothly, the first thing we need to determine is whether the server is really dead. We can ping the IP address of the target server to see if it is smooth or access the relevant network services on the server to see if it can be used smoothly, and of course, we can also judge whether its network access is smooth by the UNC address.

Step 2: Next, we use the shutdown command to restart the server through the network if the remote desktop cannot be connected smoothly. To do this, run the "shutdown m server IP address R" command prompt window so that the server will automatically restart.

In the ping -t command window, we will also see that the destination network connection has changed from unblocked to requeset timed out, which means that the destination server is already restarting. (pictured).

If you have not connected to the destination server before, you need to use "et user server IP address" password "user:username" to connect before executing the shutdown command, for example, "net user 123456 user:administrator" (administrator username, password 123456).

The shutdown can only function when the corresponding ipc$ connection is established, and the destination server will not restart obediently if the shutdown is executed without connecting.

In the default security policy of Windows XP operating system, only users in the Administrator group have the right to shut down or restart the computer from the remote end, and under normal circumstances, when accessing the computer from other computers in the local area network, only the guest user has the right, so when we execute the above command, there will be a "access denial" situation.

Once you've found the root cause of the problem, the solution is as simple as giving the guest user the permission to remotely shut down the guest computer (a computer that can be remotely shut down, such as Sunbird above). This can be achieved using Local Security Policy in Windows XP's Group Policy or Administrative Tools. The following is an example of Group Policy

Remote shutdown. 1. Click the Start button, select Run, enter in the dialog box, and then click OK to open Group Policyr.

2. In the left pane of the Group Policy window, go to Computer Configuration, Windows Settings, Security Settings, Local Policies, and User Rights Assignment.

3. In the right pane of the Group Policy window, select Force Shutdown from Remote System and open it by double-clicking.

4. In the pop-up dialog box, it shows that only members of the "administrators" group have the right to shut down from the remote computer. Click the Add User or Group button at the bottom of the dialog box, enter guest in the new dialog box, and then click OK.

5. At this time, a "guest" user is added to the attribute of "Force shutdown from the remote system", and click "OK".

6. Close the Group Policy window.

After the above operations, we have granted the guest user of the computer Sunbird the permission to remotely shut down. In the future, if you want to remotely shut down your Sunbird, simply enter the following command into another computer on your network with Windows XP:

shutdown -s m sunbird -t 30 (other parameters are used in the same as above).

At this time, a "System Shutdown" dialog box will be displayed on the screen of the Sunbird computer, saying "System is about to shut down. Save all your running work and log out. Unsaved changes will be lost.

The shutdown is initiated by Sunbird Guest. There is also a timer below the dialog box that shows how much time is left until the shutdown. While waiting for the shutdown time, the user can also perform other tasks, such as closing the program, opening files, etc., but cannot close the dialog box unless you use the shutdown a command to abort the shutdown task.

Remote reboot. If you want to implement remote reboot in Windows XP, then you also need to use the "shutdown" command, open Remote Assistance, and enter it in the case of remote desktop.

win+r - Run, enter "shutdown -r -t 0" to restart the machine.

There is a software, but it requires the network card of the computer itself to be able to support booting. The software can be set up to find your unit's machine through the network setting, and a fixed IP address can be set. But I can't remember that software, it seems to be a remote diagnosis from Microsoft.

Run the input inside; shutdown

However, it is necessary to have the user password of the remote server.