A network technician is troubleshooting a newly connected client workstation that cannot access local network resources or the internet. Executing `ipconfig /all` on the workstation yields the following output:
Ethernet adapter Ethernet0:
Connection-specific DNS Suffix . :
Link-local IPv6 Address . . . . . : fe80::d4a2:810f:3c21:7a9a%12
IPv4 Address. . . . . . . . . . . : 169.254.108.42
Subnet Mask . . . . . . . . . . . : 255.255.0.0
Default Gateway . . . . . . . . . :
Which of the following is the most likely cause of this workstation's IP configuration?
- The host was unable to obtain an IP lease from a DHCP server and self-assigned an Automatic Private IP Addressing (APIPA) address.Answer
- BThe default gateway parameter was left blank in the static IPv4 configuration properties, forcing the OS to default to a link-local range.
- CThe workstation's static IP address and default gateway address reside on mismatched IPv4 subnets.
- DThe central DHCP server scope ran out of usable host addresses because the subnet mask was set to calculate usable hosts without subtracting network and broadcast identifiers.
Answer
The host was unable to obtain an IP lease from a DHCP server and self-assigned an Automatic Private IP Addressing (APIPA) address.
An IPv4 address beginning with 169.254.x.x indicates Automatic Private IP Addressing (APIPA). Operating systems assign an APIPA address when configured as a DHCP client but fail to receive a response (DHCPACK) from a reachable DHCP server.
Step-by-Step Solution
Key Concept
Automatic Private IP Addressing (APIPA) Diagnosis
Estimated Time:1m 15s