Flamingo Raises $4.5M Seed Round

Skip to content

Network troubleshooting tools: what to use when ping runs out

MSP Tools & Reviews
IT Operations
Troubleshooting
Aliaska VarievaAliaska Varieva
November 9, 2026
33 views
Network troubleshooting tools: what to use when ping runs out

A roundup of network troubleshooting tools by the question each one answers: Wireshark and pktmon for packet capture, Nmap for scanning, iperf3 and MTR for speed and path, Zabbix, PRTG and LibreNMS for monitoring, Wi-Fi analyzers, and where an RMM fits. Free vs paid, and who each fits.


Updated: November 2026

Built-in commands tell you something is wrong, and the right tool tells you why. This roundup covers the network troubleshooting tools technicians reach for after ping and tracert run out: packet capture, scanners, monitoring, throughput and path testing, Wi-Fi analyzers, and where an RMM fits. For each one you get what it answers, what it costs and who it fits.

TL;DR

  • The short answer. Wireshark, Nmap, iperf3, MTR and a Wi-Fi analyzer cover single faults, and they're free.
  • Monitoring. Zabbix and LibreNMS are free and self-hosted, PRTG is paid above 100 sensors.
  • Paid earns its keep. Professional Wi-Fi surveys and monitoring at scale.
  • Fleet view. An RMM runs the same check on every device at once.
  • Method first. Tools speed up a method, so follow the steps before installing anything.

Network troubleshooting tools compared

ToolCategoryCostRuns onAnswers the questionFits
Built-in commands (ping, tracert, Test-NetConnection)DiagnosticsFree, preinstalledWindows, macOS, LinuxCan this device reach that one?Everyone, first five minutes
pktmon and tcpdumpPacket capture, CLIFree, preinstalledWindows (pktmon), Linux and macOS (tcpdump)What's leaving this box?Remote captures, servers
WiresharkPacket capture and analysisFree, open sourceWindows, macOS, LinuxWhat's on the wire, packet by packet?Tier 2 and up
NmapScannerFree, open sourceWindows, macOS, LinuxWhat's on this subnet and which ports are open?Audits, onboarding, firewall checks
Angry IP ScannerScannerFree, open sourceWindows, macOS, LinuxWhich addresses answer right now?Quick sweeps, Tier 1
iperf3Throughput testingFree, open sourceWindows, macOS, LinuxHow fast is this link between two points I control?"Slow" tickets, new circuits
MTR (WinMTR on Windows)Path testingFree, open sourceLinux, macOS, WindowsWhere on the path does loss start?ISP escalations
ZabbixMonitoringFree, open source (AGPLv3), paid supportSelf-hosted LinuxWhat changed, and when?Teams with Linux skills and many device types
PRTGMonitoringFree up to 100 sensors, then subscriptionWindows server, or hostedWhat changed, and when?Windows shops that want it working by Friday
LibreNMSMonitoringFree, open source (GPL)Self-hosted LinuxWhat are my switches and firewalls doing?SNMP-heavy networks, mixed vendors
Wi-Fi analyzers (NetSpot, WiFi Explorer, Ekahau)WirelessFree tiers to pro survey kitsWindows, macOS, AndroidIs it the radio, the channel or the coverage?Offices with Wi-Fi complaints
OpenFrameRMM and fleet$1 per device per month (GA pricing, July 2026)Windows, macOS endpointsIs it one device or the whole site?MSPs and IT teams running many sites

If you need the method that comes before all of this, start with our network troubleshooting guide. It covers the seven steps, the triage questions and the built-in commands on Windows, macOS and Linux. This post picks up where those commands stop.

Why the toolkit matters more than any one tool

Network teams don't lack tools. They lack the right one at the right moment. In EMA's Network Management Megatrends 2026 research, a survey of 352 network professionals, only 32% said they were completely satisfied with their current tools. 33% said they're very likely to replace their network observability tools within two years, up from 26% in 2024.

Shamus McGillicuddy, who runs EMA's network management research, wrote that up for TechTarget in May 2026. The pattern is familiar from any service desk. A monitoring platform shows that something broke, then a technician still opens three other tools to find out why.

So think in questions, not products. Each category below answers one question well. Pick the question first and the tool picks itself.

Built-in commands still come first

Every machine you'll ever touch already has ping, tracert or traceroute, nslookup, and on Windows, Test-NetConnection and pathping. They answer reachability, name resolution and the route out. Our troubleshooting guide has the full cross-platform table, so it isn't repeated here.

Two built-ins get forgotten. Windows 10 and 11 ship a packet capture tool called pktmon. pktmon start --capture records traffic, and pktmon etl2pcap converts the result into a file Wireshark opens. On Linux and macOS, tcpdump does the same job and is usually already installed.

