Users on a newly provisioned branch office subnet () report an inability to reach intranet services or external websites. Running `ipconfig /all` on an affected client workstation yields the following output:
IPv4 Address. . . . . . . . . . . : 169.254.14.88
Subnet Mask . . . . . . . . . . . : 255.255.0.0
Default Gateway . . . . . . . . . :
DHCP Server . . . . . . . . . . . :
The central DHCP server is located on the headquarters data center VLAN (). Network operations confirms that the DHCP scope for is online and contains 150 available IP addresses. Which of the following is the most likely root cause of this issue?
- The router interface serving as the default gateway for lacks a configured DHCP relay agent (IP helper address).Answer
- BThe client workstations were manually misconfigured with static APIPA addresses that bypass the default gateway.
- CThe DHCP scope for has exhausted all usable host IP addresses due to incorrect network address calculations.
- DThe workstations successfully leased an IP address but were provisioned with a Default Gateway residing on a different subnet.
Answer
The router interface acting as the default gateway for the branch subnet is missing a DHCP relay agent (IP helper address) to forward broadcast DHCP requests across subnets.
DHCP requests begin as Layer 2 broadcast packets. Routers drop Layer 2 broadcasts by default. When the DHCP server resides on a different network segment from the clients, the router interface facing the client subnet must be configured with a DHCP relay agent (such as `ip helper-address` in Cisco IOS) to convert broadcast requests into unicast traffic directed to the remote DHCP server. Without this, clients fallback to APIPA ().
Step-by-Step Solution
Key Concept
DHCP Relay / IP Helper Agent Configuration