Flamingo Raises $4.5M Seed Round

Skip to content

Network troubleshooting: 7 steps, commands and when to escalate

IT Operations
Troubleshooting
Aliaska VarievaAliaska Varieva
November 9, 2026
21 views
Network troubleshooting: 7 steps, commands and when to escalate

The seven-step network troubleshooting method with the command for each step on Windows, macOS and Linux, a PowerShell script that checks a whole site at once, the causes technicians miss, and what evidence to attach when you escalate.


Updated: November 2026

A user says "the internet is down," and the next twenty minutes decide whether you find the fault or reboot things until it goes away. Network troubleshooting is the systematic process of finding where a network fault sits, fixing it, then proving the fix worked and writing it down. This guide gives you the seven-step method, the commands for each step on Windows, macOS and Linux, and the point where the problem belongs to someone else.

TL;DR

  • The definition. Finding a network fault, fixing it, then verifying and documenting the fix.
  • The method. Seven steps: identify, theorize, test, plan, fix, verify, document.
  • The order. Work bottom-up: link, IP address, gateway, DNS, path, app.
  • The first question. One device or everyone? The answer halves the search.
  • The remote version. Run one diagnostic script across the whole site first.
  • The handoff. Escalate with evidence: the trace, the timestamps, what you ruled out.

What are the 7 steps of network troubleshooting?

The method below comes from CompTIA's Network+ exam objectives. It's objective 5.1 of the N10-009 exam, and Professor Messer walks through it here. It's written for an exam, but it survives contact with a Tuesday morning ticket queue.

  1. Identify the problem. Get the symptom in the user's words, find out who else is affected, and ask what changed.
  2. Establish a theory of probable cause. Start with the obvious and the cheap: cable, address, DNS.
  3. Test the theory. Run the command that proves or kills it. If it dies, go back to step 2 with a new one.
  4. Establish a plan of action. Work out the fix, what it touches and what could break.
  5. Implement the fix or escalate. Make the change, or hand it to whoever owns the broken part.
  6. Verify full system functionality. Check the user can work, not just that the error is gone, and add whatever stops it happening again.
  7. Document findings, actions, outcomes and lessons learned. Write it down so the next tech solves it in two minutes.

Steps 3 and 6 are where time goes missing. Skip the test and you fix a theory instead of a fault. Skip the verify and the ticket reopens on Thursday.

Three questions before you touch anything

Search "network troubleshooting" on Google and the results page asks you questions before it gives you answers: Wi-Fi or Ethernet, one device or every device, what error message. Google figured out triage. So should the first five minutes of every ticket.

One device or everyone? One device points at the endpoint: its adapter, its settings, its VPN client. Everyone at a site points upstream: the switch, the firewall, DHCP, the ISP. Everyone everywhere points at a cloud service.

Wired or Wi-Fi? If the same laptop works on a cable and fails on Wi-Fi, you've already eliminated DNS, the gateway and the internet. You're looking at the radio, the access point or the authentication.

What changed? A firmware update, a new firewall rule, a moved desk, a new security agent. Ask even when the answer seems obvious. Uptime Institute's 2025 outage analysis found that 85% of outages caused by human error came from staff not following procedures, or from flaws in the procedures themselves.

Then spend two minutes proving it's the network at all. Network people call this "mean time to innocence," and Ned Bellavance, host of the Day Two Cloud podcast, put the default assumption bluntly in a 2025 BlueCat roundtable: "It's always the network until you prove that it's not." Check the Microsoft 365 or Google Workspace service status, try the same thing from a phone on cellular data, and try it from a second device. If Teams is down for everyone on every network, no amount of ipconfig /flushdns will bring it back.

r/msp lived this in August 2026. A Microsoft 365 sign-in degradation showed up on X before Microsoft's public status page, the real detail sat in the admin center's Service Health page, and one CEO was sure it was his computer.

Symptom, likely cause, first command

Steps are a sequence. Real tickets arrive as symptoms. This table maps the symptom to where the fault usually sits and the first command that confirms it, so you start in the right place instead of at step one every time.

