Diagnose Any Network Problem Step-by-Step in 2026

Let’s talk about something different today. We won’t be discussing how to solve problems – instead, we’ll focus on how to identify them. The truth is, whenever most people encounter a network issue, their first instinct is to type “internet not working” into Google, try 10 different random fixes, and – if they’re lucky – something eventually works. However, they never actually discover what the underlying problem was. Consequently, the next time the same issue arises, they are back to blindly fumbling in the dark.

This approach is akin to a doctor prescribing medication without first conducting a diagnosis – it might work occasionally, but most of the time, it simply results in wasted effort.

In this guide, we will teach you a systematic approach to network problem troubleshooting – the very method utilized by IT professionals, network engineers, and tech support teams. Once you grasp this approach, you will be able to systematically diagnose any network issue that comes your way – whether it involves your home Wi-Fi, office LAN, Jio or Airtel mobile data, or any other connectivity problem. Just like a doctor: first the diagnosis, then the treatment.

The Fundamental Approach to Network Troubleshooting – The “Bottom-Up” Method

Before we dive into the actual steps, let’s understand a concept that professional network engineers utilize.

Network communication operates in layers – much like a building is constructed in floors. If there is a problem on the ground floor (the foundation), all the floors above it will be affected. The same principle applies to networks.

IT professionals refer to this as the OSI Model – comprising 7 layers. However, you do not need to memorize all seven. We have simplified it into 5 easy steps:

Golden Rule: Always check from the bottom up (Bottom-Up). Start with the physical cables, then the device, followed by the router, the ISP, and finally DNS/Apps. Following this sequence allows you to systematically diagnose 95% of network issues.

Why Bottom-Up? Because if the cable itself is loose (Step 1), there is no point in changing DNS settings (Step 5). Many people keep trying solutions at Step 5 while the actual problem lies at Step 1.

Step 1: Physical Layer Check – First, check the “visible” elements.

This is the most basic, yet most frequently overlooked, step. IT support professionals state that approximately 25–30% of network issues stem from physical layer problems – such as a loose cable, a damaged port, or a faulty power adapter.

What to Check:

Ethernet/LAN Cable (if using a wired connection):

• Is the cable firmly plugged in at both ends? Give it a tug to check – is it loose anywhere?
• Is there any visible damage to the cable – cuts, kinks, or chew marks (thanks, pets!)?
• Is the plastic clip on the RJ45 connector broken? A broken clip causes the cable to fit loosely.
• Try swapping out the cable – this is the quickest diagnostic step.

Router/Modem:

• Is the power light ON? Is the adapter properly plugged in?
• Internet/WAN light – on most routers, this should be green or blue; red or orange indicates an ISP issue.
• Is the WiFi light blinking? On some routers, the WiFi can be toggled on/off via a dedicated button – check for an accidental press.
• Touch the router – is it excessively hot? Overheating can cause the device to freeze.

Fiber/Broadband Connection (India-Specific):

• If you have FTTH (Fiber to Home) – check the ONT (Optical Network Terminal) box.
• The PON light on the ONT should be green – if it is red or off, there is a problem with the fiber cable.
• If the LOS light is red, the fiber cable has been cut – call your ISP.
• Check for any sharp bends in the fiber cable – excessive bending of the fiber cable causes signal loss.

Physical Layer Diagnostic Commands:

If an Ethernet cable is connected, this command will indicate whether the physical link is UP or DOWN:

Windows CMD:

netsh interface show interface

Look at the “State” column in the output:

• Connected = Physical link OK ✅
• Disconnected = Cable problem or port issue ❌

Step 2: Local Device Check – Is Your Device Working Correctly?

If the Physical Layer is OK, the next question is: Does the problem lie with your device (phone, laptop, or PC)?

Quick Device Diagnostic:

Test 1 – Check the Internet on Another Device:

This is the most important diagnostic test. If the internet isn’t working on your laptop, check it on your phone using the same Wi-Fi network. If it works on your phone, the problem lies with the laptop. If it isn’t working on either device, the problem lies with the router or ISP.

Test 2 – Check WiFi Adapter Status:

