A network technician is troubleshooting connectivity problems across several client workstations on a corporate network. Match each observed IP network configuration diagnostic output or symptom on the left with its corresponding underlying root cause on the right.
- The host automatically receives an IP address of with a subnet mask of and can only communicate with local neighbors.Automatic Private IP Addressing (APIPA) was invoked due to an unreachable DHCP server.
- The host can successfully ping neighboring computers on , but cannot access external resources on the internet.The default gateway IP address is misconfigured or missing.
- The workstation can ping remote servers using public IPv4 addresses like , but cannot load web pages using domain names.The primary DNS server IP address is invalid or non-responsive.
- The network interface displays an IPv6 address beginning with `fe80::` and fails to communicate beyond the local broadcast domain.Link-local IPv6 addresses are restricted to the local link and cannot be routed.
Answer
1. APIPA IP address () matches DHCP server unreachable.
2. Local connectivity only matches default gateway misconfiguration.
3. Ping IP succeeds but domain name fails matches DNS server misconfiguration.
4. IPv6 `fe80::` address matches non-routable link-local address behavior.
2. Local connectivity only matches default gateway misconfiguration.
3. Ping IP succeeds but domain name fails matches DNS server misconfiguration.
4. IPv6 `fe80::` address matches non-routable link-local address behavior.
Each diagnostic output maps to a distinct core IP addressing role: APIPA addresses () indicate DHCP failure; local-only communication points to a missing or invalid default gateway; successful IP pings with failed domain resolution indicate DNS issues; and `fe80::` prefixes represent non-routable IPv6 link-local addresses.
Step-by-Step Solution
Key Concept
IP Addressing Diagnostic Symptoms and Parameter Matching