A workstation on a corporate network cannot reach a web server located on a remote subnet. Arrange the following diagnostic steps in the correct logical sequence to systematically isolate whether the connectivity issue stems from local TCP/IP settings, the local default gateway, path routing, or router Access Control Lists (ACLs).
- 1Ping the local loopback address () to verify that the local workstation network stack is functional.
- 2Ping the local default gateway address to confirm Layer 2 and Layer 3 reachability within the local subnet.
- 3Execute a `traceroute` command to the remote web server IP address to locate the specific hop where packet loss occurs.
- 4Inspect the routing table and active interface Access Control Lists (ACLs) on the router at the failure hop.
Cevap
The correct sequence begins with testing the local TCP/IP stack (), followed by pinging the default gateway, executing a traceroute to locate the failing hop, and finally inspecting the router table and ACL entries at the failure point.
Structured network troubleshooting progresses from inside to outside: verifying the local host TCP/IP stack first, testing the local default gateway second, running path tracing to pinpoint intermediate failure hops third, and examining router configuration state (routes and ACLs) at the point of failure last.
Adım Adım Çözüm
Anahtar Kavram
Standard Network Troubleshooting Flow for Gateway, Routing, and ACL Faults