A network administrator receives a report that a newly assigned workstation on VLAN 25 () cannot access remote intranet services. Upon inspecting the workstation, the administrator observes an auto-configured IPv4 address of . Place the following diagnostic and remediation steps in the correct logical sequence to systematically troubleshoot and resolve this DHCP relay issue from client verification to final resolution.
- 1Run `ipconfig /all` on the local workstation to confirm link status and verify the presence of an APIPA address ().
- 2Temporarily assign a valid static IP () to the workstation and ping the default gateway () to verify local VLAN connectivity.
- 3Inspect the Layer 3 switch or router interface configuration for VLAN 25 to verify the `ip helper-address` directive pointing to the centralized DHCP server.
- 4Verify on the DHCP server that a scope for exists, is activated, and has available addresses in its pool.
- 5Reconfigure the workstation to receive an IP automatically and execute `ipconfig /release` followed by `ipconfig /renew` to confirm lease acquisition.
Cevap
The correct logical sequence begins with client-side verification (`ipconfig /all`), followed by testing local subnet connectivity using a static IP, checking the router's DHCP relay (`ip helper-address`) configuration, confirming DHCP server scope availability for VLAN 25, and finally releasing and renewing the client's lease.
Following the structured troubleshooting methodology, an administrator must first verify client symptoms (APIPA confirmation), isolate local physical and VLAN connectivity using a temporary static IP, verify that the Layer 3 boundary device is properly configured with a DHCP relay agent (`ip helper-address`), ensure the remote DHCP server has an active scope for that subnet, and finally test dynamic acquisition on the client.
Adım Adım Çözüm
Anahtar Kavram
DHCP Relay and APIPA Troubleshooting Methodology across Subnets