NetDiag: Free Portable Network Diagnostic Tool for Windows

You’re sitting in front of someone else’s machine. No admin rights. Can’t install anything. The network is acting up and you need answers right now. Sound familiar? Whether you’re a sysadmin doing a quick on-site visit, a support tech walking a user through troubleshooting, or a developer who just needs to know if port 443 is reachable — you need a tool that works instantly, from a single file, without leaving a trace.

That’s exactly why NetDiag exists. A lightweight, portable network diagnostics utility for Windows that gives you a full picture of the connection state in seconds. No installation. No registry writes. No drama.

In this guide we’ll cover what NetDiag does, how to use it, who it’s for, and why it belongs on every sysadmin’s USB drive.

Diagnosis: Why Standard Windows Tools Aren’t Enough

Sure, you can open a CMD and start typing ipconfig, ping, tracert, nslookup… one by one, copying results into Notepad, switching windows. It works. It’s also tedious, error-prone, and slow when you’re under pressure.

The real problem: there’s no single built-in tool that aggregates everything into one clean, color-coded report. You’re always stitching together a picture from five different commands. NetDiag fixes that.

What NetDiag Checks — Full Feature List

Hit the «Check» button and within a few seconds NetDiag gives you a structured, color-coded diagnostic report covering all the essentials:

• External IP — Detects your public IP address via multiple independent services with automatic failover between them.
• Local IP & MAC address — Displays all IP addresses on the active network interface (comma-separated if multiple) and the physical adapter address.
• Gateway & DNS — Shows the default gateway and all configured DNS servers.
• Address type & DHCP server — Tells you whether the IP was assigned automatically (DHCP) or configured manually (Static). If DHCP, it shows the server that issued the settings.
• DNS resolution — Verifies that a domain name resolves correctly to an IP address.
• Ping — Sends 3 packets to the target host and reports round-trip time and packet loss percentage.
• MTU / MRU — Discovers the actual maximum transmission unit by sequentially testing packet sizes from 1472 down to 576 bytes with the Don’t Fragment flag set.
• Port checks — Tests TCP ports 80 and 443 by default; you can add any custom ports via comma-separated input (e.g. 22, 3389, 8080).
• Traceroute — Launches a route trace to the target host in a separate command prompt window, one click.
• Summary — After all checks, displays either «All OK» or a specific list of detected issues.

What the Output Looks Like

After pressing «Check», here’s the kind of report you’ll see:

External IP         93.185.12.4
Local IP            192.168.1.5
MAC Address         A4-BB-6D-11-22-33
Gateway             192.168.1.1
DNS                 192.168.1.1, 8.8.8.8
Address Type        DHCP
DHCP Server         192.168.1.1
Host → IP           142.250.185.46
Ping                4 ms  (3/3)
MTU / MRU           1500 bytes  (standard)
Port 80 (HTTP)      open
Port 443 (HTTPS)    open
------------------------------------------------
✓  All OK — network is functioning normally

If something’s wrong, the green summary line is replaced by a red one listing exactly what failed. Color coding makes problem fields immediately obvious: green = normal, yellow = warning, red = error. No guesswork.

Key Features That Make It Actually Useful

• Truly portable — A single .exe file. No installation, no registry entries, no leftovers. Run it from a USB drive, a shared folder, or a desktop shortcut.
• Smart URL parsing — Paste a full URL like https://site.com/page?id=1 and NetDiag automatically strips the protocol, path, and query parameters — leaving only the host to test against.
• Multi-adapter aware — Automatically identifies the active network interface and lists all its IP addresses.
• Custom port testing — Beyond the default 80/443, test any ports you need: 22, 3306, 8080, 27017 — whatever your stack requires.
• One-click traceroute — No need to open a separate terminal; launch tracert right from the UI.
• Log saving — Export the full diagnostic report to a text file or copy it to the clipboard. Ideal for pasting into a ticket or sending to a colleague.
• Stop button — Interrupt a check at any point without closing the app.
• Modern dark UI — Color-coded results, built-in Help button. Looks like a tool someone actually cared about building.

Who Should Have This on Their USB Drive

NetDiag is genuinely useful for several groups:

• System administrators — Quick first-pass diagnostics without hauling out heavy toolkits. Especially valuable on machines you can’t modify.
• Help desk & support teams — Send the user a single file, ask them to run it and paste the result. No instructions needed, no confusion.
• Developers — Quickly verify service reachability, port availability, and DNS resolution in any environment.
• Power users & small business owners — Want to know why a site or service isn’t loading? NetDiag gives you a real answer, not just «have you tried restarting your router.»

How to Run It — Takes About 30 Seconds

1. Download netdiag.zip and extract it.
2. Double-click netdiag.exe — no installation required.
3. Enter a hostname or IP address in the «Host / IP» field.
4. Optionally, add custom ports separated by commas.
5. Click «Check» and wait a few seconds for the full report.

That’s it. No wizards, no UAC prompts (unless you’re on a locked-down corporate machine — in that case, right-click → Run as Administrator).

Under the Hood: Technical Details

NetDiag is written in C++ using the native Windows API (WinAPI). It compiles to a single self-contained .exe with no external dependencies — no .NET runtime, no Python, no third-party DLLs. File size is approximately 3 MB with static linking.

Like any unsigned native executable, some antivirus engines may flag it based on ML heuristics. This is a false positive. Major AV vendors — Kaspersky, Dr.Web, Bitdefender, ESET — report the file as clean. Source code is available upon request for review.

Possible «Side Effects» — Known Limitations

• External IP detection requires internet access (obviously). On fully isolated networks, that field will show an error — everything else still works.
• MTU detection via ICMP may not work on networks that block ICMP traffic. The tool will report the limitation rather than silently fail.
• Traceroute opens a separate CMD window by design — this is standard Windows tracert behavior.
• No Linux/macOS version. This is a Windows-native tool, built with WinAPI. For cross-platform diagnostics, look at tools like mtr, nmap, or custom shell scripts.

Best Practices: Make It Part of Your Toolkit

Keep it on a USB drive. Seriously. The whole point of portability is having it available when you need it on a machine that isn’t yours. A drive with NetDiag, Autoruns, Process Explorer, and Wireshark covers 80% of field diagnostics.

Use it as a first-line triage tool. Before digging into firewall rules, DNS configs, or application logs — run NetDiag. It takes 10 seconds and often tells you exactly where the problem is (or rules out the obvious causes).

Save the log. When escalating tickets or asking for help in forums, paste the NetDiag output. It gives responders everything they need without the back-and-forth of «what’s your IP?», «what DNS are you using?», «can you reach the gateway?».

Wrapping Up: The Prescription

NetDiag won’t replace Wireshark for deep packet inspection or Zabbix for infrastructure monitoring. But it was never meant to. It fills a specific, real gap: fast, portable, no-install network triage in a single executable.

For sysadmins, support engineers, and developers who regularly work across different machines and environments, that’s an extremely valuable thing to have available. Download it, throw it on your USB drive, and forget about it until you need it. You’ll be glad it’s there.

→ Download NetDiag (netdiag.zip)

Have feedback, feature requests, or found a bug? Drop a comment below — the author is listening. And if NetDiag saved your day, share it with a colleague who’s still tabbing between five CMD windows.

Next up: how to automate network diagnostics across multiple hosts using PowerShell and send results to a Telegram bot — so you know about problems before your users do.