Windows:

• Settings > Network & Internet – Is WiFi ON?
• Device Manager > Network Adapters – ❗ yellow mark on WiFi adapter?
• Fn + F5/F7/F8 (depending on laptop brand) – hardware WiFi switch

Android:

• Settings > WiFi – toggle ON?
• Is Airplane Mode OFF?
• Settings > Network > Reset Network Settings

Test 3 – IP Address Assigned?

Windows CMD:

ipconfig

See:

• Is the IPv4 Address in the 192.168.x.x format? ✅ Good
• Is it showing 169.254.x.x? ❌ DHCP failure – the device did not receive an IP address
• Is it 0.0.0.0 or no IP address at all? ❌ Network adapter issue

Android:

• Settings > WiFi > Connected Network > Details – Check IP Address

If the IP address is 169.254.x.x (APIPA Address) – What to do:

This indicates that the device requested an IP address from the router but did not receive one. This signifies a DHCP failure.

Fix Sequence:

1. ipconfig /release then ipconfig /renew (Windows CMD)
2. Forget WiFi and reconnect
3. Router restart
4. DHCP enabled check on the router

Test 4 – Network Adapter Driver Check:

Windows:

netsh wlan show drivers

This will display the WiFi driver details – version, date, and provider. If the driver is very old or is a generic “Microsoft” driver (rather than a manufacturer-specific one), update the driver.

Step 3: Local Network Check – Is the Router/Modem Accessible?

The device is OK; now, check whether the communication between the device and the router is functioning correctly.

Router Reachability Test – Ping:

Ping is the most fundamental tool for network troubleshooting. It verifies whether data is successfully reaching one device from another.

Windows CMD or Mac Terminal:

ping 192.168.1.1

(Enter your router IP – usually 192.168.1.1 or 192.168.0.1)

Result Interpretation:

If you are unable to ping the router:

• Cable check (Step 1 repeat)
• WiFi reconnect
• Try setting the IP manually (Static IP: 192.168.1.100, Subnet: 255.255.255.0, Gateway: 192.168.1.1)

Router Admin Panel Access:

Open the router IP (192.168.1.1) in your browser. If the admin panel opens – local network connectivity ✅

India Common Router Default Credentials:

⚠️ Important: Change the default password immediately – it is a security risk.

Connected Devices Check:

Check for “Connected Devices” or “DHCP Client List” in the router admin panel.

• How many devices are connected? More than necessary?
• Is there any unrecognized device? (WiFi theft)
• Does the problematic device appear in the list?

Router Logs Check:

Router Admin Panel > System Log or Event Log – This provides valuable diagnostic information:

• When did connection drops occur?
• DHCP errors
• Authentication failures
• WAN connection status changes

Step 4: ISP/External Connection Check – Connection to the Outside World

Connectivity to the Router ✅ – Now, check whether there is a connection from the router to the internet.

External Ping Test:

Ping a Public IP:

ping 8.8.8.8

(This is Google’s DNS server – it is almost always online.)

This test is very important because:

• If the router pings ✅ but 8.8.8.8 does not ❌ – the problem lies between the ISP and the router.
• If 8.8.8.8 pings ✅ but websites are not opening – the problem is at the DNS level (Step 5).

Traceroute – Path Analysis:

Traceroute shows which servers (hops) your data passes through to reach its destination – and where it gets stuck.

Windows:

tracert 8.8.8.8

Output Example:

1    1ms    192.168.1.1      (Your router)
2    5ms    10.x.x.x         (ISP local node)  
3    15ms   72.x.x.x         (ISP backbone)
4    *      *      *          Request timed out
5    25ms   8.8.8.8          (Google DNS)

Interpretation:

• Hop 1 (Router) – Fast ✅
• Hops 2–3 (ISP) – Reasonable ✅
• Hop 4 – Timeout – There could be a problem at this hop (or a firewall blocking ICMP).
• If the timeout occurs at the last hop – Destination issue.
• If the timeout occurs consistently at the ISP hops – ISP routing problem.

ISP Outage Check:

