A system administrator notices that the NTP service on a Linux server is not synchronizing time with external NTP servers. The administrator runs 'ntpq -p' and sees that all servers listed have a 'reach' value of 0. Which of the following is the most likely cause?
Trap 1: The system timezone is incorrectly set.
Timezone does not affect NTP synchronization.
Trap 2: The NTP service is configured to use the local clock.
Local clock would show reach only if configured as server, not client.
Trap 3: The NTP server is using a different NTP version.
Version mismatch typically causes 'no data' or 'refused' but not reach 0.
- A
The system timezone is incorrectly set.
Why wrong: Timezone does not affect NTP synchronization.
- B
The NTP service is configured to use the local clock.
Why wrong: Local clock would show reach only if configured as server, not client.
- C
A firewall is blocking UDP port 123.
Reach 0 indicates no response, common when firewall blocks NTP.
- D
The NTP server is using a different NTP version.
Why wrong: Version mismatch typically causes 'no data' or 'refused' but not reach 0.