The server is originally installed with Terminal Services and PCANYWHERE, and later uninstalling PCANywhere, but add another user who has additionally Administrators permission. But today is very tragic, this user always prompts the maximum range of connections. After the Administrator logs in to the terminal, they can only look at the desktop, and there is no response. Fortunately, the Web services and FTP services are still normal. Let the server restarted in Windows 2000 to call the shell32.dll file in Windows under System to implement shutdown, such as "Indir / Rundll32.exe Indir / System / shell32.dll, ShexitWindowSex 8", but unclear the meaning of specific parameters Worrying that in case of shutdown rather than reboot, it is still using WinXP's own Shutdown.exe insurance, and its method is clear: shutdown.exe -a cancel shutdown shutdown.exe -f forcibly shut down the application. Shutdown.exe -m // Computer Name Controls Remote Computers. Shutdown.exe -i shows the graphical user interface, but must be the first parameter of Shutdown. Shutdown.exe -l logs out of the current user. Shutdown.exe -r shuts down and restarts. Shutdown.exe -t Time Sets the shutdown countdown. Shutdown.exe -c "Message Content" Enter the message content in the shutdown dialog (not over 127 characters). Considering that the default server opens IPC $, and you know the password of Administrator, try to use NET USE // IP / IPC $ "Password" / user: "administrator" to connect the server, the result is a 53 error, no network path. Want to go up the Tumacroplasses, the server has installed anti-virus software, and it must not. Already let the netizen pass Shutdown.exe to me again to the server, how to run it? Thinking that I log in to FTP is the system administrator account, so under the CMD window: ftp: // Server IP Username Password Login Success CD Shutdown.exe The directory quote site exec shutdown.exe -r result is Permission Denied. Original I didn't give the execution permission. Add a remote computer on this unit serv-u, use the system administrator account password, so you can manage the Serv-U on the server, add execution permissions to the account. Retry the previous order, result 200 exec command successful (TID = 33). But the server actually didn't respond, fainted! When there is any other method, the Serv-U prompts to disconnect with the server, hahaha, after a while, the server is restarted!