What the user seesWhere the fault usually isFirst command (Windows)
"Network cable unplugged" or no link lightCable, switch port, NIC or driverGet-NetAdapter
IP address starts with 169.254DHCP didn't answer, so Windows gave itself an addressipconfig /release then ipconfig /renew
Can ping 8.8.8.8, websites won't loadDNSResolve-DnsName microsoft.com
Local shares work, internet doesn'tGateway, firewall or ISPtracert 8.8.8.8
One site or app fails, everything else worksThat server, its DNS record or a blocked portTest-NetConnection app.example.com -Port 443
Slow for everyone at the siteSaturated uplink, ISP, or a broadcast stormpathping 8.8.8.8
Slow for one userWi-Fi signal, a bad cable, or something on the PC eating bandwidthnetsh wlan show interfaces
Drops every few minutesWi-Fi roaming, duplicate IP, or a flapping portping -t <gateway> plus the System event log
VPN connects, internal resources don'tVPN DNS or split-tunnel routesroute print and Resolve-DnsName <internal-name>
Works on Wi-Fi, fails on EthernetSwitch port VLAN, 802.1X, or the cableGet-NetAdapter then check the port's VLAN on the switch

The commands for macOS and Linux are in the cross-platform table further down.

How to troubleshoot network issues step by step

The order below follows the network from the bottom up: physical link, addressing, local network, name resolution, the path out, then everything else. Each step proves one layer works before you trust it. It's the same layered logic network engineers learn as the OSI model, minus the exam.

Start with the boring stuff, because the boring stuff is broken more often than anyone admits. Is the cable seated? Is the link light on? Is the adapter enabled?

powershell
Get-NetAdapter | Select-Object Name, Status, LinkSpeed

Status should say Up. A link speed of 100 Mbps on a gigabit network usually means a damaged cable or a bad port. On Wi-Fi, netsh wlan show interfaces shows signal strength and which access point the laptop is clinging to.

Step 2. check the IP configuration

powershell
ipconfig /all

You're looking at four lines: the IPv4 address, subnet mask, default gateway and DNS servers. An address starting with 169.254 means the PC asked DHCP for an address, got no answer, and made one up. Microsoft calls this Automatic Private IP Addressing, and the whole 169.254.0.0 to 169.254.255.255 range is reserved for it. That's a DHCP or link problem, not a DNS one.

Also check the "DHCP Server" line. If it shows an address you don't recognize, someone has plugged in a consumer router and it's handing out addresses. More on rogue DHCP below.

Step 3. ping the gateway

powershell
ping <default-gateway>

If the gateway answers, the local network works. If it doesn't, the problem sits between this device and the first router: the switch, the VLAN, or the gateway itself. Some firewalls drop ping, so a failure here isn't proof on its own. arp -a shows whether the PC at least learned the gateway's MAC address, which tells you the two can see each other at layer 2.

Step 4. test DNS

DNS turns names into addresses. When it breaks, everything that uses a name breaks, even though the connection is fine. The sysadmin haiku says it best: "It's not DNS. There's no way it's DNS. It was DNS."

powershell
Resolve-DnsName microsoft.com
Resolve-DnsName microsoft.com -Server 1.1.1.1

If the second line works and the first doesn't, the PC's configured DNS server is the problem, not the internet. Don't fix that by pointing a domain-joined PC at a public resolver; our guide to DNS server not responding explains why that breaks sign-in.

Step 5. trace the path

powershell
tracert 8.8.8.8
pathping 8.8.8.8

tracert lists every router between you and the destination. A row of asterisks on one hop usually just means that router ignores trace traffic. It only matters when every hop after it fails too. pathping runs longer and adds packet loss per hop, which is what you want for "slow" complaints. Loss that starts at one hop and continues all the way to the destination is real. Loss at a single hop that disappears on the next is that router being busy, not your problem.

Know what "good" looks like before you call something slow. For Teams calls, Microsoft's network requirements ask for under 100 ms round trip, under 1% packet loss and under 30 ms jitter from the client to Microsoft's network edge.

Professor Messer runs through every one of these tools on a live terminal, including how to read the asterisks in a trace, in 18 minutes.

Step 6. read the logs and recent changes

If the path looks clean and the problem persists, the evidence is in the logs. On Windows, check the System event log for NIC resets, DHCP warnings and IP conflict events. On the network side, check the firewall's deny log, the switch log for ports flapping, and the DHCP server's lease table.

Then check the change log, if you have one. A firewall rule pushed last night explains more tickets than any packet capture.

Step 7. fix, verify, document

Make one change at a time. Two changes at once means you won't know which one fixed it, or which one broke the next thing.

Verify from the user's side. "Ping works" isn't the finish line. The user opening the app they called about is. Then document it, using the template further down.

Network troubleshooting commands by operating system

Every guide on page one of Google picks a side: Windows commands or Linux commands. Client fleets don't. This is the same set of checks on all three.

