VNC Remote Desktop solves server failure in three cases

Intermediary transaction http://www.aliyun.com/zixun/aggregation/6858.html ">seo diagnose Taobao guest cloud host technology Hall

The author for many years engaged in operation and maintenance work, operation and maintenance work peacetime pressure is not, but every month have a few days-server ventilation! Our company installs the Windows system the server rarely runs continuously for more than three months, the regular restart is almost necessary, otherwise freezes, the blue screen, the response odd slow and so on all sorts of problems all come.

The time to restart the server command to the timer task, to reduce the server failure does help, but only to cover up the problem rather than the final solution, the price is "pumping to death"-server crash or even can not boot operating system, then will be more miserable, the middle of the night had to go to the computer room If Catch a holiday, travel, back home, it is miserable, for this I even repeatedly moved the idea of a career! A friend recommended the author use hardware VNC to solve the sudden, the author through the use of a period of time and experience to accumulate the sense of operation and maintenance of a lot of pressure relief, especially in this introduction to all of you in the transport industry to help the early escape from the abyss of misery.

When it comes to VNC, most of the operators are familiar with the old Remote Desktop tool, which is known for supporting multi-platform and has become the de facto standard for remote desktops, including the famous RealVNC, TightVNC, and so on. Hardware VNC is the hardware that integrates VNC server-side functionality, it runs independently of the managed server installation and does not need to install any VNC servers on the managed server, just connect the hardware VNC to the managed server, and then connect the managed servers through a variety of VNC clients. Compared to the various software VNC, hardware VNC's greatest advantage is that it does not rely on the server, through hardware VNC can remotely configure the BIOS, view the blue screen error, the server connecting the card, and even the server is still connected. Here is a brief introduction to the use of hardware VNC to solve the Windows 2003 server failures of three instances, including some of the author summed up some of the tips, I hope that you will be able to carry the same fellow to help and inspire:

Instance one, server CPU or memory footprint high, slow response

Solution: As soon as possible to occupy CPU or high content of the exception process and end, can not be considered to restart the server.

What to do: You can imagine the server response has been very slow at this time, the server running VNC or Remote Desktop services are often unable to connect. At this point the hardware VNC should be connected to the server, taking into account the slow response of the server caused difficult to operate, should be reduced mouse operation, as far as possible through the shortcut key to complete the operation. The author concludes the quickest sequence of operations is (1) through the CTRL+SHIFT+ESC key combination of Investigation Task Manager, (2) through the SHIFT key switch to the Process page, (3) to find the server CPU and memory process usage of the process of using an exception, through the ALT key to end. According to this process, at least 2 or 3 keystrokes can be used to remove the exception process K, and then identify the specific cause of the exception or restart the corresponding process. There is a small trick, that is, try to connect the hardware VNC through the TightVNC, and then press the TightVNC inside the "Ctrl tool" and then press the SHIFT+ESC key, so that you can pull out the task manager, try you understand, do not explain.

If you cannot find the problem process, you can only choose to restart the server to restore the fastest failure, the author uses the quickest operation is: (1) TightVNC under the "Windows Banner button" click on the R key, (2) In the Run dialog box Input command ' Shutdown-r-f-t 00 ' After pressing ENTER, the system will reboot immediately.

Instance II, server poisoning or attack caused network bandwidth to be filled

Solution: Disable the network interface, identify specific reasons and then re-enable

What to do: under normal circumstances (such as the server receives SYN flood attack causes the maximum number of connections to fill), Hardware VNC network connection is not affected, you can directly remotely control the managed host, in the "Network Neighborhood" icon click the right mouse button Select "Properties", the Internet connection window opens, Select "Disable" by clicking the right mouse button after selecting the appropriate network connection. Some special circumstances (such as server poisoning after a large number of local area networks), hardware VNC network connection bandwidth is also affected, at this time the hardware VNC Remote Desktop screen refresh will be relatively slow, it is recommended to operate through the shortcut keys. The author's practice is: (1) under the TightVNC Press "Windows Banner button", click R, type "cmd+ carriage return", at this time will call out the DOS command prompt line window; (2) Type the command ' netsh interface set interface in the DOS window Name= "Eth0" admin=disabled, you can disable network connections with a network name of Eth0, and the "eth0" section of the command needs to be replaced with the appropriate network connection name. Recommended in the day-to-day maintenance of the appropriate preparation, the "local Connection *" Chinese network connection name replaced by the "eth*" style of English shorthand, is ready to use at the critical moment. In addition, you can view the network connection name and current state by command ' netsh interface show interface ' command, through the command ' netsh interface set interface name= ' Eth0 ' admin=enabled ', you can re-enable network connection eth0.

Instance three, Server blue screen

Solution: Record blue screen information, try to reboot the server, and enter Safe mode if unable to boot

Specific: Blue screen case, hardware VNC can see the reality of the screen information, sometimes this part of the information can indicate the specific error of the hardware driver or DLL program, in such cases can be copied through the VNC client screen, left for later analysis use ( Of course, in many cases, Windows blue screen hints are of no value. Then we can contact the engine room, help us to restart, generally speaking, restart can restore more than 80% of the fault. If you reboot and go to the operating system again blue screen, then we can only with the room to say "Sorry, trouble you, can again give a reboot ...", and then stare at the VNC client, once see the server boot screen began to F8, choose to enter the Safe mode, and then slowly fix the specific fault good. Incidentally, a small experience, this way can also know exactly whether the computer room network management to restart the server, this use is not much explained, understand.

The above is the author summed up some of the troubleshooting of server failures, some of the small experience and skills, if you have a better solution to the maintenance of friends, or in the actual operation of the work of any doubt or difficulties, please feel free to contact with the author to communicate with each other to learn and exchange!