Windows Network Diagnostic: Connectivity & Latency Check
WINDOWS
The Challenge
Network troubleshooting is notoriously difficult when relying on end-user descriptions like "the internet is slow." IT support often needs to determine if the issue is the local Wi-Fi, the ISP, or a specific business application server. Traditionally, this involves guiding a user through opening Command Prompt, running multiple commands (ping, ipconfig, tracert), and reading results back over the phone—a frustrating experience for everyone.
The goal was to execute a single, comprehensive diagnostic to:
- Verify local connectivity to the Gateway and Internet (DNS)
- Map the local network segment (ARP Table) to identify potential conflicts
- Trace the route to a critical business application to pinpoint latency bottlenecks
- Confirm all findings without changing any settings (Read-Only)
The Prompt Sent to Myrmex
Using the Myrmex Agent (Perseus) installed on the target device, we sent:
Perform a non-intrusive network diagnostic from this Windows host. Execute pings to the local
gateway and a public DNS (8.8.8.8) to verify connectivity, list the current ARP table to
map local communications, and run a trace to a specific business URL to identify latency points.
Report the results clearly without modifying any network adapters or routing tables.
Note: Myrmex orchestrates standard networking tools like ICMP Echo Requests and ARP cache retrieval to build a complete connectivity profile in seconds.
What Myrmex Did
Myrmex executed a read-only network diagnostic on host DEMO-WIN11.
🛡️ Network Diagnostic Report: DEMO-WIN11
📊 Connectivity Summary
| Target | Destination | Status | Avg. Latency | Outcome |
|---|---|---|---|---|
| Local Gateway | 10.255.254.254 | ✅ Success | 8.75 ms | Local segment is reachable and stable. |
| Public DNS | 8.8.8.8 | ✅ Success | 26.5 ms | External connectivity is functional. |
| Business URL | myrmex.ai | ✅ Success | 25.0 ms | End-to-end path is clear (11 hops). |
Technical Deep Dive
1. Interface Configuration
The diagnostic confirmed the device is using Wi-Fi with IP 10.255.254.5. IPv6 is enabled and functioning, ensuring compatibility with modern network stacks.
2. Local Communication (ARP Table)
The ARP cache provided a hardware mapping for the gateway (02-10-18-78-19-7c), confirming that Layer 2 communication is established and correct. This rules out issues like IP conflicts or ARP spoofing at a glance.
3. Latency & Path Analysis
The traceroute to myrmex.ai revealed a healthy path:
- Internal: Exit via Gateway at 7ms (acceptable for Wi-Fi).
- ISP Edge: Consistent latency (~17ms) through the carrier network.
- Destination: Final landing at 25ms. No packet loss or high-latency hops were found, exonerating the network from "slowness" complaints.
Benefits of the Approach
⚡ Rapid Isolation
Within seconds, you know if the problem is local (Gateway failure), ISP-related (High latency at hop 2-3), or specific to the destination.
🛡️ Zero-Touch Safety
The diagnostic is strictly read-only. It gathers data without resetting adapters or flushing DNS caches, ensuring no disruption to active user sessions.
📉 Evidence-Based Support
Instead of guessing, you have a documented baseline of network performance (Latency, Jitter, Path) to share with ISPs or infrastructure teams.
Result
With Myrmex analysis:
- ✅ Connectivity Verified: Validated full path from LAN to WAN.
- ✅ Hardware Confirmed: Active Adapter and ARP mapping are correct.
- ✅ Performance Baseliend: Established that 25ms latency is normal for this endpoint.
Prompt Variations
The same pattern can be used for other network tasks:
For Wi-Fi signal analysis:
Report the current Wi-Fi Signal Strength (RSSI), Channel, and BSSID.
List all other visible networks in range to check for interference.
For DNS troubleshooting:
Perform an NSLOOKUP for 'google.com' using the configured DNS server
and compare the result with a query to '1.1.1.1'.