A systems administrator is manually assigning a static IP configuration to a new server on a corporate network segment designated as . The server is configured with an IPv4 address of and a subnet mask of . The administrator enters into the default gateway field. During post-configuration testing, workstations on the local subnet can successfully access services on the server, but remote hosts on other corporate subnets cannot establish a connection to it. Which of the following is the most likely cause of this network issue?
- The default gateway is configured with an IP address outside the host's local subnet.Answer
- BThe server automatically defaulted to an APIPA IP address because the DHCP server was unreachable.
- CThe network switch connecting local hosts operates at Layer 2 and cannot forward frame headers across subnets.
- DThe DNS server failed to lease a valid default gateway address to the host during network startup.
Answer
The default gateway is configured with an IP address outside the host's local subnet.
For a host to communicate with remote networks, its default gateway must reside within the same local IP subnet as the host's IP address. With an IP of and a subnet mask (), valid local gateway addresses must fall between and . Because is on a different subnet, the server cannot ARP for the gateway, rendering off-subnet destination IPs unreachable while allowing local subnet traffic to function.
Step-by-Step Solution
Key Concept
Subnet Boundaries and Default Gateway Assignment
Estimated Time:1m 30s