A network technician is systematically troubleshooting a workstation that is unable to access an internal web portal (`app1.corp.internal`). Order the command-line network utilities in the correct logical sequence to isolate this issue, following a bottom-up methodology from local host configuration to remote transport port verification.
- 1Run `ipconfig /all` to verify local host IP address assignment, subnet mask, and default gateway settings.
- 2Run `ping 192.168.1.1` to test Layer 3 ICMP reachability to the local default gateway.
- 3Run `nslookup app1.corp.internal` to confirm DNS name resolution maps the FQDN to the expected destination IP ().
- 4Run `tracert 10.10.50.20` to identify intermediate router hops and locate upstream packet loss or drop points.
- 5Run `Test-NetConnection 10.10.50.20 -Port 443` to evaluate TCP socket state and remote application port availability.
Cevap
The correct troubleshooting sequence is: 1) `ipconfig /all` to verify local host configuration, 2) `ping` the default gateway to confirm local subnet communication, 3) `nslookup` the FQDN to confirm proper DNS resolution, 4) `tracert` the destination IP to pinpoint routing path failures, and 5) `Test-NetConnection -Port 443` to verify remote transport port availability.
A systematic bottom-up OSI troubleshooting workflow begins at Layer 1/2/3 local host configuration (`ipconfig`), moves to local network reachability (`ping` gateway), confirms DNS resolution (`nslookup`), traces path routing to the destination IP (`tracert`), and concludes with transport port verification (`Test-NetConnection`).
Adım Adım Çözüm
Anahtar Kavram
Bottom-Up Command-Line Network Troubleshooting Sequence