A network administrator deploys a new workstation on VLAN 35 (). Upon booting up, the workstation cannot access internal servers or the internet. Executing `ipconfig /all` on the workstation yields the following output:
IPv4 Address. . . . . . . . . . . : 169.254.14.88
Subnet Mask . . . . . . . . . . . : 255.255.0.0
Default Gateway . . . . . . . . . :
DHCP Enabled. . . . . . . . . . . : Yes
The central DHCP server is located on VLAN 10 () and actively provides IP address leases to clients on VLAN 10. Which of the following represents the most likely cause of this issue?
- The Layer 3 interface serving VLAN 35 lacks an IP helper address pointing to the DHCP server.Answer
- BThe workstation has been manually assigned an invalid static default gateway address.
- CThe central DHCP server's scope pool for VLAN 10 has exhausted all available host IP addresses.
- DThe workstation's default gateway resides on a different IP subnet than the host.
Answer
The Layer 3 interface serving VLAN 35 lacks an IP helper address pointing to the DHCP server.
The client address indicates that the workstation failed to receive a response to its DHCP DISCOVER broadcast and fell back to Automatic Private IP Addressing (APIPA). Because the DHCP server is on a different subnet (VLAN 10), the router interface serving VLAN 35 must be configured with a DHCP Relay Agent (`ip helper-address`) to forward client broadcast requests to the unicast IP address of the DHCP server.
Step-by-Step Solution
Key Concept
DHCP Relay Agent and APIPA Diagnosis
Estimated Time:1m 15s