A user reports that their laptop can connect to the corporate Wi-Fi but cannot access any network resources. The technician checks the IP configuration and sees an IP address of 192.168.1.105 with a subnet mask of 255.255.255.0 and a default gateway of 192.168.1.1. The technician pings the gateway successfully but cannot ping a server at 192.168.2.10. What is the most likely issue?
When a laptop attempts to communicate with a device on a different subnet, it sends the traffic to its default gateway. For the communication to succeed, the default gateway must possess a valid routing table entry that specifies how to reach the target 192.168.2.0 network. If this route is missing or incorrect, the gateway will not know where to forward the packets, resulting in them being dropped and the ping failing, even though the laptop can successfully reach the gateway itself.
Why this answer
The technician can ping the default gateway (192.168.1.1) but not the server at 192.168.2.10, indicating that Layer 3 connectivity exists within the local subnet but fails beyond it. This points to a routing issue on the default gateway, which likely lacks a route to the 192.168.2.0/24 network. Without that route, the gateway cannot forward packets destined for the server, even though the laptop's IP configuration is correct.
Exam trap
A common trap in CompTIA A+ is the distinction between local connectivity (pinging the gateway) and remote connectivity (pinging a different subnet) — candidates often assume the server is down or DNS is the problem, but the real issue is a missing route on the default gateway.
How to eliminate wrong answers
Option A is wrong because DNS misconfiguration would cause name resolution failures, not the inability to ping a specific IP address; the technician is pinging by IP, not hostname, so DNS is irrelevant. Option B is wrong because while the server could be offline, the most likely cause given the successful gateway ping and the fact that the server is on a different subnet is a routing problem; the question asks for the 'most likely' issue, and a missing route is more probable than a server failure in this context. Option D is wrong because the subnet mask 255.255.255.0 is correct for the 192.168.1.0/24 network, and the laptop can communicate with the gateway, proving the mask is not the issue.