A network administrator is troubleshooting an issue where client workstations on a newly p… — CompTIA Network+

A network administrator is troubleshooting an issue where client workstations on a newly provisioned VLAN are receiving APIPA addresses ( $169.254.x.x$ ) instead of valid leases from the centralized DHCP server located on a different subnet. Arrange the troubleshooting steps in the logical order the administrator should execute them to systematically diagnose and resolve the issue.

1Verify client physical link status and confirm the local IP configuration displays an APIPA address ( $169.254.x.x$ ).
2Inspect the local Layer 3 switch/router interface configuration to verify the IP helper address (DHCP relay) is correctly configured.
3Test IP reachability from the local gateway router interface to the centralized DHCP server IP address.
4Verify on the DHCP server that an active scope exists for the client subnet with available IP addresses in the pool.
5Execute `ipconfig /renew` on the affected client workstation to verify successful IP address lease acquisition.

Cevap

The correct sequence starts with verifying client link status and APIPA configuration, followed by checking the local gateway's IP helper address, testing routing connectivity to the DHCP server, verifying DHCP scope availability on the server, and finally renewing the IP lease on the client host.

Systematic network troubleshooting proceeds from the local client symptom to the local gateway configuration, across the routed network path to the centralized service, and finishes with verification on the client. Verifying local link/APIPA confirms host status. Checking the IP helper configuration ensures DHCP requests cross the VLAN boundary. Testing reachability verifies path routing. Checking server scope ensures address availability. Finally, running `ipconfig /renew` confirms the fix works.

Adım Adım Çözüm

Confirm client physical layer connectivity and host IP status.

Establishes that the physical NIC is link-up and confirms failure of local DHCP acquisition (indicated by APIPA

169.254.x.x

Always begin troubleshooting at the affected end host before inspecting network infrastructure.

Check the local router interface configuration for DHCP Relay / IP Helper settings.

Determines whether broadcast DHCP DISCOVER messages are being converted to unicast packets targeted at the remote DHCP server.

Cross-subnet DHCP request delivery relies on a properly configured IP helper address on the client's default gateway interface.

Test IP connectivity from the local gateway to the DHCP server IP.

Verifies Layer 3 routing and ACL permeability between the relay agent and the DHCP server.

If the relay agent cannot communicate with the DHCP server, forwarded DHCP packets will be dropped in transit.

Inspect DHCP server configuration and scope health for the target subnet.

Confirms the scope matching the gateway interface address (`giaddr`) is active, correctly configured, and has unallocated IP addresses.

Even with valid relaying, a missing scope or scope exhaustion will prevent the DHCP server from issuing a lease.

Issue a DHCP lease renewal request from the client host (`ipconfig /renew`).

The client successfully completes the DORA exchange and acquires a valid IPv4 configuration.

Final validation must always be confirmed on the end device that originally experienced the issue.

Anahtar Kavram

Standard methodology for cross-subnet DHCP troubleshooting involves validating host status, gateway relaying (IP helper), intermediate routing reachability, server scope availability, and client verification.

Soru

Cevap

Adım Adım Çözüm

Anahtar Kavram

Sık Yapılan Hatalar

Konular

Bu konudan daha fazla soru