A technician is troubleshooting a Windows 11 desktop that can successfully communicate with local printers on the 192.168.1.0/24 network, but cannot reach servers on remote corporate subnets (such as 192.168.2.50) or access the internet. Reviewing the static IPv4 configuration properties on the client reveals the following settings:
- IPv4 Address: 192.168.1.45
- Subnet Mask: 255.255.0.0
- Default Gateway: 192.168.1.1
- Preferred DNS: 192.168.1.2
Which of the following explains why traffic destined for remote subnets is failing?
- The misconfigured subnet mask causes the client to treat remote subnets as local network traffic, preventing it from forwarding packets to the default gateway.Cevap
- BThe preferred DNS server is located on the local subnet and is incapable of resolving IP routing tables for external subnets.
- CThe default gateway must be configured with an IP address belonging to a completely separate subnet from the client.
- DThe Windows desktop edition restricts multi-subnet network routing unless upgraded to a server operating system edition.
Cevap
The misconfigured subnet mask causes the host to view destination IPs in the 192.168.2.0/24 range as local rather than remote, leading the client to bypass the default gateway.
Subnet masks determine whether a destination IP address is local or remote. The expected subnet mask for a 192.168.1.0/24 network is 255.255.255.0. Because the subnet mask was entered as 255.255.0.0, the Windows client incorrectly calculates that 192.168.2.50 is on its local physical segment. Consequently, it attempts direct ARP requests for 192.168.2.50 rather than routing the traffic through the default gateway (192.168.1.1), causing communication to fail.
Adım Adım Çözüm
Anahtar Kavram
Subnet Mask Logic and Default Gateway Traversal