• downdetector.in – Check Jio, Airtel, BSNL, and Vi.
• Check your ISP app – Outage notifications appear in the Jio app and Airtel Thanks app.
• Search for your ISP’s name on Twitter/X – If there is a widespread outage, it will likely be trending.
• Ask your neighbors or friends – specifically those who use the same ISP.

WAN Status in the Router:

Router Admin Panel > WAN Status or Internet Status:

• Is a WAN IP assigned? (A public IP should be visible, not 0.0.0.0)
• Connection Status: Connected/Disconnected
• Uptime: If it is very low (just a few minutes), the connection is dropping repeatedly.

Step 5: DNS & Application Layer Check – Websites and Apps

If everything is ✅ up to Step 4 (ping 8.8.8.8 successful), but websites are not opening, the problem lies at the DNS level.

DNS Test:

nslookup Command:

nslookup google.com

If DNS is failing:

nslookup google.com 8.8.8.8

This specifically queries Google DNS. If this works but the first command does not, your configured DNS server is down.

Fix:

• Change DNS: 8.8.8.8 (Google) or 1.1.1.1 (Cloudflare)
• DNS cache flush: ipconfig /flushdns

Specific Website/App Down Check:

Sometimes, the problem lies not with the internet, but with a specific website or service.

• isitdownrightnow.com – Check the status of any website
• downdetector.in – Indian services (Paytm, PhonePe, Hotstar)

If only one website is not opening:

• ISP-level blocking may be in effect (many websites are blocked in India).
• The website itself might be down.
• Try checking with a VPN – if it opens via the VPN, then it is an ISP block.

Browser-Specific Issues:

• Problem with Chrome – Try Firefox or Edge.
• Clear your browser cache: Ctrl+Shift+Delete.
• Try disabling your extensions – one of them might be blocking it.
• Test it in Incognito mode.

Complete Diagnostic Flowchart – At a Glance

Encountered a Network Issue? 
│
├── Step 1: Cables/Hardware OK? 
│       ├── NO → Fix/Replace cables, check power
│       └── YES ↓
│
├── Step 2: Is it working on another device? 
│       ├── YES → Problem lies with this specific device (driver/settings)
│       └── NO ↓
│
├── Step 3: Can you ping the router? (192.168.1.1)
│       ├── NO → Restart router, reconnect to WiFi
│       └── YES ↓
│
├── Step 4: Can you ping 8.8.8.8? 
│       ├── NO → ISP issue – Check/Call your ISP
│       └── YES ↓
│
└── Step 5: Website/DNS Issue
├── Change DNS (to 8.8.8.8)
├── Clear browser cache
└── Check if the specific site is down

Take a screenshot of this flowchart and save it on your phone – the next time you encounter any network issue, just follow it.

Essential Free Diagnostic Tools – Build Your Toolkit

Command Line Tools (Built-in – No installation required):

Free Software Tools:

Mobile Diagnostic (Android):

Android phones have a hidden diagnostic menu.

Type this into the phone dialer:

• *#*#4636#*#* – Phone Information (signal strength, network type)
• WiFi Information – detailed WiFi stats

Jio Specific:

• MyJio App > Network Issues > Run Diagnostic – This automated test detects ISP-side issues

Airtel Specific:

• Airtel Thanks App > Help > Network Issue > Self Diagnose

Common Mistakes People Make During Troubleshooting

Mistake 1: Random Fixes First, Diagnosis Later

“Internet not working? Change the DNS, restart the router, reset the network, perform a factory reset!”

This approach works occasionally, but most of the time, it just wastes time. Diagnose the issue first, then apply a targeted fix.

Mistake 2: Checking Only One Device

“It’s not working on my phone,” – but did you check your laptop? Or another phone? If you first verify whether the problem is device-specific or network-wide, the diagnosis time is reduced by 50%.

Mistake 3: Skipping Basic Checks Before Calling the ISP

You spent 20 minutes on hold with ISP customer care, only for a technician to arrive, tighten a cable, and leave. Had you performed that first step yourself, you would have saved those 20 minutes.

Mistake 4: Assuming DNS is the Solution to Every Problem

