EndRun Meridian II, Руководство пользователя

Страница: 103 / 240

M e r i d i a n I I U s e r M a n u a l 82
C H A P T E R S E V E N
83 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 )
http://support.ntp.org/bin/view/Main/ExternalTimeRelatedLinks
Configure NTP
Directory path names are not given in the instructions below because there are multiple ways to
install
ntpd
and multiple versions of Windows.
After installing
ntpd
, you must edit the
ntp.conf
file by adding a line similar to this:
server 192.168.1.120
This line tells
ntpd.exe
to use the NTP server at address 192.168.1.120 in addition to any other
servers which might also be configured in the ntp.conf file.
Restart
ntpd.exe
to have it begin using the Meridian II server. By default, the NTP installation pro-
gram 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 restart it.
Use the NTP utility
ntpq.exe
to check that
ntpd.exe
is able to communicate with Meridian II.
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 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 have other peers configured, verify that the offset information for the Meridian II
server peer and your other peers is in agreement to within a few milliseconds, assuming that the other
peers are synchronized to that level of accuracy.
It may also be useful to start the NTP daemon in ‘debug’ mode (
ntpd -d
) to confirm successful con-
figuration. Refer to the NTP documentation for detailed usage of these debug utilities.
Windows: MD5 Authenticated NTP Client Setup
MD5 authenticated setup is relatively simple, if:
• You have been able to successfully communicate with Meridian II on your network.
• Your Meridian II has been configured to perform authentication either by factory default, or by
running the
ntpconfig
shell script. The example Meridian II authentication configuration shown in