A network administrator is investigating connectivity complaints from users on a newly deployed subnet (). An affected workstation displays an IP address of and a subnet mask of . The organization's central DHCP server is located on a separate administrative segment (). Which of the following issues could cause the client to receive this address? (Select TWO.)
- The local router interface serving as the default gateway for is missing a DHCP relay agent (ip helper-address) configuration.Cevap
- The DHCP scope designated for the subnet on the central server has exhausted all available IP addresses.Cevap
- CThe host network interface card and switch port are operating with a speed and duplex mismatch.
- DThe host system rejected the lease assignment because its static default gateway belonged to a different IP subnet.
Cevap
The client receiving an Automatic Private IP Addressing (APIPA) address indicates a failure to communicate with or obtain an IP lease from a DHCP server. The two valid root causes are: 1) missing DHCP relay (IP helper) configuration on the local default gateway router interface, which prevents broadcast discovery frames from reaching the remote DHCP server, and 2) scope exhaustion on the DHCP server for that specific subnetwork pool.
An APIPA address (169.254.0.1 through 169.254.255.254) indicates that the client attempted to obtain an IP lease via DHCP but received no response. When a DHCP server resides on a different IP subnet than the client, broadcast DHCPDISCOVER packets require a Layer 3 relay agent (such as ip helper-address on network routers) to unicast the request to the central DHCP server. Without this relay, requests are dropped by the default gateway. Alternatively, if the relay is functioning but the DHCP server has run out of available addresses in its scope pool for that subnet, no lease can be granted, resulting in APIPA self-assignment.
Adım Adım Çözüm
Anahtar Kavram
APIPA Diagnosis and DHCP Relay Configuration