Question

Difficulty: HardWindows Client Networking Configuration

A desktop technician is troubleshooting a newly assigned Windows 11 Pro workstation in a branch office. The computer can ping other host devices on the local subnet (192.168.4.0/24192.168.4.0/24), but users cannot reach internal company servers on other subnets or access external internet resources. A review of the network adapter's IPv4 configuration details shows:

- IP Address: 192.168.4.45192.168.4.45
- Subnet Mask: 255.255.255.0255.255.255.0
- Default Gateway: 192.168.4.45192.168.4.45
- Preferred DNS Server: 192.168.4.1192.168.4.1

Which of the following best identifies the configuration error and the required resolution?

  1. The default gateway is configured with the workstation's own IP address; it must be changed to the IP address of the local router interface.Answer
  2. B
    The subnet mask is restrictive; it must be expanded to 255.255.0.0 to allow routing between remote networks.
  3. C
    The preferred DNS server IP address is invalid for off-subnet routing; it must be reconfigured to use the loopback address 127.0.0.1.
  4. D
    The operating system edition limits network routing; the client must be joined to an Active Directory domain via Network and Sharing Center to unlock default gateway routing.

Answer

The default gateway is configured with the workstation's own IP address; it must be changed to the IP address of the local router interface.
The default gateway is the IP address of the local router that enables host devices on a subnet to communicate with hosts on external networks or remote subnets. Because the gateway was misconfigured to match the workstation's own static IP address (192.168.4.45192.168.4.45), any traffic sent to off-subnet destinations fails to egress the local network segment. Changing the default gateway to the router's interface IP address resolves remote network connectivity.

Step-by-Step Solution

1
Analyze local subnet communication capabilities.
The workstation can reach local devices on 192.168.4.0/24192.168.4.0/24, confirming local physical layer, data link layer, and local IP addressing are functioning.
Traffic destined within the same subnet does not require a router or default gateway.
2
Evaluate the configuration required for off-subnet routing.
Traversing beyond the local subnet (192.168.4.0/24192.168.4.0/24) requires packets to be directed to the next-hop router interface, defined in IPv4 properties as the Default Gateway.
Without a valid default gateway address pointing to the router, packets intended for remote subnets cannot leave the local segment.
3
Identify the incorrect parameter in the TCP/IP settings.
The Default Gateway field erroneously matches the client host IP address (192.168.4.45192.168.4.45).
This misconfiguration causes the OS to attempt sending remote-bound packets to itself rather than forwarding them to the router interface (such as 192.168.4.1192.168.4.1).

Key Concept

Windows Client IPv4 Gateway Configuration and Off-Subnet Routing
Estimated Time:1m 30s
Rate this question