When your internet stops working or slows to a crawl, the instinct is to search for some tool to download. But Windows 11 already ships with a complete set of network diagnostic tools — accessible through Command Prompt — that can identify most connectivity issues without installing a single thing.
This guide covers every major built-in network diagnostic tool in Windows 11, explains what each one does, when to use it, and how to read the output so you can pinpoint exactly where your connection is failing.
Why You Do Not Need to Download Anything to Diagnose Internet Problems
Most internet problems — whether it is a DNS failure, packet loss, a bad IP configuration, or a routing issue — can be identified using commands that are already part of Windows. These are the same tools that network engineers and IT support professionals use daily. They are not hidden or advanced. They are simply underused.
What Windows 11 Already Has Built In
Windows 11 includes the following network diagnostic commands out of the box:
- ipconfig — view and manage IP address configuration
- ping — test basic connectivity to a host
- pathping — identify packet loss at each network hop
- tracert — trace the route data takes across the internet
- nslookup — query DNS servers and test name resolution
- netstat — display active connections and listening ports
In addition to these command-line tools, Windows 11 also includes a GUI-based Network Troubleshooter that can detect and sometimes auto-fix common issues like disabled adapters or misconfigured DNS settings.
When to Use Built-In Tools vs Third-Party Tools
Built-in tools cover the vast majority of home and small office network diagnostics. If you need to check whether your DNS is resolving, whether your router is reachable, or whether a specific hop in your network path is dropping packets — these tools handle it.
Third-party tools become useful only when you need continuous network monitoring, advanced packet capture, or visual traceroute mapping. For standard troubleshooting — especially when your internet is already down and you cannot download anything — the Windows 11 network commands list covered here is exactly what you need.
How to Open Command Prompt for Network Diagnostics on Windows 11
Before running any diagnostic command, you need to open Command Prompt. Here is the fastest way on Windows 11:
- Press Windows + S to open search.
- Type cmd.
- Right-click Command Prompt and select Run as administrator.
Running as administrator is important because some commands — like ipconfig /release and ipconfig /renew — require elevated privileges to modify network settings. If you open a standard Command Prompt, those commands will fail silently or return an access denied error.
Once the Command Prompt window is open, you are ready to start diagnosing. Every tool covered in this guide runs directly from this window.
Tool 1 — ipconfig — Check Your IP Address and Network Configuration
The ipconfig command is usually the first tool to reach for when diagnosing internet problems on Windows 11. It displays your current IP address, subnet mask, default gateway, and DNS server — the foundational details that determine whether your device can even communicate with the network.
If any of these values are missing, incorrect, or showing a self-assigned address, you have found the source of the problem before running any other command.
What ipconfig Shows and What Each Line Means
Open Command Prompt and type:
ipconfigThe output will show each network adapter on your system. For your active connection, the key lines are:
- IPv4 Address — the IP address assigned to your device by the router
- Subnet Mask — defines the range of your local network (typically 255.255.255.0)
- Default Gateway — the IP address of your router, which is the exit point to the internet
If the Default Gateway field is blank, your device is not connected to a router — which explains why the internet is not working. This is one of the most common findings when troubleshooting scenarios like ethernet connected but no internet.
ipconfig /all — Full Network Adapter Details
For a more detailed view, run:
ipconfig /allThis adds critical fields like DNS server addresses, DHCP status, MAC address, and lease duration. If you suspect a DNS issue — for instance, pages not loading even though you can ping IP addresses — checking the DNS server listed here is the logical next step.
ipconfig /flushdns — Clear DNS Cache
Windows caches DNS lookups locally. If a website recently changed its IP address, or if a corrupted cache entry is causing resolution failures, clearing it can fix the issue immediately:
ipconfig /flushdnsThis command purges all stored DNS records and forces Windows to query the DNS server fresh on the next request.
ipconfig /release and /renew — Reset Your IP Address
If your device has a bad or conflicting IP address, you can request a new one from the DHCP server:
ipconfig /release
ipconfig /renewThe /release command drops your current IP. The /renew command requests a fresh assignment from the router. This is particularly useful after switching networks, reconnecting cables, or recovering from a router reboot.
What a 169.254 IP Address Means and Why It Is a Problem
If your IPv4 address starts with 169.254, it means Windows failed to reach the DHCP server and assigned itself an Automatic Private IP Address (APIPA). This is not a valid routable address — you will have no internet access.
Common causes include a disconnected cable, a router that is not responding, or a DHCP service failure. The fix usually starts with running ipconfig /release followed by ipconfig /renew. If the 169.254 address persists, the issue is between your device and the router — not beyond it.
Tool 2 — ping — Test If Your Connection Is Reaching a Destination
Once you have confirmed your IP configuration with ipconfig, the next step is testing whether your device can actually reach another host. That is exactly what ping does — it sends small packets to a target and measures whether a response comes back and how long it takes.
How to Use Ping for Basic Connectivity Testing
The basic syntax is:
ping 8.8.8.8This sends four ICMP echo requests to Google’s DNS server. If all four return a reply with a time value in milliseconds, your connection to the internet is working at the IP level. If replies come back but websites still do not load, the problem is likely DNS — not connectivity.
For a deeper walkthrough of using this command to isolate issues, see this ping command troubleshooting guide.
How to Use ping -t for Continuous Testing
The standard ping command sends only four packets, which is not always enough to detect intermittent issues. Adding the -t flag keeps the test running indefinitely:
ping -t 8.8.8.8This is useful when you suspect your connection is dropping at random intervals. Let it run for a few minutes, then press Ctrl + C to stop and review the summary. If you see scattered “Request timed out” lines between successful replies, you are dealing with intermittent packet loss.
What Ping Results Tell You About Your Internet Connection
Each reply line includes a time value — this is your latency, measured in milliseconds. For a typical home connection, anything under 30ms to a nearby server is normal.
Two common error messages require attention:
- Request timed out — the packet was sent but no reply came back. This could indicate packet loss, a firewall blocking ICMP, or a dead route. If it happens consistently, follow this request timed out fix.
- Destination host unreachable — your device cannot find a path to the target at all. This usually points to a local network or gateway problem and is covered in detail in this destination host unreachable fix.
Tool 3 — pathping — Find Exactly Which Hop Has Packet Loss
While ping tells you whether a destination is reachable, it does not tell you where the problem is along the route. The pathping command in Windows 11 fills that gap — it combines route tracing with packet loss measurement at every hop between you and the target.
What Makes pathping Better Than ping and tracert Combined
A standard ping only tests the endpoint. A tracert shows each hop but does not measure loss. The pathping command does both — it first maps the entire route, then sends packets to every hop over a period of time and calculates loss percentages at each one. This makes it the single most effective built-in tool for finding where a connection degrades.
How to Run pathping on Windows 11
Open Command Prompt as administrator and type:
pathping 8.8.8.8The command will first display each hop (similar to tracert), then spend approximately 25 seconds per hop collecting packet loss data. For a route with 10 hops, expect the full test to take around four to five minutes. Do not interrupt it — the loss statistics only appear after the collection phase completes.
How to Read pathping Output Line by Line
After the collection phase, pathping displays a table with two key columns:
- This Node/Link — the percentage of packets lost at that specific hop
- Source to Here — cumulative loss from your device to that hop
A healthy route shows 0% across all hops. If a specific hop shows significant loss — say 15% or higher — that node is where the degradation is occurring.
What Packet Loss on a Specific Hop Actually Means
If the hop showing loss is your default gateway (hop 1), the problem is local — your router, cable, or Wi-Fi signal. If loss appears at hop 2 or 3, it is likely within your ISP’s infrastructure. If loss only appears at the final hop, the destination server itself may be under load or rate-limiting ICMP traffic, which is not always a real problem.
The key distinction is whether packet loss at a mid-route hop also affects all subsequent hops. If hops after the problematic node recover to 0%, the node in question may simply deprioritize ICMP responses — which is normal and not a sign of actual data loss.
Tool 4 — tracert — Map the Route Your Data Takes to a Destination
The tracert (trace route) command maps every hop your data passes through on its way to a destination. Each hop is a router or network node — and tracert reports the round-trip time to each one. This gives you a visual picture of the path and helps identify where delays or failures occur along the route.
When to Use tracert Instead of pathping
Use tracert when you need a quick view of the route without waiting several minutes for a full loss analysis. While pathping is more thorough, it takes significantly longer. If you simply want to see where traffic stops — for example, whether it gets past your ISP before failing — tracert delivers that answer in seconds.
Run it with:
tracert 8.8.8.8Each line in the output represents one hop. If a hop shows asterisks (* * *) instead of time values, that router is either not responding to ICMP or the route is broken at that point. If all hops after a certain point time out, the failure is occurring at or just beyond that node.
How to Read Each Hop in tracert Output
Each row in the tracert output contains three time values (in milliseconds) and the hop’s IP address or hostname. The three values represent three separate round-trip measurements. Consistent times across all three indicate a stable connection to that hop. A sudden spike — for example, jumping from 15ms to 180ms — suggests congestion or a routing issue at that specific node.
The first hop is always your local gateway (router). The final hop is the destination. Every hop in between belongs to your ISP or upstream transit providers.
Each packet sent by tracert carries a TTL (Time to Live) value that increases by one for each hop. This is the mechanism that forces each successive router to reveal itself. For a detailed walkthrough of interpreting every line, see this guide on how to read tracert results.
Tool 5 — nslookup — Test and Diagnose DNS Problems
DNS translates domain names like google.com into IP addresses your device can route to. When DNS fails, websites stop loading — even though your underlying internet connection may be perfectly fine. The nslookup command lets you test whether DNS resolution is working and which server is handling your queries.
How to Use nslookup to Check If DNS Is Working
Type the following into Command Prompt:
nslookup google.comIf DNS is functioning, you will see the server that handled the query and the resolved IP address for google.com. If you get a timeout or a “DNS request timed out” error, your configured DNS server is either unreachable or not responding. This exact scenario is covered in detail in this DNS server not responding fix guide.
How to Use nslookup to Test a Different DNS Server
One of the most useful features of nslookup is the ability to query a specific DNS server directly. This tells you whether the problem is with your current DNS server or with DNS in general:
nslookup google.com 8.8.8.8This sends the query to Google Public DNS{:target=”_blank” rel=”nofollow”} instead of your default server. You can also test with Cloudflare DNS at 1.1.1.1{:target=”_blank” rel=”nofollow”}:
nslookup google.com 1.1.1.1If one of these public DNS servers resolves the domain successfully while your default server does not, switching your DNS settings to that working server is the fastest fix.
What nslookup Output Tells You About Your Connection
The nslookup output contains two sections. The first shows the DNS server that handled the request — its name and IP address. The second shows the result — the domain name and its corresponding IP addresses.
If the server section says “UnKnown,” it means your DNS server did not return a reverse lookup for its own address. This is common and not necessarily an error. What matters is whether the answer section returns valid IP addresses. If it does, DNS is working. If it does not, the issue is either with the DNS server itself or with the network path between your device and that server.
Tool 6 — netstat — See All Active Network Connections
The netstat command shows every active network connection on your Windows 11 machine — including which processes are communicating, which ports are in use, and the state of each connection. While tools like ping and tracert test outbound connectivity, netstat looks inward at what your device is already doing on the network.
How to Use netstat to Find Active Connections
Open Command Prompt and type:
netstatThe default output lists all current TCP connections, showing the local address and port, the foreign (remote) address and port, and the connection state. This gives you a snapshot of every active communication between your device and external servers.
If you notice connections to unfamiliar addresses or an unusually high number of established sessions, it may indicate background processes consuming bandwidth or, in rarer cases, unauthorized network activity.
netstat -an — View All Ports and Connection States
For a more complete picture, use:
netstat -anThe -a flag includes listening ports — services waiting for incoming connections — and the -n flag displays addresses and ports numerically instead of resolving hostnames. This makes the output faster and easier to scan.
Each connection will show one of several states:
- ESTABLISHED — an active, open connection
- LISTENING — a port is open and waiting for connections
- TIME_WAIT — a connection that recently closed and is being cleaned up
- CLOSE_WAIT — the remote side has closed, but the local application has not released the connection yet
A large number of connections in CLOSE_WAIT can indicate an application that is not properly releasing resources, which sometimes contributes to network slowdowns or port exhaustion.
When netstat Is Useful for Troubleshooting
Use netstat when your internet is technically working but performance is degraded and you cannot identify why. It helps answer questions like: Is something on my machine making excessive connections? Is a specific port blocked or already in use? Are there connections to addresses I do not recognize?
It is also valuable when setting up applications that require specific ports — such as game servers or remote desktop — to verify whether those ports are actively listening.
Tool 7 — Windows Network Troubleshooter — When to Use It and Its Limits
Windows 11 includes a built-in GUI-based Network Troubleshooter that attempts to detect and automatically fix common connectivity problems. It is not a command-line tool, but it deserves mention because it handles a few specific scenarios faster than manual diagnosis.
How to Run the Built-In Network Troubleshooter
To launch it on Windows 11:
- Open Settings (Windows + I).
- Navigate to System → Troubleshoot → Other troubleshooters.
- Find Network and Internet and click Run.
The troubleshooter will scan your network adapters, check DNS settings, verify gateway connectivity, and attempt to identify the issue. If it finds a fixable problem — such as a disabled adapter or a reset DNS configuration — it will offer to apply the fix automatically.
What It Can and Cannot Fix
The Network Troubleshooter works well for simple issues: a Wi-Fi adapter that was accidentally turned off, a DNS configuration that needs resetting, or a network profile that needs switching from public to private. It handles these reliably and saves time.
However, it cannot diagnose packet loss along a route, identify which hop is failing, detect DNS server performance issues, or troubleshoot anything beyond the most surface-level problems. If the troubleshooter reports “Windows can’t identify the problem” or applies a fix that does not resolve the issue, that is when the command-line tools covered earlier become essential.
Think of it as a useful first step — but not a replacement for the diagnostic depth that ipconfig, ping, pathping, tracert, nslookup, and netstat provide.
Which Tool to Use for Each Internet Problem — Quick Reference Table
| Problem | Best Tool | Command Example |
|---|---|---|
| No IP address or wrong IP assigned | ipconfig | ipconfig /all |
| Need to reset IP configuration | ipconfig | ipconfig /release then /renew |
| Websites not loading, suspect DNS | nslookup | nslookup google.com 8.8.8.8 |
| Stale DNS cache causing failures | ipconfig | ipconfig /flushdns |
| Cannot reach any website or server | ping | ping 8.8.8.8 |
| Intermittent connection drops | ping | ping -t 8.8.8.8 |
| Need to find where packet loss occurs | pathping | pathping 8.8.8.8 |
| Need a quick route map to a server | tracert | tracert google.com |
| Unknown background connections | netstat | netstat -an |
| Simple adapter or profile issue | Network Troubleshooter | Settings → Troubleshoot |
This table covers the most common scenarios. In many cases, effective diagnosis involves chaining two or three tools — starting with ipconfig to verify configuration, moving to ping for connectivity, and then using pathping or nslookup depending on what the symptoms suggest.
Frequently Asked Questions
What network diagnostic tools are built into Windows 11?
Windows 11 includes ipconfig, ping, pathping, tracert, nslookup, and netstat — all accessible through Command Prompt. It also includes a GUI-based Network Troubleshooter in Settings. Together, these tools cover IP configuration checks, connectivity testing, route tracing, DNS diagnosis, packet loss detection, and active connection monitoring — without requiring any downloads.
How do I diagnose internet problems on Windows 11 without downloading anything?
Start by opening Command Prompt as administrator. Run ipconfig to check your IP configuration. Use ping 8.8.8.8 to test basic internet connectivity. If ping works but websites do not load, run nslookup google.com to test DNS. If the connection is intermittent, use pathping to find where packet loss is occurring. These built-in network diagnostic tools in Windows 11 handle nearly every common scenario.
What does ipconfig /flushdns do in Windows 11?
The ipconfig /flushdns command clears the local DNS resolver cache stored by Windows. This cache holds recently looked-up domain-to-IP mappings. Flushing it forces your system to query the DNS server fresh on the next request, which resolves issues caused by outdated or corrupted cache entries — such as websites failing to load after a server migration.
What does a 169.254 IP address mean in Windows 11?
A 169.254.x.x address is an Automatic Private IP Address (APIPA). Windows assigns it when your device fails to contact a DHCP server — meaning it could not get a valid IP from your router. This results in no internet access. The typical causes are a disconnected network cable, a router that is powered off or frozen, or a DHCP service failure on the router itself.
What is pathping and how is it different from ping?
The ping command tests whether a destination is reachable and measures round-trip time. It only tests the endpoint. The pathping command goes further — it maps every hop between your device and the destination, then measures packet loss at each one over a sustained period. This makes pathping the better tool when you need to identify exactly where along the route a problem is occurring.
How do I use pathping to find packet loss in Windows 11?
Open Command Prompt as administrator and run pathping 8.8.8.8 or replace the IP with any destination you want to test. The command will first list each hop, then spend several minutes collecting loss data. After it finishes, review the “This Node/Link” column — any hop showing significant loss percentage is where the degradation is happening.
How do I use nslookup to test DNS on Windows 11?
Type nslookup google.com in Command Prompt. If it returns an IP address, your DNS is working. To test a specific DNS server, add it after the domain — for example, nslookup google.com 8.8.8.8. If your default DNS fails but a public DNS server succeeds, switching your DNS settings to that server is the fastest resolution.
What does netstat show in Windows 11?
The netstat command displays all active TCP/UDP connections on your machine, including local and remote addresses, port numbers, and connection states. Running netstat -an gives the most complete view — showing established connections, listening ports, and connections in transitional states like TIME_WAIT or CLOSE_WAIT.
How do I open Command Prompt for network diagnostics in Windows 11?
Press Windows + S, type cmd, right-click Command Prompt, and select Run as administrator. Running as administrator is necessary because several diagnostic commands — particularly ipconfig /release and ipconfig /renew — require elevated privileges to modify network settings.
What is the best built-in tool to diagnose slow internet on Windows 11?
For slow internet specifically, pathping is the most effective built-in tool. It identifies packet loss at each hop along the route, which is the most common cause of perceived slowness beyond your local network. If pathping shows loss at hop 1, the issue is local — your router or Wi-Fi. If loss appears at hops managed by your ISP, the problem is on their side and outside your control.
Every tool covered in this guide is already installed on your Windows 11 machine and ready to use from Command Prompt. Between ipconfig, ping, pathping, tracert, nslookup, and netstat, you have enough diagnostic capability to isolate whether a problem is local, DNS-related, ISP-side, or destination-side — without downloading a single utility.
If your diagnostics consistently show packet loss or failures beyond your first hop — particularly at hops belonging to your ISP — and restarting your router does not resolve the issue, that is the point to contact your internet service provider with your findings. Sharing pathping or tracert output with their support team gives them specific, actionable data and typically speeds up resolution significantly.