These matter for remote work. You can run a capture through a remote terminal on the user's machine, pull the file back and open it in Wireshark on yours. No installer, no change request, no "can you click Next for me."

The built-ins run out when the question gets specific. Ping proves a path exists. It can't tell you why a TLS handshake stalls, which ports a rogue device has open, or whether a 1 Gbps link delivers 200 Mbps. That's where the next categories start.

Packet capture and analysis

Wireshark is the default answer when the commands disagree with the user. It's free, open source and runs on Windows, macOS and Linux. It decodes thousands of protocols, follows a TCP conversation from handshake to reset, and shows retransmissions, window problems and slow server responses that ping never sees.

The 4.6 release in October 2025 added a Plots dialog with scatter graphs next to the older I/O graphs, plus compression for live captures. It also dropped support for WinPcap and AirPcap, so Windows installs now use Npcap for capture.

Where it fits: Tier 2 and up, and any ticket where "the app is slow" survives the command checks. Capture filters keep the file small, so set one before you start (host 10.0.0.25 and port 443). Display filters like tcp.analysis.retransmission then find the problem in seconds instead of scrolling.

Where it doesn't: a busy uplink produces gigabytes in minutes, and Wireshark on a laptop sees only what reaches that laptop. To see traffic between two other devices you need a SPAN or mirror port on the switch, or a network tap. Plan that before the outage, not during it.

Professor Messer covers protocol analyzers, port scanners and speed test sites in a seven-minute video, which is a fast way to brief a junior tech on what each category is for.

Network scanners

Nmap answers "what's on this subnet, and what is it listening on." It's free and open source, with Zenmap as an optional GUI, and version 7.99 shipped in March 2026. A ping sweep (nmap -sn 192.168.1.0/24) lists live hosts. A service scan (nmap -sV -p 1-1024 10.0.0.15) shows which ports are open and what's behind them.

In troubleshooting, Nmap settles arguments. Is the firewall blocking 3389, or is nothing listening? Did the printer come back on a new IP? Is there a device on the network nobody can name? It's also the first tool to run when you onboard a new client and the documentation is a sticky note.

Angry IP Scanner is the quick option. It's free, cross-platform and faster to read for a simple sweep. One caveat comes from a January 2026 r/sysadmin rant. A technician's sweep across VLANs reported all 254 addresses alive on the same ports, probably because a firewall in the path answered for them. A scanner reports what answers, and that isn't always the device you meant.

Ask before you scan. A scan on a client network can trip their IDS or EDR, and some contracts require notice. Get it in writing, especially on networks you don't manage day to day.

Monitoring platforms

Monitoring answers the question the other tools can't: what changed, and when. A baseline of interface traffic, CPU, errors and latency means you can say "the uplink has hit 95% every afternoon since Tuesday" instead of guessing. Our network management software roundup compares a dozen platforms in depth. These three come up most in troubleshooting conversations.

Zabbix is free and open source, licensed under AGPLv3 since version 7.0, with paid support available. It monitors almost anything through agents, SNMP and templates, and it scales to large estates. The cost is setup time. Templates, triggers and host groups take a weekend to learn, and someone on the team needs Linux skills.

PRTG is the fast start. It runs on a Windows server, discovers devices and builds sensors with little configuration. The freeware edition covers 100 sensors, which is enough for a small office. Paessler moved PRTG to subscription-only licensing in July 2024, and long-time customers on r/sysadmin reported sharp jumps at renewal. Our PRTG review breaks down the current tiers.

LibreNMS is free, GPL-licensed and built around SNMP auto-discovery. Point it at a switch with SNMP credentials and graphs for every interface appear within minutes, across a wide range of vendors. It's strongest on switches, routers and firewalls. It's lighter on servers and applications.

The difference between Zabbix and LibreNMS is easier to feel than to describe. In this r/networking thread, a long-time LibreNMS user tries Zabbix against a Ubiquiti switch. LibreNMS showed data within five minutes. Zabbix took 20 minutes of head-scratching before he found that it needed a device template first.

Who each fits: LibreNMS for SNMP-heavy, mixed-vendor networks where you want graphs today. Zabbix for teams that monitor servers, apps and network gear in one place and have the Linux time to invest. PRTG for Windows shops that would rather pay than tinker.

Speed and path testing

"The internet is slow" is two questions. How much bandwidth does this link deliver? And where on the path does latency or loss start? Speed test websites answer neither well, because they test to a server you don't control, over links you can't see.

iperf3 tests throughput between two machines you control. Run iperf3 -s on one end and iperf3 -c <server> -t 30 on the other. You get the real throughput of exactly that segment: the Wi-Fi, the switch uplink, the site-to-site VPN. Add -R to test the reverse direction and -u to test UDP, which reports jitter and packet loss for voice traffic. It's free, open source and maintained by ESnet.

