Category: Windows diagnostic tools
Compare IPv4 and IPv6 on Windows without disabling a protocol as a shortcut
Use protocol-specific observations to investigate a partial connectivity problem while preserving the intended network configuration.
Read guideEthernet and Wi-Fi are both connected: which path is Windows testing?
Read the selected interface before using a successful test as proof that a new Ethernet adapter works.
Read guideBuild an internet-outage log that support can actually use
Capture the time, affected devices and failing stage before a restart erases useful clues.
Read guideBefore sharing a network report: remove private details and keep the useful evidence
Share a targeted extract with trusted support instead of posting an entire diagnostic archive publicly.
Read guideRead ipconfig without confusing Wi-Fi, Ethernet and VPN adapters
Identify the interface carrying your connection before interpreting its address, gateway and DNS information.
Read guideUse the Windows wireless report to investigate repeated disconnects
Match recorded wireless sessions to the time of a real failure and preserve the report before changing drivers or profiles.
Read guidePing your home gateway: what replies, delays and timeouts actually tell you
Use a short gateway test to examine the local path without mistaking every unanswered packet for an internet outage.
Read guideWhen flushing the Windows DNS cache helps—and when it does not
Use a DNS cache flush for a plausible stale-resolution problem, then verify the same hostname and application.
Read guideRead an nslookup result without confusing the DNS server with the website
Separate the resolver being queried from the name and addresses returned for your destination.
Read guideWhy tracert shows asterisks even when a website still works
Read intermediate timeouts as missing diagnostic replies before blaming a particular internet router.
Read guide