After we set up a small Internet cafe, network maintenance is very important in order to make the Internet cafe work normally. Due to the complexity of network protocols and network devices, many failures are not as simple as solving a single machine failure. The location and elimination of network faults requires long-term knowledge and experience accumulation, as well as a series of software and hardware tools, and more needs your wisdom. Therefore, learning more about the latest knowledge is what every network administrator should do.
A, troubleshooting processBefore you start troubleshooting, it's a good idea to prepare a pen and a notepad, and then carefully record the symptoms. Be sure to pay attention to the details when observing and recording, and eliminate large network failures. This is also true for small network failures of more than a dozen computers, because sometimes the smallest details make the whole problem clear.
1. Identify faults
As an administrator, before you troubleshoot, you must know exactly what is wrong with the network, you can't share resources, you can't find another computer, and so on. Knowing what is wrong and being able to identify it in time is the most important step in successfully troubleshooting. In order to compare with the fault phenomenon, as an administrator you must know how the system works under normal conditions. Conversely, you are not good at locating problems and faults.
When identifying a fault, you should ask the operator the following questions:
(1) What process is being run when the recorded fault phenomenon occurs (ie, what the operator is doing with the computer).
(2) Has this process been run before?
(3) Was the previous operation of this process successful?
(4) When was the last successful operation of this process?
(5) Since then, what has changed?
With these questions to understand the problem, you can correct the problem.
2. Detailed description of the fault phenomenon
A detailed description of the fault phenomenon is particularly important when dealing with problems reported by the operator. If you only rely on their side of the word, sometimes it is difficult to draw conclusions, then you need the administrator to personally operate the program that just went wrong, and pay attention to the error message. For example, when browsing with a web browser, no matter which website you type, you will return information such as "This page cannot be displayed." When the ping command is used, the timeout connection information is displayed regardless of which IP address is pinged. Error messages such as this will provide a lot of valuable information to narrow down the problem. Before troubleshooting this, you can perform the following steps:
(1) Collect information about the fault phenomenon;
(2) A detailed description of the problem and the phenomenon of the fault;
(3) pay attention to the details;
(4) Write down all the questions;
(5) Do not rush to conclusions.
3. List the reasons that may lead to errors
As a network administrator, you should consider the reasons why you can't view the information, such as network card hardware failure, network connection failure, network device (such as hub, switch) failure, improper TCP/IP protocol settings, and so on.
Note: Don't worry about the conclusions, you can sort these reasons by priority according to the possibility of error, and eliminate them one by one.
4, narrow the search scope
Test all the listed causes of errors one by one, and do not judge whether the network in a certain area is normal or abnormal according to one test. Also, don't stop on the first mistake that you think has been fixed, until the end of the test.
In addition to testing, network administrators should also pay attention: Do not forget to look at the LED indicators on the network card, Hub, Modem, router panel. Normally, a green light indicates that the connection is normal (Modem requires several green and red lights to be lit), a red light indicates a connection failure, and a non-light indicates no connection or no line. Depending on the size of the data traffic, the indicator light flashes quickly and slowly. At the same time, don't forget to record all the means and results of observation and testing.
5, isolation error
After some of your tossing, you basically know the fault location. For computer errors, you can start to check if the computer network card is installed, whether the TCP/IP protocol is installed and set correctly, and the web browser connection. Set whether it is appropriate to wait for anything related to known failure phenomena. Then the only thing left is to troubleshoot.
Note: When opening the case, don't forget the danger of static electricity to the computer, and properly disassemble the computer parts.
6, failure analysis
After processing the problem, as a network administrator, you must also figure out how the fault occurred, what caused the fault, how to avoid similar faults in the future, draw up corresponding countermeasures, take necessary measures, and formulate strict Rules and regulations.
B, the cause of the failureAlthough the causes of the failure are various, but in general, it is nothing more than hardware problems and software problems. To be more precise, these problems are network connectivity issues, configuration file options, and network protocol issues.
1, network connectivity
Network connectivity is the first reason that should be considered after a failure occurs. The problem of connectivity usually involves devices such as network cards, jumpers, information outlets, network cables, hubs, modems, and communication media. Among them, the damage of any one device will cause the network connection to be interrupted. Connectivity is usually tested and verified with software and hardware tools. For example, when a computer cannot browse the Web, the first thought that arises in the minds of network administrators is the problem of network connectivity. Is it true? Can be verified by testing. Can you see your online neighbor? Can I send and receive emails? Ping to get other computers in the network? As long as one of the answers is "yes", then it can be concluded that there is no problem with the connectivity of the machine to the Hub. Of course, even if you answer "No", it does not mean that connectivity is definitely a problem, but it may be problematic, because if there is a problem with the configuration of the computer's network protocol, the above phenomenon will occur. In addition, it is not a bad idea to see if the indicator light on the network card and the Hub interface is blinking or blinking.
After eliminating the possibility of failure due to improper configuration of the computer network protocol, you should check whether the indicator of the network card and the hub is normal, and measure whether the network cable is unblocked.
2, configuration files and options
Servers and computers have configuration options, and configuration files and configuration options are not properly set, which can also cause network failures. If the server permissions are not set properly, the resource will not be shared. Improper configuration of the computer network card will result in failure to connect. When all the services in the network are not implemented, you should check the Hub.
Solar Connector,Solar Dc Pannel Branch Connector,Solar Dc Connector,Solar Dc Branch Connector
Shenzhen Hongyian Electronics Co., Ltd. , https://www.hongyiancon.com