Error logs are files that record the events and errors that occur on a server or a network device.
They can provide valuable information about the cause and the time of the outage, as well as any warnings or alerts that preceded it. Analyzing the error logs can help the administrator narrow down the possible sources of the problem and identify the best course of action to resolve it. The first step in troubleshooting a network is to identify the problem. As a part of this step, the administrator should gather information about the current state of the network using the network troubleshooting tools that are available. One of these tools is the error log viewer, which can be accessed through the server's operating system or a network monitoring software. The administrator should look for any entries that indicate a failure, a crash, a timeout, or an exception in the error logs. The administrator should also note the date and time of the entries, as well as the severity and the frequency of the errors.

1. Identify the problem.
2. Establish a theory of probably cause. (Question the obvious)
3. Test the theory to determine cause.
4. Establish a plan of action to resolve the problem and implement the solution.
5. Verify full system functionality and if applicable implement preventative measures.
6. Document findings, actions, and outcomes.