Examkin

Question

Difficulty: HardWindows Client Networking Configuration

A help desk technician is troubleshooting a Windows 11 client workstation in a enterprise environment. The workstation is assigned a static IPv4 address of 172.16.45.110 with a subnet mask of 255.255.255.0. Users report that while the machine can communicate with other systems on the local 172.16.45.0/24 subnet, it cannot access intranet resources on adjacent subnets nor browse external websites by domain name. Upon reviewing the TCP/IP v4 properties in ncpa.cpl, the technician notes the current configuration. Which TWO setting errors are directly causing the reported connectivity failures? (Select TWO.)

  1. An incorrect or missing Default Gateway address, preventing traffic from routing off the local subnet.Answer
  2. An invalid Preferred DNS Server address, preventing name resolution for external and internal domain names.Answer
  3. C
    A subnet mask of 255.255.255.0, which improperly isolates class B private IP addresses.
  4. D
    Failure to execute the netsh interface ipv4 reset command after applying static configuration properties.

Answer

The connectivity failures are caused by an incorrect or missing Default Gateway address and an invalid Preferred DNS Server address.
Ability to communicate locally paired with inability to reach external subnets indicates a missing or misconfigured Default Gateway. The inability to resolve domain names to IP addresses points directly to an invalid Preferred DNS Server configuration.

Step-by-Step Solution

1
Analyze local vs. remote network traffic failure symptoms.
The workstation can reach local subnet hosts (172.16.45.0/24) but cannot reach remote subnets, indicating a routing failure beyond the local boundary.
Traffic destined outside the local subnet must be sent to the local router IP address configured as the Default Gateway.
2
Analyze domain name resolution failure symptoms.
The workstation cannot resolve domain names to IP addresses, pointing to a name resolution misconfiguration.
Hostnames must be translated into IP addresses by a reachable Domain Name System (DNS) server.
3
Evaluate TCP/IP client configuration parameters.
Confirming an invalid or missing Default Gateway accounts for the inter-subnet failure, and an invalid Preferred DNS Server accounts for the hostname resolution failure.
Both settings are configured independently within the IPv4 properties window of the network adapter.

Key Concept

Windows TCP/IP Client Configuration & Troubleshooting
Rate this question

Topics

Windows Client Networking Configuration

More questions from this topic