Guide to Troubleshooting and its Types and Working.
                     GUIDE TO TROUBLESHOOTING, 
ITS TYPES AND WORKING
 Troubleshooting is the process of identifying what is 
wrong with these faulty systems when the problem is not 
immediately obvious.
Troubleshooting
Source: www.fiixsoftware.com
 Troubleshooting usually follows a systematic, four-step 
approach; identify the problem, plan a response, test the 
solution, and resolve the problem. 
 Steps one to three are often repeated multiple times 
before a resolution is reached.
Approach for 
Troubleshooting
Source: www.fiixsoftware.com
 The process is based on collecting as much information as 
possible from as many sources as possible to identify the 
most likely cause of the breakdown.
How is 
troubleshooting 
usually done in 
maintenance?
Source: www.fiixsoftware.com
 Unexpected equipment failure is the entire reason 
troubleshooting exists. 
 If assets never broke down without any clear signs of 
imminent failure, there would be no need to troubleshoot 
the problem.
Why does 
troubleshooting 
matter?
Source: www.fiixsoftware.com
STEPS TO TROUBLESHOOT A 
NETWORK
 Before you start trying to troubleshoot any issue, you want 
to have a clear understanding of what the problem is, how 
it came up, who it’s affecting, and how long it’s been going 
on. 
Issues can arise at 
numerous points 
along the network
Source: www.dnsstuff.com
 When you’re beginning the troubleshooting process, 
check all your hardware to make sure it’s connected 
properly, turned on, and working. 
Check the hardware
Source: www.dnsstuff.com
 Open the command prompt and type “ipconfig” into the 
terminal. The Default Gateway (listed last) is your router’s IP. 
 If your computer’s IP address starts with 169, the computer 
is not receiving a valid IP address.
Use ipconfig
Source: www.dnsstuff.com
 Use the command “nslookup” to determine whether there’s 
a problem with the server you’re trying to connect to.
Perform a DNS check
Source: www.dnsstuff.com
 Make sure your virus and malware tools are running 
correctly, and they haven’t flagged anything that could be 
affecting part of your network and stopping it from 
functioning.
Check on virus and 
malware protection
Source: www.dnsstuff.com
 Collect information
 Customize logs
 Check access and security
 Follow an escalation framework
Network  Use monitoring tools
Troubleshooting 
Best Practices
Source: www.dnsstuff.com