A network technician is systematically troubleshooting a connectivity failure from a client workstation to a remote application server. Place the following command-line utilities in the logical order they should be executed to isolate the issue from local interface settings out to remote route reachability.
- 1Execute `ipconfig /all` to verify local host network configuration and default gateway assignment.
- 2Execute `ping 192.168.1.1` to test ICMP reachability to the local default gateway.
- 3Execute `tracert 10.0.50.25` to trace the hop-by-hop routing path to the remote server.
- 4Execute `nslookup app.corp.internal` to verify DNS host name resolution for the target server.
Answer
The correct logical order begins with checking local IP settings using `ipconfig`, verifying local gateway reachability using `ping`, tracing the remote path using `tracert`, and verifying DNS resolution using `nslookup`.
Standard network troubleshooting follows a logical sequence from local host configuration (`ipconfig`), to local subnet reachability (`ping`), to multi-hop path analysis (`tracert`), and finally upper-layer services like DNS resolution (`nslookup`).
Step-by-Step Solution
Key Concept
Structured Command-Line Diagnostic Sequence