Read ipconfig all Output Like a Technician and Find Network Faults
Before fixing a network, read it. ipconfig /all prints the complete truth about a connection in ten lines — most faults announce themselves right there.
✍️ Technical Anshu🪟 Windows 10 / 11⏱️ 6 minute read
🎥 Watch the full video — CMD Toolkit V3 GUI, portable software and 5000+ commands shown step by step
The most underrated network tool in Windows costs nothing and needs no installation: ipconfig /all. Beginners run it and see a wall of text; technicians run it and see the diagnosis — because four fields in that output explain almost every 'internet not working' call. This guide teaches you to read those fields like a professional, so you fix the actual fault instead of randomly resetting things. Keep the toolkit closed for ten minutes; this one is about understanding.
The output that confesses everything (recreated panel)
👆 An address starting 169.254, no gateway and no DHCP server — the router never answered. The fault is found before any fix is tried (panel recreated)
1
The Address Itself Tells the First Story
Look at the IPv4 Address line for your active adapter:
An address like 192.168.x.x or 10.x.x.x means the router gave this PC an address — the local connection basically works
An address starting 169.254 is called APIPA: Windows invented it for itself because no DHCP server answered. The fault is now narrowed to the cable, the Wi-Fi link, or the router — not the internet company, not the browser
No address at all, or 'Media disconnected', means the link itself is down — cable out, Wi-Fi off, adapter disabled or dead
2
Gateway and DHCP Server — Who Is in Charge Here
Two more lines confirm the story:
Default Gateway is the router's address and your road to the internet. If it is blank while the address looks normal, the PC can talk to the home network but has no way out
DHCP Server shows who handed out the address — it should match the gateway on a home network. A DHCP server address that belongs to some other device exposes the classic office fault: a rogue router or misconfigured device handing out wrong addresses
DHCP Enabled: No with a wrong static address is the signature of an old manual setting someone forgot — common on PCs that moved between office and home
3
DNS Servers — Why Sites Fail but the Internet Works
The last field solves the most confusing complaint of all — 'internet is connected but nothing opens':
If the address, gateway and DHCP all look right, read the DNS Servers line. DNS is the phone book that turns names into addresses; a wrong or dead DNS makes every website 'not found' while the connection is healthy
A DNS address pointing at a router that is off, or at a random address typed years ago, is the fault
This is also how you prove the fault is the provider's DNS and not the PC — the reading takes thirty seconds and ends all argument
4
Turn the Reading into the Right Fix
Diagnosis first means the fix is now obvious and small:
169.254 address → fix the link or the router's DHCP, not the PC's settings
Blank gateway with static settings → correct the manual configuration or return the adapter to automatic
Everything right except DNS → repair or replace the DNS setting only
Random resetting sometimes cures the symptom while hiding the cause; reading cures the cause. The full video shows these readings alongside the toolkit's network section, where the fixes for each case live.
🎥 See CMD Toolkit V3 Working in the Full Video
The complete walkthrough — GUI interface, portable software and the command library, shown live on a real PC.
What does an IP address starting with 169 254 mean
It means the PC asked the network for an address and nobody answered, so Windows assigned itself a placeholder address from the 169.254 range, called APIPA. The PC cannot reach the internet with it. The fault is between the PC and the router — link, Wi-Fi or the router's DHCP service — not with Windows settings.
How do I know which adapter section to read
ipconfig /all lists every adapter, including old and virtual ones. Read the section for the connection actually in use — 'Wireless LAN adapter Wi-Fi' for Wi-Fi, 'Ethernet adapter' for a cable — and check its Media State says connected. Sections marked Media disconnected are not your problem today.
Can ipconfig fix anything or does it only show information
The plain command and its /all form only report. Its repair switches — release, renew, flushdns — exist and belong to the network-fix workflow, but their results only make sense once you can read the output. Diagnosis is the skill; the switches are just buttons after it.
This guide is based on the Technical Anshu CMD Toolkit V3 video • Stuck on a step? Ask in the video comments — you will get a reply 🙏