EndRun Meridian II, User Manual

Page: 107 / 240

M e r i d i a n I I U s e r M a n u a l 86
C H A P T E R S E V E N
87 M e r i d i a n I I U s e r M a n u a l
N E T W O R K T I M E P R O T O C O L ( N T P )
ntpq
you will see the
ntpq.exe
command prompt:
ntpq>
Use the command
peers
to display the NTP peers which your computer is using. One of them should be the Meridian II
server which you have just configured. You should verify that it is being ‘reached’. (You may have
to continue issuing the peers command for a minute or two before you will see the ‘reach’ count
increment.)
If you are using authentication, you can verify that authentication is being used by issuing the com-
mand
associations
to display the characteristics of the client server associations. In the “auth” column of the display,
you should see “OK” for the row corresponding to the Meridian II server. If you see “bad”, you
should wait a few minutes to be sure that there is a problem since “bad” is the initial state of this
setting. If the “bad” indication persists then you must check your configuration for errors. Typically
this is due to a typing error in creating the ntp.keys file on the client that causes a mismatch between
the keys being used by the server and client. (If you transfer the file by
ftp
or
scp
, this shouldn’t be
a problem.) It is also possible to have a typing error in the ntp.conf file that causes the needed key to
not be included in the “trustedkey” list.