220-802 · Question #61
A user, Ann, reports that her computer is able to connect to devices on her local network but not on the remote office network. Ann's computer shows the following ipconfig information: IP address…
The correct answer is D. Gateway is set incorrectly. Ann's IP address (192.168.10.45) with a /24 subnet mask places her on the 192.168.10.0 network. For the default gateway to be reachable, it must reside on that same subnet. Her gateway is configured as 192.168.11.1, which belongs to the 192.168.11.0 network - a completely…
Question
A user, Ann, reports that her computer is able to connect to devices on her local network but not on the remote office network. Ann's computer shows the following ipconfig information:
IP address: 192.168.10.45 Subnetmask: 255.255.255.0 Gateway: 192.168.11.1 DNS server 1: 192.168.10.2 DNS server 2: 8.8.8.8 Which of the following is the cause of the problem?
Options
- ADNS server 2 is set incorrectly.
- BDNS server 1 is set incorrectly.
- CIP address is set incorrectly.
- DGateway is set incorrectly.
How the community answered
(53 responses)- A4% (2)
- B6% (3)
- C13% (7)
- D77% (41)
Explanation
Ann's IP address (192.168.10.45) with a /24 subnet mask places her on the 192.168.10.0 network. For the default gateway to be reachable, it must reside on that same subnet. Her gateway is configured as 192.168.11.1, which belongs to the 192.168.11.0 network - a completely different subnet. Because the gateway is logically unreachable, her workstation cannot forward traffic destined for remote networks, explaining why local communication works (no gateway needed) but remote access fails. The IP address and both DNS server entries are not the cause of this specific routing failure.
Topics
Community Discussion
No community discussion yet for this question.