Troubleshooting of Network

These easy network troubleshooting techniques should always be used as a starting point to assist identify and narrow the problem. 

Check the hardware.

• As you start the troubleshooting procedure, ensure all of your hardware is turned on, connected correctly, and functioning. Your networking troubles could be caused by something as simple as a loose wire or someone turning off a crucial router. 
• If all you need to do is plug in a cord, there is no use in going through the process of diagnosing network issues. Verify that every switch is in its proper place and hasn't been accidentally bumped.
• Next, switch the hardware on and off once more. This is the cornerstone of IT troubleshooting, and although it may appear straightforward, it frequently actually resolves the issue. Simple problems can be resolved by rebooting your modem, router, and computer.

Use ipconfig.

• Ipconfig should be entered into the command prompt's terminal window without quotation marks. Your router's IP address is specified as the Default Gateway (last). The number next to "IP Address" is your computer's IP address. 
• Your computer is not obtaining a valid IP address if its IP address begins with 169. Your PC is receiving a legitimate IP address from your router if it begins with a number different from 169.
• To get rid of your current IP address and request a new one, try typing "ipconfig /release" and "ipconfig /renew." In certain circumstances, this will make the issue go away. 
• If your router is still unable to provide you with a working IP address, try connecting your computer directly to the modem with an ethernet connection. If it functions, the router is at fault.

Use ping and tracert.

• The issue is most likely between your router and the internet if your router is functioning properly and your IP address doesn't begin with 169. It's time to use the ping tool at this point. To see if it can connect with your router, try sending a ping to a reputable, big server, like Google. 
• Open the command prompt and type "ping 8.8.8.8" to ping the Google DNS servers. You can also add "-t" to the end to make the command continually pinging the servers while you troubleshoot (ping 8.8.8.8 -t). 
• The command prompt will reveal the most basic information on the problem if the pings are unable to send.
• By typing "tracert 8.8.8.8," you may perform the same action using the tracert command, which will display each "hop" between your router and the Google DNS servers. Where the error is occurring along the pathway is seen. 
• If the error first appears along the path, your local network is probably where the problem is.

Perform a DNS check.

• To check if there is a problem with the server you are attempting to connect to, use the command "nslookup." The DNS server for your destination may be the source of the issue if you do a DNS check on, say, google.com and get responses like "Timed Out," "Server Failure," "Refused," "No Response from Server," or "Network Is Unreachable." (To check your own DNS server, you can alternatively use nslookup.)

Contact the ISP.

• If none of the aforementioned steps reveal any issues, consider calling your internet service provider to check if they're experiencing any problems. 
• On a smartphone, you can search for outage maps and associated data to check if other people in your area are experiencing the same issue.

Check on virus and malware protection.

• Check the security against malware and viruses. Next, check to see whether your malware and virus protection program are functioning properly and haven't detected anything that might be affecting a portion of your network and preventing it from operating.

Review database logs.

• To ensure that the databases are operating as planned, review all of your database logs. The performance of your network may be impacted if your database is overloaded or broken but your network is functional otherwise.

There are some more troubleshooting tools to be learn