Network Management Combat: Troubleshooting The two cases of bizarre server

When the same servers carry out different service applications, they may encounter a very different breakdown, even some of the fault seems to be bizarre! But these strange server failures, often make our ordinary network management personnel to cope with the problem, and ultimately affect the efficient operation of the server. In view of this, we should be more from the actual combat point of view, more master some of the methods and ideas to eliminate the special server, in order to ensure that in the future when the server rare failure to respond calmly. This is not, this article on the author has experienced the two server rare troubleshooting process to contribute to the Feast of friends!

1. Server cannot be a secondary domain controller

The Unit local Area network has a primary domain server, which is installed with a Windows server operating system, and recently purchased a new server and installed Windows 2003 server in the server, due to work needs. The unit now intends to use the newly erected Windows 2003 server as a secondary domain controller in the LAN, but when network administrators try to add the server to the primary domain server that has the Windows Server system installed, the screen appears. The Active Directory Installation Wizard cannot continue because the forest does not have a fault prompt for installing Windows 2003 server, and it is clear that Windows 2003 Server servers are having trouble trying to become secondary domain controllers. So what can we do to get the Windows 2003 Server servers to successfully complete the Domain Controller role transformation task in the face of such a failure hint?

By searching for the fault prompt, the author finds that the cause of the failure is mainly the latest version of the domain schema in the Windows 2003 server servers, whereas the Windows Server master domain controller uses a relatively low domain schema version when Windows 2003 The server server's attempt to join the primary domain controller found that the domain schema version was inconsistent between them, resulting in the Active Directory Installation Wizard not being able to continue running. To eliminate the above symptoms and ensure that Windows 2003 Server servers are successfully added to the primary domain controller to complete the role conversion for the secondary domain controller, we may wish to proceed as follows: (Learn computer)

First log on to the Windows Server master domain controller as a super administrator, and then check the computer system to see if the server has the SP4 patch installed, and if not, we must go to Microsoft's official website to download the SP4 patch. And do not randomly to other unknown sites to download the patch, because the download from the unknown site is easy to bring security risks to the server. When the SP4 patch is downloaded, install it to the Windows Server master domain controller in the correct way, and restart the computer system where the primary domain controller is located after the installation is complete;

Second, unplug the network connection cable connecting the Windows Server master domain controller from the NIC interface to ensure that the primary domain server is detached from the LAN network, thus avoiding the potential threat to the primary domain server by illegal network access operations;

Below, locate the installation CD for Windows Server, and place the disc 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 to enter the root directory window of the disc. Locate the Adprep.exe file below the I386 subfolder and copy the file directly to the computer hard disk on which the primary domain controller resides;

Next, on the system desktop of the primary domain controller, with the mouse to expand the start, run the project, open the System's Run dialog box, and then enter the string command "cmd", click on the system will automatically switch to the MS-DOS command line state; Enter string command on DOS command line " Adprep/forestprep ", the system will automatically update the existing forest-wide information of the primary domain controller after clicking the ENTER key, and after a while, the system will be updated with a successful message;

Immediately after continuing with the input string command "Adprep/domainprep" on the DOS command line, the system will automatically update the existing domain-wide information for the primary domain controller after clicking the ENTER key, and after a while the system will also receive a prompt for updated success.

After confirming that the string command above is successfully executed, reinsert the network cable into the network card interface of the primary domain controller, ensure that the primary domain controller is connected to the LAN network, close the MS-DOS window interface, and restart the server system. Wait until the primary domain controller restarts successfully, then return to the computer that has the Windows 2003 Server system installed, and then click Start, Run, and then in the System Run dialog box that appears, enter the string command "Dcpromo", and then click Enter , Windows 2003 Server servers can be successfully added to the primary domain controller to become secondary domain controllers in the local area network.

2, the server can not stabilize the work

Two years ago the unit purchased an HP Proliant DL385 server, the server has been stable since the purchase of the "service", but recently did not know what the reason, the server often appear inexplicably restart or panic phenomenon, When there is a serious loss of CMOS information, these failures occur in a spate, has affected our daily work. Forced to dial the HP manufacturer's technical support hotline, the other engineers in accordance with the fault phenomenon provided by the author to answer the trouble; According to the Professional and technical personnel of the solution, the author of the server respectively CMOS discharge operation and grounding resistance test operation, However, this effort does not make the server's work performance a little bit improved. In addition, HP technical support personnel also deliberately mentioned that the dust may also cause server performance instability, he reminded me that once the server has accumulated too much dust, be sure to ask the local HP after-sales personnel to the server for dust disposal. According to this clue, the author quickly opened the server chassis shell, sure enough, the server covered with a thick layer of dust; When I recall the HP Proliant DL385 server just bought back, is catching up with the unit room decoration, the server's current operating environment is very poor, The author secretly thought that most of these dust may be left at that time; carefully look at the dust in the server, the author found that some of the dust at the location, the server inside the chip is completely "swallowed up". Taking into account the unit worried about the need to use the server, contact the local HP after-sales personnel, they also claimed that there is no manufacturer's notice of door-to-door service needs to charge a special service fee, so the author decided to do their own to the server in the dust cleaning, cleaning. Yibu, over Boots, the author carefully removed the relevant board from the server, then find a soft hair brush, carefully to the server inside the dust to clean, until the dust is all clean and clean, and then all the removed board back to the original location, finally connected to the server power, Let the server live for a period of time, the results found that the server every once in a while restart or panic phenomenon no longer occurs. The reason of its failure, the author thinks that the dust covered on the surface of the server chip in summer rainy, humid environment, has the server built-in board or chip circuit signal produced a small impact, and ultimately affect the normal stability of the server work; Once the dust is cleaned and covered in the server's interior, The circuit signal of each board or chip of the server is restored to normal immediately, so the performance of the server can be stabilized immediately.