Question

Network administrators are required to troubleshoot networking issues on a regular basis.

Based upon your experiences, discuss your thoughts with the class regarding the best approaches to track down and identify problems and any challenges that you envision when attempting to do this.

How would you summarize the process to troubleshoot problems with any given network issue?

What advice might you give someone new to troubleshooting networks?

Answer 1

Let’s step through the basic process of how to troubleshoot network connectivity problems. That way, next time you open up your web browser to a Cannot Connect message, you’ll know what to do. Like all troubleshooting, we’ll start broadly and narrow down to specifics.

After each step, attempt to connect to a website to verify your connection is working. If it still doesn’t work, continue to the next part.

1. Power Cycle Everything and Check Other Devices

There’s no need to get upset right away, as the fix to your problem might be as simple as rebooting your equipment. Restarting fixes a ton of issues, so make sure it’s your first response to network problems, too.

Go ahead and reboot your PC, as well as your modem and router. To clear the modem and router caches, wait 60 seconds before you turn them back on again. When you plug everything back in, plug your modem in first and wait for it to power on before connecting your router.

Turning everything off and back on first ensures that it isn’t a temporary network problem. It’s better to reboot now than to waste 30 minutes continuing on when you don’t need to.

Once you’ve restarted, if you have another computer (or a mobile device), try getting online with that machine. If you find that no devices can connect, it’s likely an issue with your equipment or your ISP.

Should you find that only one computer can’t get online, you can continue to narrow down the problem. On that device, make sure to run an antivirus scan to ensure you don’t have malware interfering with your connection. You should also make sure that your firewall settings aren’t blocking the connection.

Finally, try using a different browser to see if your usual one is somehow damaged.

2. Check Physical Connections

Does your network problem persist after rebooting? Before you start diving into settings and tests, the next step to check is that you’re physically connected.

If you use an Ethernet cable to connect to your router, check to make sure that it’s not unplugged or damaged. If your laptop has a physical wireless switch, make sure that it’s not set to the off position.

Once you’ve verified a proper connection, check your equipment. Are the lights on your router and/or modem flashing green as normal? If no lights come on after the reboot, the device could be dead or malfunctioning. However, if you get red lights, or a power light but no connection light, your ISP is likely experiencing disruption

3. Run the Windows Network Troubleshooter

Windows includes some built-in troubleshooters that can automatically find and fix issues. To run the troubleshooter for network problems, right-click the network icon in your System Tray and choose Troubleshoot Problems. Once the troubleshooter runs, it could fix issues, find issues but fail to fix them, or find nothing.

If the troubleshooter finds a problem that it fixes, try to connect again. If you get a specific error or problem name that Windows can’t fix automatically, take note of it for later research.

Advanced users might also look at using other Windows tools to troubleshoot network issues.

4. Check for a Valid IP Address

At this point, you’ve verified that the problem is not temporary and that all your hardware works. Since Windows can’t fix the problem on its own, we need to pinpoint the spot along the connection where the problem is occurring.

It’s a good idea to make sure that you don’t have any strange IP settings selected. To check this, open Settings and go to Network & Internet > Status. Below the Change your network settings header, choose Change adapter options. In the resulting window, double-click the name of your network.

Next, you’ll see a status box. Click the Properties button.

ere, double-click the Internet Protocol Version 4 entry.

Unless you’ve set up a static IP (if you don’t know what this is, you probably don’t use one), make sure you have both Obtain an IP address automatically and Obtain DNS server address automatically checked. Repeat this process for Internet Protocol Version 6 to ensure everything is automatic there, as well.

Reviewing Your IP Address Validity

Once you’ve done this, you can check to confirm the router is giving you a valid IP address. Open up a Command Prompt window by typing cmd into the Start Menu. Enter ipconfig and look for the text under Ethernet adapter (for wired connections) or Wireless LAN Adapter (for wireless connections).

If IPv4 Address starts with 169.x.x.x, your computer is not receiving a valid IP address from your router. Typing the following two commands will release your computer’s current IP address and request a new one, which may resolve this:

ipconfig /release 
ipconfig /renew

Should you still have a 169.x.x.x address after typing the above commands and ipconfig again, your machine still isn’t receiving an IP from the router. Try plugging your PC directly into the modem with an Ethernet cable and see if you can get online. If so, your router is the problem.

5. Try a Ping and Trace Its Route

If your IP address starts with anything other than 169 when you run ipconfig, you have a valid IP address from your router. At this point, you’ve confirmed the problem is somewhere between your router and the internet.

ping 8.8.8.8

This will send four packets to Google. If they fail to send, you’ll see some basic info about the failure. In case you want to continue pinging indefinitely so you can monitor it while troubleshooting, just add a -t to the end, like so:

ping 8.8.8.8 -t

You can press Ctrl + C to stop pinging at any time. For more information, type this command to trace the route between your computer and Google’s DNS servers:

tracert 8.8.8.8

The above command gives you a step-by-step breakdown of the path the information takes to reach the destination you specify. Watch it, and if it fails, check to see where the problem occurs. If an error pops up early in the route, the issue is likely with your local network.

6. Contact Your ISP

Should all the above steps complete successfully, you’ve now verified that your equipment is working and confirmed you have a valid IP address from the router. Also, you’re sure that the problem is occurring outside of the network for multiple devices. If this is the case, your next best option is to find out if your ISP is having issues.

Using your smartphone will prove useful here, as you can look up an outage map for your provider or check Twitter to see if others in your area are experiencing issues as well. If you don’t see anything of note online, try giving your ISP a call to see if there are known issues. Perhaps line issues are affecting a small area; a representative should be able to run tests to check.

7. Wait the Network Problems Out

Once you’ve let your ISP know of the issue and confirmed that it’s not just one computer having a problem, all you can do is wait. Many times, you can’t fix network issues on your own.

If your ISP is aware of the issues, hopefully they’ll get everything fixed in a short time. Meanwhile, you can take the opportunity to enjoy reading a book, going for a walk, or something else that’s offline.