The trick is placement. A test from a laptop to a server in the same closet isolates the LAN. A test from a branch office to a box at head office isolates the WAN or VPN. Move the server end and you move the question.

MTR combines traceroute and ping into one continuous test. It shows loss and latency at every hop, updated live. On Linux and macOS it's mtr, and on Windows WinMTR does the same job. For an ISP ticket, mtr -rwzc 100 8.8.8.8 produces a 100-cycle report with AS numbers that a carrier's NOC takes seriously.

Pathping on Windows covers some of the same ground, and the troubleshooting guide covers it. MTR's advantage is that it keeps running, so it catches the loss that shows up for 30 seconds every ten minutes.

Wi-Fi analyzers

When the same laptop works on a cable and fails on Wi-Fi, the problem is the radio, the channel, the coverage or the authentication. Wi-Fi analyzers show which one.

Start with what's built in. On Windows, netsh wlan show wlanreport writes an HTML report of the last three days of wireless sessions, including disconnects and their reasons. On a Mac, hold Option and click the Wi-Fi icon to open Wireless Diagnostics, which includes a scanner for nearby networks and channels.

The free and low-cost tier adds a picture. NetSpot runs on Windows and macOS and has a free mode for discovering networks and channels. WiFi Explorer is a paid macOS app that shows channel overlap and signal quality clearly. On Android, the open source WiFiAnalyzer app turns a spare phone into a channel scanner.

Professional surveys are where paid tools earn their price. Ekahau's survey tools and its Sidekick measurement hardware produce heatmaps of coverage, interference and capacity for a whole floor. That's the kit for a new office fit-out or a warehouse with dead zones, and the price puts it in project budgets rather than a single ticket.

Who each fits: built-in reports for Tier 1 and one-user complaints. NetSpot or WiFi Explorer for a tech who handles small offices. Ekahau for teams that design and sell wireless projects.

Free vs paid, and who each fits

Single-fault tools are free and good. Wireshark, Nmap, iperf3 and MTR are open source, actively maintained and standard kit for network engineers. Paying for an alternative rarely buys a better answer to the same question.

Paid tools earn their money in two places. The first is scale: monitoring hundreds of devices across many sites with alerting, reporting and someone to call. The second is specialist work, like a professional Wi-Fi survey with calibrated hardware.

The hidden cost of free is time. A self-hosted Zabbix or LibreNMS server needs patching, backups and someone who knows how it works. Budget those hours like a license, because that's what they are.

Where an RMM fits

Every tool above looks at one device, one path or one network. An MSP technician has a different first question: is this one laptop, or the whole site? An RMM answers that, because its agent already runs on every endpoint.

The approach is to run a diagnostic on every device at the affected site before opening a single remote session. If all 40 devices fail DNS, look upstream. If one does, look at that laptop. Our troubleshooting guide includes a PowerShell script for exactly this check.

In OpenFrame, that script lives in the script library and runs against a device group on Windows and macOS, with results kept in execution history. Scheduled scripts can run the same checks when a device comes back online. Live queries through osquery read interface addresses, routes, the ARP cache and listening ports across the fleet. Remote terminal access through MeshCentral lets you start a pktmon capture, MTR or iperf3 test on the user's machine without a screen share.

Here's what an RMM doesn't replace. OpenFrame isn't an SNMP monitor for your switches and firewalls, so LibreNMS, Zabbix or PRTG still has a job. Think of the RMM as the layer that tells you where to point the other tools. Mingo, the technician-side agent, can write and run those diagnostic scripts and queries for you, with approvals before anything changes.

A starter kit by role

Tier 1 technicians need the built-ins, a Wi-Fi report and the fleet script. That covers scope, reachability and the "is it everyone" question, and it's enough to escalate with evidence.

Tier 2 adds Wireshark, Nmap, iperf3 and MTR. With those four, almost any single fault can be isolated to a device, a link, a hop or a protocol.

Network leads and NOC teams add a monitoring platform and, for wireless-heavy clients, a survey tool. That's the layer that catches the problem before the call comes in.

The short version

Start with the method and the built-in commands. Reach for Wireshark when the commands disagree with the user, Nmap when you don't know what's on the network, iperf3 and MTR when someone says "slow," and a Wi-Fi analyzer when the cable works and the radio doesn't. Add monitoring so you know what normal looked like, and an RMM so you know whether it's one device or fifty.

If you haven't read it yet, the network troubleshooting guide linked at the top is the other half of this post. Install the free tools before the next outage, not during it.

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-tools

Still deciding?

Ask Mingo answers from our docs and customer stories.

Loading related content and questions