Local Machine Fixes: Clearing DNS Cache, Firewall, and Network Services
The standard set of local fixes to try on your own machine before escalating a network issue.
Tools required: ipconfig, netsh, services.msc
Overview
Before assuming a remote site or server is broken, rule out your own machine first. This is the exact same set of fixes an automated tool would try - done by hand, with an explanation of what each one actually does.
Step-by-Step Manual Check
Flush the local DNS cache
Windows caches DNS answers locally - if a site's IP address recently changed, your machine may still be using the old, stale answer.
ipconfig /flushdnsHealthy result
Windows IP Configuration Successfully flushed the DNS Resolver Cache.
Problem result
(command still succeeds, but the problem persists afterward - meaning stale DNS wasn't the cause)
What it means
This command always reports success - it doesn't confirm the fix worked, only that the cache was cleared. Re-run the DNS Resolution guide's nslookup steps afterward to confirm the machine is now getting the current answer.
If unresolved, escalate to: Level 1 — Basic
Release and renew the IP address
Refreshes the machine's own IP address, gateway, and DNS server assignment from DHCP - useful if the machine has been on the same network connection for a long time or recently changed networks.
ipconfig /release
ipconfig /renewRun as two separate commands, in order. Requires an active DHCP server on the network (normal for most office/home networks).
Healthy result
A new lease is obtained, showing a valid IPv4 Address, Subnet Mask, and Default Gateway.
Problem result
"Unable to contact your DHCP server" or the adapter shows no IP address (0.0.0.0 or an APIPA 169.254.x.x address) after renew.
What it means
An APIPA (169.254.x.x) address after renew means the machine could not reach a DHCP server at all - this points to a physical/link-layer problem (cable, Wi-Fi, switch port) rather than anything DNS or firewall related.
If unresolved, escalate to: Level 2 — Intermediate
Reset Winsock and the TCP/IP stack
Winsock is the Windows API layer that all network applications use - corruption here (often from malware removal or a bad driver) can cause unpredictable connectivity issues across every app on the machine.
netsh winsock reset
netsh int ip resetRequires an elevated (Administrator) command prompt. A restart is required after running these for the reset to take effect.
Healthy result
"Successfully reset the Winsock Catalog." / "Restart the computer to complete this action."
Problem result
Command fails with an access-denied error.
What it means
An access-denied error almost always means the prompt wasn't run as Administrator - right-click Command Prompt/PowerShell and choose 'Run as administrator'. This step is intentionally a last-resort reset, not a first thing to try.
If unresolved, escalate to: Level 2 — Intermediate
Confirm the Windows Firewall service itself is running
If the firewall service has stopped or crashed, some tools report this as a generic connectivity failure rather than a clear firewall error.
sc query mpssvcmpssvc is the internal service name for Windows Defender Firewall. Alternative: open services.msc and look for "Windows Defender Firewall".
Healthy result
SERVICE_NAME: mpssvc
STATE : 4 RUNNINGProblem result
STATE : 1 STOPPED
What it means
A stopped firewall service is unusual and often indicates a misconfiguration or third-party security software conflict, not a normal end-user state. Restart the service via services.msc rather than simply leaving the firewall off.
If unresolved, escalate to: Level 2 — Intermediate
Interpreting the Results
These are ordered from least to most invasive on purpose - flush DNS first since it's harmless and instant, and only move to the Winsock reset (which requires a restart) if the earlier steps didn't help.
Common Causes
| Symptom | Likely Cause | Fix |
|---|---|---|
| Site works on phone/other device but not this machine | Stale local DNS cache or local firewall rule on this specific machine | Flush DNS (Step 1) and check local firewall rules per the Ports & Firewall guide. |
| No internet access after connecting to a new network | Stuck DHCP lease from the previous network | Release/renew the IP address (Step 2). |
| Intermittent, unpredictable connectivity across many different apps | Corrupted Winsock catalog or TCP/IP stack, often after malware removal or driver changes | Reset Winsock and the IP stack (Step 3), then restart. |
Automated by
Diagnostic Suite - Network Security Diagnostic & Fix (Option 1)
Runs this exact sequence of local fixes automatically as part of its remediation pass.