CheckWindowsmacOSLinux
Adapter and linkGet-NetAdapterifconfig -aip link or nmcli device status
IP, gateway, DNS serversipconfig /all or Get-NetIPConfigurationnetworksetup -getinfo Wi-Fiip a and ip route
Renew the DHCP leaseipconfig /release then /renewsudo networksetup -setdhcp Wi-Fisudo dhclient -r then sudo dhclient
Reachabilityping or Test-NetConnectionpingping
Is a TCP port open?Test-NetConnection host -Port 443nc -vz host 443nc -vz host 443
Path and loss per hoptracert, pathpingtraceroutetraceroute, mtr
DNS lookupResolve-DnsName, nslookupdig, nslookupdig, resolvectl query
Which DNS servers am I using?Get-DnsClientServerAddressscutil --dnsresolvectl status
Flush the DNS cacheClear-DnsClientCache or ipconfig /flushdnssudo dscacheutil -flushcache; sudo killall -HUP mDNSResponderresolvectl flush-caches
Neighbors (ARP)arp -a or Get-NetNeighborarp -aip neigh
Open ports and connectionsnetstat -ano or Get-NetTCPConnectionnetstat -an or lsof -iss -tunlp
Routing tableroute print or Get-NetRoutenetstat -rnip route

On macOS, swap "Wi-Fi" for "Ethernet" or whatever networksetup -listallnetworkservices calls the adapter. On Linux, resolvectl assumes systemd-resolved, which Ubuntu, Fedora and Debian 12 desktop installs use by default.

On Windows, the PowerShell versions are worth learning even if ipconfig is muscle memory. They return objects instead of text, so you can filter them, run them remotely and feed them into a script, which is exactly what the next section needs.

Doing it remotely across a fleet

Every step above assumes you're sitting at the broken machine. An MSP tech usually isn't. The user is two states away, the site has 40 devices, and the one laptop that called in is the only one you've heard from.

Flip the order. Before you open a remote session on one laptop, run the same diagnostic script on every online device at that site through your RMM. If every device fails DNS, it's the site's DNS server or firewall. If one does, it's that laptop. Either way, you've answered the scope question before opening a single remote session.

Something like this, pushed to every Windows device at the site, answers steps 1 to 4 in one pass:

powershell
$gw  = (Get-NetIPConfiguration | Where-Object IPv4DefaultGateway | Select-Object -First 1).IPv4DefaultGateway.NextHop
$ip  = (Get-NetIPAddress -AddressFamily IPv4 | Where-Object { $_.InterfaceAlias -notmatch 'Loopback' } | Select-Object -First 1).IPAddress
[pscustomobject]@{
  Device    = $env:COMPUTERNAME
  LinkUp    = [bool](Get-NetAdapter -Physical | Where-Object Status -eq 'Up')
  IPAddress = $ip
  APIPA     = $ip -like '169.254.*'
  Gateway   = if ($gw) { Test-Connection $gw -Count 2 -Quiet } else { $false }
  DNS       = [bool](Resolve-DnsName microsoft.com -ErrorAction SilentlyContinue)
  HTTPS     = (Test-NetConnection outlook.office365.com -Port 443 -WarningAction SilentlyContinue).TcpTestSucceeded
}

One row per device comes back. Sort by the first column that says False, and the fault usually names itself.

Three more things change when you're remote:

The switch and firewall talk too. SNMP polling on the switch shows port errors and utilization, and the DHCP server's lease table shows scope exhaustion and strange MAC addresses. Our NetFlow guide covers what flow data adds when the question is "who's eating the bandwidth."

Offline devices tell you something. If the RMM agent dropped off at 09:12 and so did four others at the same site, you have an outage, not a laptop problem.

Some fixes need hands. A dead switch port, a cable chewed by a chair wheel or a tripped breaker in the comms cupboard. Know when to send someone, and say so early instead of after an hour of remote attempts.

In OpenFrame, the diagnostic above lives in the script library and runs against a device group, Windows and macOS, with every result kept in execution history. A scheduled version with "run when the device comes online" catches the laptop that was asleep when you ran it. If you're still deciding what an RMM should do for you, start with what an RMM is and what it isn't.

Causes technicians miss

Cables, DHCP and DNS cover a lot of tickets. These are the ones that survive the usual suspects, because nothing in steps 1 to 5 looks obviously broken.

