Explore the guide library · Windows diagnostic tools
Use protocol-specific observations to investigate a partial connectivity problem while preserving the intended network configuration.
Some connectivity problems affect one address family more than another. Windows tools can collect IPv4 and IPv6 observations separately. Use that evidence to locate a problem rather than disabling IPv6 permanently because one generic guide recommends it.
Choose a suitable destination
Use a public service relevant to the failure and confirm that it publishes the address records needed for the comparison. A service with no IPv6 address cannot serve as a fair test of your IPv6 internet path.
Inspect name information
A targeted lookup for A and AAAA records can show the available IPv4 and IPv6 addresses. Different answers may be normal for a distributed service. Keep the exact hostname constant when comparing the next stage.
Collect limited reachability tests
Microsoft documents /4 and /6 options for ping and route tracing. Use the appropriate option with the intended hostname. Remember that some destinations do not answer diagnostic probes even while their web service works.
Record the complete pattern
- Which address records are available.
- Which protocol-specific tests receive replies.
- Whether another device shows the same pattern.
- Whether the actual application fails at the same time.
Escalate the relevant path
If the difference is consistent across clients, provide the router administrator or provider with the timing and reviewed diagnostic results. If it affects only one computer, inspect its supported adapter and policy configuration.
A failed probe is not enough to justify a permanent protocol change. Likewise, a successful ping does not validate TLS, authentication or application data transfer. Preserve the intended dual-stack setup while identifying the failing stage. After an authorized correction, repeat the same comparison and the original task so the result demonstrates restored usability rather than merely a different fallback path chosen by the application.
Sources and editorial notes
Sources checked 8–9 October 2026. Independent guidance and original illustrations; product comparisons use published specifications rather than hands-on benchmarks. Check the exact model, revision and regional documentation before changing settings.
- Microsoft: ping command and response interpretation
- Microsoft: nslookup reference
- Microsoft: tracert and nonresponding intermediate routers