A desktop technician is systematically troubleshooting a workstation on a newly configured subnet () that cannot access network resources. The workstation failed to acquire a lease from the enterprise DHCP server located on a separate server subnet (). Following standard troubleshooting methodology from the local client to the centralized infrastructure, in what order should the technician perform these diagnostic and verification steps?
- 1Run `ipconfig /all` on the local workstation to confirm link status and verify the assigned automatic private IP address.
- 2Verify that the access switch port connected to the workstation is assigned to the correct VLAN and operating at full-duplex.
- 3Inspect the default gateway interface configuration on the Layer 3 switch to ensure the correct `ip helper-address` is configured.
- 4Audit the centralized DHCP server scope for subnet to verify active pool authorization and address availability.
Cevap
The correct logical sequence begins with checking the local host IP configuration via `ipconfig /all`, followed by verifying switch port VLAN assignment, then checking the `ip helper-address` configuration on the gateway router, and finally auditing the centralized DHCP server scope for available addresses.
The standard troubleshooting methodology moves systematically from the affected endpoint up to the remote infrastructure. First, verifying the local host configuration with `ipconfig /all` identifies symptoms such as APIPA assignment. Next, checking the physical/datalink switchport ensures the client is in the proper VLAN segment. Third, checking the gateway's IP helper address verifies that DHCP broadcast requests are properly relayed across subnets to the server's IP address. Finally, auditing the central DHCP server scope verifies server-side availability and pool capacity.
Adım Adım Çözüm
Anahtar Kavram
Methodological IP and DHCP Service Troubleshooting
Tahmini Süre:1m 30s