CauseWhat you seeHow to confirmFix
Rogue DHCP serverSome PCs get the wrong gateway or a 192.168.0.x addressipconfig /all shows an unknown DHCP ServerFind the port, unplug it, turn on DHCP snooping
DHCP scope exhaustedNew devices get 169.254 addresses, existing ones are fineFree addresses in the DHCP scope statisticsShorten the lease time or widen the scope
Duplicate IPRandom drops, an IP conflict event in the System logarp -a shows the address flipping between two MACsFix the static assignment or add a reservation
Clock driftSign-ins fail, certificate errors on internal sitesw32tm /query /status and compare to a known sourceFix the time source on the domain controller
Expired certificateOne app fails with TLS errors, the network tests passThe certificate dates in the browserRenew and redeploy
Switching loop or broadcast stormThe whole site crawls, switch lights blink in unisonInterface counters and spanning tree logsFind the loop, enable storm control
Asymmetric routingConnections open, then stall through a firewallTrace in both directionsFix the route so traffic returns the way it left
Lapsed licenseA firewall feature or VPN seat quietly stops workingThe vendor portalRenew, then set a reminder

When to escalate

Escalation sits in step 5 of the method, right next to the fix. Set a time box per tier and hand over with evidence, so the next person doesn't repeat your first hour.

The cost of sitting on it adds up. In Uptime Institute's 2026 outage analysis, 57% of respondents said their most recent major outage cost more than $100,000, and networking and connectivity was the top cause of IT service outages at 23%.

HandoffWhenWhat to attach
Tier 1 to Tier 2No working theory after 20 minutes, or more than one user affectedSymptom, scope, and the output of steps 1 to 4
To the ISPLoss starts at the first hop past your firewall and continues to the destinationpathping output with timestamps, a test from a device plugged straight into the modem, the circuit ID
To a SaaS vendorTheir status page is green, but the port test fails from two different networksTest-NetConnection output from both networks, the time window, your tenant ID
To the clientThe fix needs money, downtime or a change they must approveWhat broke, what the fix costs, what waiting costs

The ISP row is where evidence matters most. "The internet is slow" gets you a script read back to you. "Loss starts at your hop 3 and continues to the destination, here's the output from 10:42" gets you a technician.

A passing ping isn't proof of a clean path either. In this r/networking thread, UDP and ICMP to one IP stayed perfect while TCP hung, and the pattern followed the source prefix. The top answer pointed upstream at broken ECMP or LACP, which is a case for the ISP with captures attached.

Document the fix

Six of the ten guides ranking for this topic tell you to document your work. None say what to write. Here's the minimum that makes a ticket useful the next time the same thing breaks:

  • Symptom. What the user reported, in their words, and when it started.
  • Scope. Who and what was affected, and who wasn't.
  • Tests run. The commands and the output that mattered.
  • Root cause. What was broken, in one sentence.
  • Fix. The exact change, and who approved it if anyone had to.
  • Follow-up. Anything that stops it happening again: monitoring, a reservation, a replaced cable.

A good ticket is also the raw material for automation. Once the same root cause shows up three times, it's a script, not a ticket. Our guide to what a help desk is for covers how to structure the ticket fields around this.

Tools that make the steps faster

Everything above runs on built-in commands, and that's on purpose: they're on every machine you'll ever touch. A few tools speed up specific steps. Wireshark shows what's on the wire when the commands disagree. Nmap answers "what's on this subnet and which ports are open." PRTG, Zabbix and Netdata watch interfaces and alert before the user calls. Your RMM runs the commands for you across a fleet.

Monitoring earns its place by shortening the slow cases. In a NETSCOUT survey at Cisco Live 2025, 81% of IT respondents said issues in their environment took a few hours or more to resolve. A baseline tells you what normal looked like before the call came in, and an alert gets you there before the user does.

For a side-by-side of the monitoring platforms, see our roundup of network management software.

The short version

Ask the scope question first. Prove it's the network before you fix the network. Work from the cable up. Run one script across the site before you remote into one laptop. Hand over with evidence, and write it down.

When a specific error shows up, the deeper guides pick up where this one stops: destination host unreachable, DNS server not responding and every ipconfig switch worth knowing.

It's probably DNS. Check anyway.

Aliaska Varieva

Aliaska Varieva

VP of Engineering

Hi! I’m Aliaska, and I’ve been working as a software engineer (mostly Java + a bit Kotlin) for over 8 years now. I mostly spend my time building backend services, integrating systems, fixing bugs (the fun part 🙃), and making sure things don’t fall apart behind the scenes.

Related Content

Frequently Asked Questions

/blog/network-troubleshooting

Still deciding?

Ask Mingo answers from our docs and customer stories.

Loading related content and questions