Soru

Zorluk: OrtaIP Addressing and Network Configuration

A network technician is diagnosing workstation configuration issues following a network migration. Match each observed host symptom to its most likely underlying root cause.

  • Workstation self-assigns an IP address in the range 169.254.1.1169.254.1.1 to 169.254.254.254169.254.254.254 and can only communicate with other hosts on the same physical link.Unreachable DHCP server or failed lease negotiation, causing the client to fall back to Automatic Private IP Addressing (APIPA).
  • Workstation can successfully reach internal web portals using direct IP addresses like 192.168.10.50192.168.10.50, but fails to load web pages using domain names such as corporate.local.Unreachable or incorrectly configured DNS server addresses.
  • Workstation communicates normally with local hosts on the 10.1.20.0/2410.1.20.0/24 subnet, but cannot send packets to servers located on the 10.1.30.0/2410.1.30.0/24 subnet.Misconfigured or missing Default Gateway address on the host network interface.
  • Workstation displays an IP address collision alert shortly after joining the network using dynamic configuration settings.Overlapping static IP assignment within the DHCP server's active scope range.

Cevap

Matching pairs:
- Self-assigned 169.254.x.x169.254.x.x address matches Unreachable DHCP server causing APIPA fallback.
- Access by direct IP success but hostname failure matches Unreachable or incorrectly configured DNS server.
- Local subnet communication success but remote subnet failure matches Misconfigured or missing Default Gateway.
- IP address collision alert matches Overlapping static IP assignment within the active DHCP scope range.
Each diagnostic symptom directly correlates with a specific TCP/IP configuration component: APIPA (169.254.0.0/16169.254.0.0/16) indicates a missing DHCP lease response; inability to resolve hostnames while IP routing works points to DNS misconfiguration; loss of off-subnet routing while retaining intra-subnet connectivity indicates a default gateway misconfiguration; and dynamic IP address conflicts stem from static IPs existing within active DHCP scopes.

Adım Adım Çözüm

1
Analyze symptom 1 (169.254.x.x169.254.x.x address)
Identified APIPA address range generated when DHCP server requests fail.
Windows and other operating systems automatically assign link-local APIPA addresses when DHCP client lease acquisition times out.
2
Analyze symptom 2 (IP connectivity works, domain resolution fails)
Isolated issue to name-to-IP resolution service.
DNS is specifically responsible for mapping domain hostnames to IP addresses; IP reachability confirms underlying layer 3 routing is functional.
3
Analyze symptom 3 (Local subnet ping succeeds, cross-subnet ping fails)
Identified default gateway routing issue.
Host computers use the subnet mask to determine if a destination is local; off-subnet traffic must be forwarded to the default gateway router interface.
4
Analyze symptom 4 (IP collision alert on dynamic host)
Identified duplicate IP conflict cause.
If a static IP is configured on a host within a DHCP scope without an exclusion, the DHCP server may assign that same IP address to a dynamic client.

Anahtar Kavram

IP Network Configuration Parameters and Diagnostic Symptoms
Bu soruyu puanla