2. An organization recently connected a new computer to the LAN. The user is unable to ping the default gateway. The technician examines the configuration and sees a self-assigned IP address. Which of the following is the most likely cause?
Answer: A
The DHCP server is not available.
A self-assigned IP address indicates that the computer could not obtain an IP address from a DHCP server, which is typically the reason for failing to ping the default gateway.
A) The DHCP server is not available.
This option is correct because when a computer fails to connect to a DHCP server, it cannot obtain a valid IP address and resorts to a self-assigned address (usually in the range of 169.254.x.x). This self-assigned address prevents communication with other network devices, including the default gateway.
B) An RFC1918 address is being used.
This option is incorrect as RFC1918 addresses are private IP addresses that are valid within local networks. If the computer were using an RFC1918 address, it would still be able to ping the gateway unless there is another configuration issue.
C) The TCP/IP stack is disabled.
This option is incorrect because if the TCP/IP stack were disabled, the computer would not be able to communicate over the network at all, resulting in an inability to ping any addresses, not just the default gateway. The self-assigned IP address indicates that the TCP/IP stack is active but misconfigured.
D) A static IP is assigned.
This option is also incorrect. If a static IP were assigned correctly within the same subnet as the default gateway, the computer should be able to ping the gateway. A self-assigned IP address suggests that no valid IP configuration was established through DHCP.
Conclusion
The correct answer is "The DHCP server is not available" because the inability to obtain an IP address from the DHCP server leads to a self-assigned IP address. Other options do not align with the symptoms described, as they would not explain the failure to ping the default gateway in the context provided.