Changing the DNS (e.g., to 8.8.8.8) is a very popular fix – but it only resolves DNS-related issues. If the ISP connection itself is down, changing the DNS won’t make any difference.

Mistake 5: Installing “Speed ​​Booster” / “Network Fixer” Apps

There are thousands of “WiFi Booster” and “Internet Speed ​​Booster” apps on the Play Store – but 99% of them are useless or contain malware. No app can physically increase your internet speed. Clearing your RAM does not boost your internet speed.

Advanced Diagnostic Techniques – For Power Users

Continuous Ping (Network Stability Test):

ping 8.8.8.8 -t

This will continue pinging continuously. Stop it by pressing Ctrl+C. The statistics will appear:

• Packets Sent/Received/Lost – Loss % will tell how stable the network is.
• 0% loss = Perfect ✅
• 1–5% loss = Minor issues – usable but not ideal
• 10%+ loss = Serious problem ❌

Let it run for at least 100 pings (2–3 minutes) to get an accurate picture.

Pathping (Windows Exclusive):

pathping 8.8.8.8

This is a combination of ping and traceroute – it measures packet loss at every hop. It takes 5–10 minutes to run but provides very detailed results. It is the best tool for identifying ISP routing issues.

WiFi Signal Analysis (Detailed):

netsh wlan show all (Windows CMD) – This provides complete WiFi information:

• all available networks
• Signal strength (in dBm)
• Channel assignments
• Security types

Signal Strength Guide:

MTU (Maximum Transmission Unit) Issues:

Sometimes, a VPN or specific websites do not work due to an MTU mismatch.

Test:

ping 8.8.8.8 -f -l 1472

If “Packet needs to be fragmented” appears, the MTU is too large. Decrease the size (1472 → 1400 → 1380) until ping is successful – that is the optimal MTU.

Fix: Router settings > WAN > MTU Size = tested optimal value (usually 1400–1472)

Troubleshooting Comparison – Home vs Office vs Mobile

Create Your Network Diagnostic Checklist

Every time a network issue arises, follow this checklist:

✅ Immediate (0–2 minutes):

• [ ] Did you check the internet on another device?
• [ ] Did you toggle Airplane mode?
• [ ] Did you toggle WiFi/Data?

✅ Basic (2–5 minutes):

• [ ] Checked cables/connections?
• [ ] Did you check the Router/Modem lights?
• [ ] Restarted the router? (30 sec power off)

✅ Diagnostic (5–10 minutes):

• [ ] ipconfig – IP address check
• [ ] ping 192.168.1.1 – Router connectivity
• [ ] ping 8.8.8.8 – Internet connectivity
• [ ] nslookup google.com – DNS check
• [ ] Speedtest.net – Speed measurement

✅ Advanced (10+ minutes):

• [ ] tracert 8.8.8.8 – Path analysis
• [ ] Driver update check
• [ ] Router admin panel – WAN status, logs
• [ ] ISP outage check (Downdetector)
• [ ] DNS change (8.8.8.8 / 1.1.1.1)

Maintain a Diagnosis Record – Look for Patterns

If network issues are recurring, keep a record:

Pattern Recognition:

• Always slow in the evening? → ISP congestion
• Problems during rain? → Physical cable issue
• Only on a specific device? → Device driver/hardware
• Temporarily fixed by restarting the router? → Router aging/overheating

FAQs – Diagnose Any Network Problem

Final Thoughts

So, that was the complete, systematic approach to diagnosing network issues – the “Bottom-Up” method utilized by professional IT engineers, simplified into 5 easy steps. Physical → Device → Router → ISP → DNS/App – remember this sequence. At each step, there are specific tests (ping, traceroute, nslookup) that pinpoint exactly where the problem lies.

The biggest takeaway here is this: stop attempting random fixes; instead, perform a systematic diagnosis. A doctor conducts a blood test before prescribing medication; similarly, you should run ping or traceroute tests first, and then apply a targeted fix. This approach not only saves time but also boosts your confidence – the next time any network issue arises, you will know exactly where to look and what to do. For more guides, visit: fixtech.in. 🔍✅