Following a scheduled power maintenance window at a branch office, multiple workstation users report that they cannot access internal file shares or connect to the internet. A technician runs `ipconfig /all` on an affected client machine and observes an IP address of , a subnet mask of , and a blank Default Gateway entry. Upon inspecting the main local host server, the technician observes that a newly installed centralized logging service failed to launch because UDP port 67 was already bound by another process that crashed during reboot. Which of the following best explains the root cause of the network connectivity failure on the workstations?
- The DHCP server service on the local host server failed to start, preventing client workstations from obtaining valid IP configuration leases and causing them to auto-assign APIPA addresses.Cevap
- BThe DNS server service failed to lease dynamic IP addresses and default gateway assignments to the local workstations.
- CThe web server role was configured to listen on UDP port 67 instead of TCP port 443, preventing secure communication with local hosts.
- DThe workstation adapter experienced a static IP collision and defaulted to a public, globally routable APIPA address.
Cevap
The DHCP server service on the local host server failed to start, preventing client workstations from obtaining valid IP configuration leases and causing them to auto-assign APIPA addresses.
The correct answer identifies that the failure of the DHCP server role (which operates on UDP port 67) prevents client workstations from receiving dynamic IP address leases, default gateways, and DNS settings. When clients fail to communicate with a DHCP server, modern operating systems automatically assign a link-local APIPA address (), allowing local subnet communication if configured properly, but preventing off-subnet network and internet routing.
Adım Adım Çözüm
Anahtar Kavram
DHCP Server Role and APIPA Fallback Behavior