ntpdate -d Server dropped Strata too high

Solution 1:

NTP increases the stratum for each level in the hierarchy - a NTP server pulling time from a "stratum 1" server would advertise itself as "stratum 2" to its clients.

A stratum value of "16" is reserved for unsynchronized servers meaning that your internal NTP server at 192.168.92.82 thinks not to have a reliable timesource (i.e. not synchronizing to a higher-level stratum server).

You would need to do some debugging there - if it is a Linux server using ntpd, look at the output of ntpq peers for clues for possible reasons

Solution 2:

I have found that attempting to change the stratum of a server in the client side ntp.conf with a

fudge <server_ip> stratum <number_less_than_16>

does not work.

However, if you can access the ntp.conf on the server (the machine running ntpd) and add the following lines

server 127.127.1.0
fudge 127.127.1.0 stratum 8

it is able to fudge itself (127.127.1.0 is the local ntpd server address, 8 is a number less than 16) (remember to restart ntpd).

You can then successfully run ntpdate on the client (ntpdate <server_ip>).