Shared server guidance

Windows network & HTTP diagnostics

Test the client-side network path, DNS answers, TCP ports and HTTP responses before changing a remote server.

10 practical answersClear prerequisites and verification

Filter these questions

10 guides

How do I test whether a server TCP port is reachable from Windows?

Use Test-NetConnection for a specific server TCP port, interpret its result correctly, and distinguish reachability from application health.

Run a bounded Windows ping test, read packet-loss and latency results, and recognise why missing replies do not prove a server is offline.

Use Windows tracert to inspect a server route, limit probe time, and interpret silent intermediate hops without assuming a network failure.

Query server A and AAAA records using PowerShell or CMD, compare expected addresses, and distinguish DNS answers from server availability.

Clear a stale local Windows DNS cache after checking the published record, then retest resolution without changing server DNS configuration.

Read local Windows network configuration before troubleshooting server access, identify VPN adapters, and avoid changing the active connection.

Find a local Windows TCP listener and its owning process before diagnosing an SSH tunnel or application port conflict.

Test server access separately over IPv4 and IPv6, compare DNS records and SSH results, and avoid disabling IPv6 as a blanket fix.

Use curl.exe to inspect HTTPS status and headers from Windows, follow redirects deliberately, and keep certificate verification enabled.

Inspect Windows WinHTTP proxy settings and client behaviour, distinguish HTTP proxying from SSH, and preserve managed network policy.