A network technician is diagnosing host network configuration issues on a corporate network. Match each observed host diagnostic symptom on the left with its most likely underlying network cause on the right.
- Workstation network adapter shows an IPv4 address of 169.254.112.45 with a 255.255.0.0 subnet mask.DHCP server is unreachable, causing automatic private IP address self-assignment.
- Workstation can ping local IP addresses on its subnet but fails to resolve website domain names.DNS server IP address is missing or incorrectly configured in host network settings.
- Workstation can communicate with other hosts on the 10.1.10.0/24 subnet but cannot send traffic to remote subnets.Default gateway IP address is missing or incorrectly configured on the network profile.
- Workstation interface automatically assigns itself an address with the fe80:: prefix.IPv6 Link-Local unicast address auto-configuration for single-segment communications.
Answer
Each host symptom correctly pairs with its configuration cause: an IP in 169.254.x.x matches APIPA from DHCP unreachability; hostname resolution failure with working local IP pings matches misconfigured DNS; inability to route past the local subnet matches misconfigured default gateway; and fe80:: prefix matches IPv6 Link-Local auto-configuration.
Each diagnostic state aligns with its core networking component: 169.254.x.x addresses indicate APIPA due to DHCP failure; domain resolution issues reflect missing DNS settings; inability to route past the local subnet indicates default gateway issues; and fe80:: addresses represent IPv6 link-local autoconfiguration.
Step-by-Step Solution
Key Concept
IP Addressing, Host Configuration Parameters, and Network Diagnostics