Excluding the server bizarre failure case two

When the same server is used for different service applications, the failures they may encounter are quite different. Some faults may seem strange! But these strange server failures often make us ordinary networks. Managers should deal with the lack of skills, which ultimately affects the efficient operation of the server. In view of this, we should start from the practical point of view, and learn more ways and ideas to eliminate the special faults of the server, in order to ensure that when the server encounters a rare fault in the future, it should be calmly dealt with. This does not, put the following article author experienced two strange troubleshooting process server contributed out to satisfy all our friends!

1, the server can not become a secondary domain controller unit

LAN There is a primary domain server, which is installed with the Windows 2000 Server operating system. Recently, due to work needs, the unit bought a new server and installed Windows 2003 Server in the server. Now the unit plans to install the new one. The Windows 2003 Server server is used as a secondary domain controller in the LAN, but when the network administrator tries to join the server to the primary domain server with the Windows 2000 Server system, the Active Directory Installation Wizard appears on the screen. Can't continue, because Lin is not ready to install Windows 2003 Server, it is clear that Windows 2003 Server server has trouble getting a secondary domain controller. That prompted the face of such a failure, how do we deal with in order to make Windows 2003 Server domain controller server role reversal successfully completed the task it?

by searching for related failures prompted the author to identify the cause of the fault The main reason is that the Windows 2003 Server server contains the latest version of the domain architecture, while the Windows 2000 Server primary domain controller uses a relatively low domain architecture version. When Windows 2003 Server servers try to join the primary domain controller, they are found between them. The version of the domain schema is inconsistent and eventually the Active Directory Installation Wizard cannot continue to run. To eliminate the above fault tips ensure smooth Windows 2003 Server server added to the primary domain controller in order to complete the purpose of conversion of the secondary domain controller role, we might as well step by step in accordance with the following steps:

first to Log in to the Windows 2000 Server primary domain controller as a super administrator, and then check if the server has the SP4 patch installed on the computer system. If it is not already available, we must go to Microsoft's official website to download and obtain the SP4 patch. Instead of downloading the patch from other unknown sites, downloads from unknown sites can easily pose a security risk to the server. After downloading the SP4 patch, install it to the Windows 2000 Server primary domain controller in the correct way. After the installation is complete, restart the computer system where the primary domain controller is located. This article is from the computer software and hardware application network. Www.45it.com Please indicate the

Secondly, unplug the network connection cable connecting the Windows 2000 Server primary domain controller from the NIC interface to ensure that the primary domain server is disconnected from the LAN network. You can prevent the illegal network access operation from posing a potential threat to the primary domain server.

Locate the installation CD of Windows 2000 Server and place the CD in the CD-ROM drive where the primary domain controller is located, and then double-click The CD-ROM icon in the My Computer window, enter the root directory window of the CD, find the Adprep.exe file under the I386 subfolder, and copy the file directly to the hard disk of the computer where the primary domain controller is located;
< BR> Next, in the system desktop of the primary domain controller, use the mouse to expand the "Start" and "Run" items one by one, and open the running pair of the system. In the dialog box, enter the string command "cmd", click the Enter key and the system will automatically switch to the MS-DOS command line state; enter the string command "adprep /forestprep" in the DOS command line, click back After the key is pressed, the system will automatically update the existing forest-wide information of the primary domain controller. After a while, the system will display the prompt information for successful update;

Then continue to input the string in the DOS command line. The command "adprep /domainprep", after clicking the Enter key, the system will automatically update the existing global domain controller's existing global information. After a while, the system will also display a message indicating that the update is successful.

After confirming that the above string command is successfully executed, re-insert the network cable into the NIC interface of the primary domain controller to ensure that the primary domain controller is connected to the LAN network; DOS window interface, and restart the server system. After the main domain controller restarts successfully, return to the computer with the Windows 2003 Server system installed, and then click the "Start" and "Run" commands one by one in the system desktop, and the system running dialog box that appears after it. In the input string command "dcpromo", after clicking the Enter key, the Windows 2003 Server server can be successfully added to the primary domain controller, thus becoming a secondary domain controller in the LAN.

2, the server can not steady work

unit two years ago bought a HP Proliant DL385 server, which has been stable since the buy back after we provide for the "service", but recently I don't know why, the server often appears to be inexplicably restarted or crashed. In serious cases, the failure of CMOS information is lost. These faults occur one after another, which has affected our daily work. The HP manufacturer's technical support hotline has to be dialed, and the other engineer has answered the trouble according to the fault phenomenon provided by the author. According to the answer from the professional technicians, the author performed the CMOS discharge operation and the grounding resistance test operation on the server, but Such efforts have not changed the performance of the server. In addition, HP technical support staff also specifically mentioned that dust may also cause unstable server performance. He reminded me that once it is found that too much dust is accumulated in the server, you must ask the local HP after-sales personnel to dedust the server. According to this clue, the author quickly opened the chassis of the server. Sure enough, the inside of the server was covered with a thick layer of dust. At this time, I recalled that when the HP Proliant DL385 server was just bought back, it was catching up with the unit room decoration. The operating environment is very poor, the author secretly believes that most of this dust is left at that time; carefully look at the dust in the server, I found that some locations of dust, has completely "swallowed" the chip inside the server. Considering that the unit is in a hurry to use the server and contact the local HP after-sales personnel, they also claimed that there is no manufacturer to notify the on-site service to charge a special service fee, so I decided to clean and clean the dust in the server. I don't do it, I don't stop it, the author carefully removes the board from the server, then finds a soft fine brush, carefully cleans the dust inside the server, and waits until the dust is completely cleaned. All the removed board cartoons are restored to their original positions. Finally, the server is powered on and the server is powered on for a period of time. As a result, it is found that the server restarts or freezes at intervals. In view of the cause of the failure, the author believes that the dust covering the surface of the server chip has exerted no small influence on the circuit signal of the built-in board or chip of the server under the action of rainy and humid environment in summer, which ultimately affects the normal and stable operation of the server. Once the dust covering the inside of the server is cleaned, the circuit signals of the various boards or chips of the server are immediately restored, and the performance of the server is immediately stabilized.