A network technician is troubleshooting connectivity issues for several newly provisioned workstations on the finance VLAN (10.15.30.0/24). While the workstations can communicate with each other on the local switch, none of them can access corporate servers on external subnets or reach the internet. An inspection of `ipconfig /all` on one of the affected clients yields the following output:
IPv4 Address. . . . . . . . . . . : 10.15.30.45
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 10.15.40.1
DHCP Server . . . . . . . . . . . : 10.15.10.10
Which of the following is the most likely cause of the routing failure?
- The DHCP scope option for the default gateway specifies an IP address located outside the local subnet.Cevap
- BThe client host failed to acquire an IP lease from the DHCP server and generated an APIPA address.
- CThe local switch interface is missing an IP helper address required to forward DHCP request broadcasts.
- DThe DHCP address pool for the 10.15.30.0/24 subnet has exhausted all available usable host addresses.
Cevap
The DHCP scope option for the default gateway specifies an IP address located outside the local subnet.
For a workstation to communicate with remote networks, its configured default gateway must share the same network identifier as defined by the host IP address and subnet mask. In this scenario, the host IP (10.15.30.45/24) belongs to the 10.15.30.0/24 subnet, but the gateway (10.15.40.1) resides on 10.15.40.0/24. This subnet mismatch prevents ARP resolution for the default gateway, resulting in failed off-subnet routing while allowing local switch traffic.
Adım Adım Çözüm
Anahtar Kavram
Default Gateway Subnet Alignment in DHCP Scope Configurations