How do I trace the network route to a server from Windows?
tracert shows routers that respond to probes along a path toward the destination. It can help identify where a route changes, but intermediate routers may intentionally suppress replies. Asterisks alone do not prove packet loss for your application.
Instructions
1. Run a bounded trace
Use the numeric endpoint to avoid confusing reverse-DNS delays with network latency.
tracert -d -h 20 -w 1000 203.0.113.10-d avoids reverse lookups, -h limits hops, and -w sets the wait per reply in milliseconds.
2. Look for the destination outcome
Check whether the final destination responds and compare its service availability. Intermediate hop addresses represent responding router interfaces, not necessarily a complete or symmetrical picture of the connection path.
3. Record evidence useful to support
Record the test time, your source network, destination and relevant TCP-port result. A comparison from another approved network can distinguish a source-specific problem. Redact internal route addresses before publishing the output.
Check the result
- The trace targets the intended endpoint.
- Any suspected failing segment is supported by destination and service tests, not only silent intermediate hops.
Troubleshooting
- Several hops show asterisks but the service works
- Those routers may not answer the diagnostic probes. Treat the working service result as separate evidence.
- The trace stops before the destination
- Check endpoint service reachability and routing policy; the trace alone cannot locate the responsible device with certainty.
Official references
Use the documentation for your installed version when a flag, service name or platform feature differs.