EndRun Tempus LX GPS, User Manual

Page: 40 / 116

T e m p u s L X G P S U s e r M a n u a l 28
C H A P T E R F O U R
29 T e m p u s L X G P S U s e r M a n u a l
S E T T I N G U P N T P C L I E N T S O N W I N D O W S N T 4 . 0 / 2 0 0 0 / X P
Re-start
ntpd.exe
to have it begin using the Tempus LX server with MD5 authentication. By de-
fault, the NTP installation program installs
ntpd.exe
as a service called Network Time Protocol, and
starts it. You must use the Services utility in Control Panel to stop the Network Time Protocol service
and then re-start it.
Use the NTP utility
ntpq.exe
to check that
ntpd.exe
is able to communicate with the Tempus LX.
By default it is installed in the \
Program Files\Network Time Protocol
sub-directory of your Windows
NT/2000/XP partition. From a console window, after issuing the command
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 Tempus LX
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.)
You can verify that authentication is being used by issuing the command
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 Tempus LX 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 \winnt\system32\drivers\etc\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 \winnt\
system32\drivers\etc\ntp.conf
file that causes the needed key to not be included in the “trustedkey”
list.
Broadcast/Multicast NTP
Client Setup
Broadcast/multicast client setup is relatively simple, if:
• You have been able to successfully communicate with the Tempus LX on your network.
• Your Tempus LX has been configured to perform broadcasts or multicasts via the front-panel key-
pad or by running the
ntpconfig
shell script. (This is not the factory default configuration, so be
sure to run
ntpconfig
.) If you are going to use MD5 authentication, your Tempus LX must have
been configured to operate with authentication in the broadcast/multicast mode, and you must know
which of the trusted keys it is using for broadcast/multicast operation. The example Tempus LX
configuration shown in Chapter 2 - Configuring the Network Time Protocol will be assumed in the
example configuration commands shown here.