Getting NTP to work on NT Server v4

G

Guest

Guest
Archived from groups: microsoft.public.windowsnt.misc (More info?)

Hi All,

I'm trying (without much success!!) to get all of our servers and
workstations synchronised to a single time.

NTP seems to be a way of achieving this.

From what I've read it appears that I need to have ...
1. A single m/c (I'll call it "Timemaster") within our domain that
periodically 'synchs' with an external accurate time source. Currently we are
trying to use the PDC as the 'timemaster'
2. All other m/c's within the domain synch with "Timemaster" on a periodic
basis.

I have installed the Server res kt (incl supplement 4) on the 'Timemaster'
machine and copied timeserv.ini into the 'WinNT' directory and Timeserv.exe &
dll into the 'WinNT\System32' directory. A copy of our current Timeserv.ini
file is included at the end of this mail.

On the 'Timemaster' machine I've ...

1. Configured the time service (via control panel) to start automatically on
NT load using a dedicated account having domain administrative privilege and
able to 'logon as a service'. This account is also permitted to reach the
web via MS Proxy (Webproxy) to our ADSL router.

2. Checked the time service and it says it is running - however when I look
at the event log (I've turned on logging) it repeatedly records the following
Event ...
Description : "Modem timeout - might be BUSY "
Event Id : 17
Source : Timeserv
Type : Warning
User : N/A
Also the current system time does not appear to be corrected as expected -
it is currently about 45 minutes fast.

3. I've tried stopping and restarting the time service and performing 'cold
boot' - always get the same result (as above).

I imagine the problem is in the Timeserv.ini settings but i have double
checked the entries and do not see anything that is obviously wrong - however
I have only limited documetation about such settings. I do not see why it is
trying to access a modem (the m/c in question does not have nor has it ever
had a modem attached to it. I've looked at the timeserv.ini settings re modem
based access and I think I've turned everything off - I am trying to get the
service to use NTP

However I'm unsure of the following settings...
Type=NTP (should this be set to 'primary' ??)
PrimarySource=\\TIMEMASTER (should this be set to the name of the
machine??)
Period=0 (not sure what to set this to)
SecondaryDomain= (not sure what to set this to)
Hour=6 (not sure what to set this to)
TAsync=no
TAsync (is this relevant ??)


And finally even when I do get synch between 'Timemaster' and the external
time source, how do I then distribute it o the other m/cs within the domain.


REM This is TimeServ.ini, to be placed in %SystemRoot%

REM Remarks and blank lines are allowed. Following is the section name:

[TimeServ]

REM remove the ; from in front of one of the Types, below.
REM NISTACTS means dial NIST ACTS using the modem to set the time.
REM PRIMARY means a networked machine intended in a second "tier"
REM SECONDARY means a networked machine lower in the tier (a "client")
REM USNO means dial Naval Observatory using the modem to set the time.
REM INTERNET means use TCP/IP to access NIST
REM NTP means use Simple Network Time Protocol over IP
REM NRC means dial the National Research Council using the modem to set time.
REM BBC means dial the BBC using the modem to set the time.
REM COMPUTIME means dial Telecom Australia's service to set the time.
REM EUROPE means dial a European service (Sweden/Austria/Germany/Italy, etc).
REM MSL means dial the New Zealand Measurement Standards Laboratory
REM GC1000 means use the Heath GC-1000 Most Accurate Clock
REM GC1001 means use the Heath GC-1001 Most Accurate Clock II
REM SPECTRACOM means use the Spectracom NETCLOCK/2
REM HP means use the 58503A Time and Frequency Reference Receiver
REM TIMELINK means use the TrueTime TL-3 WWV Timing Receiver
REM TRUETIME means use the serial output from TrueTime product other than TL-3
REM ARBITER means use the serial output from Arbiter Systems
REM TRIMBLE means use a Trimble GPS with TSIP over RS-232
REM ROCKWELL means use a Rockwell GPS with messages over RS-232
REM ZODIAC means use a newer Rockwell GPS with messages over RS-232
REM MOTOROLA means use a Motorola 8-channel GPS with binary format over RS-232
REM or BC620AT, BC630AT, PC03XT, PCSG2, PCLTC, AMDAT, MOBATIME, RADIOCODE

;Type=SECONDARY
;Type=PRIMARY
;Type=NISTACTS
;Type=USNO
;Type=INTERNET
Type=NTP
;Type=NRC
;Type=BBC
;Type=COMPUTIME
;Type=EUROPE
;Type=MSL
;Type=GC1000
;Type=GC1001
;Type=Spectracom
;Type=HP
;Type=TimeLink
;Type=TrueTime
;Type=Arbiter
;Type=Trimble
;Type=Rockwell
;Type=Zodiac
;Type=Motorola
;Type=

REM The PrimarySource list below are the servers which are known good
REM Each server name should start with \\, separated by a semicolon

;PrimarySource=\\TIMEMASTER

REM Period 0 below means to use the default delay between each time set
REM Default is daily for modem or every 8-12 hours for network
REM Period can also be set to a number which means that many times daily

Period=0

REM Port is the name of the serial port used for modem, GPS, or clock

;Port=\\.\COM1
;Port=\\.\COM2
;Port=\\.\COM3

REM ModemCommand below is the string used to setup and dial your modem.
REM The &Q0 is desirable for high speed Hayes modems
REM The &D2 is desirable for quickest hangup
REM The plain ATDT is intended for older Hayes Smartmodem 1200 or 300
REM A B15 may need to be added to force the BBC V.21 communication standard
REM For USNO, S2 must be 43, S12 must be 50 or less, and must not be X0
REM The entry with \N1 is intended for Megahertz XJ2288
REM The entry with &A0&K0&M0 is intended for USR Sportster
REM The entry with B5 03, is intended for PDI @ MS from 12-button phone
REM The entry with B26 03, is intended for PDI @ MS from x-button phone

;ModemCommand=AT&D2&Q0DT
;ModemCommand=AT&D2DT
;ModemCommand=ATDT
;ModemCommand=AT&D2\N1DT
;ModemCommand=AT&D2&A0&K0&M0DT
;ModemCommand=AT&D2DTB5 03,
;ModemCommand=AT&D2DTB26 03,

REM Prefix is the number dialed prior to the phone number, such as for a PBX

;Prefix=9,
;Prefix=

REM PhoneNumber is the number of NIST in Colorado (+1 303 494 4774)
REM or USNO in Washington DC (+1 202 762 1594)
REM or NRC in Ottawa (+1 613 745 3900)
REM or BBC in the UK (0891 516880 a special number inside UK only)
REM or Computime in Australia (+61 03 9600 1641, or 02 9267 4648, or
REM 07 3221 7033, 08 8941 3423, 09 221 5457, 08 8410 0143, 03 6224 1905)
REM or Sweden (0900 100 2000 a special number inside Sweden only)
REM or Sweden (0729 31 00 20 a special number inside Sweden only?)
REM or Austria (+43 316 472366)
REM or Germany (+49 531 512038)
REM or Italy (166 11 46 15 a special number inside Italy only)
REM or NPL in the UK (0891 516 333 a special number inside UK only)
REM or Belgium (+32 2 3730320)
REM or Netherlands (+31 15 2617181)
REM or Switzerland (+41 313 233 225)
REM or New Zealand (0900 45222 a special number inside New Zealand only)

;PhoneNumber=1 303 494 4774
;PhoneNumber=1 494 4774
;PhoneNumber=494 4774
;PhoneNumber=1 202 762 1594
;PhoneNumber=1 762 1594
;PhoneNumber=762 1594
;PhoneNumber=1 613 745 3900
;PhoneNumber=0891 516880
;PhoneNumber=03 9 600 1641
;PhoneNumber=316 472366

REM NTPServer is the name or numeric address of an NTP server
REM No default is given, since you should contact a timekeeper
REM (If you don't know what this is, you shouldn't try NTP)
REM (The names BroadcastClient and MulticastClient are reserved)

NTPServer=swisstime.ethz.ch

REM timesource is a flag used by LanmanServer, placed in the registry
REM It should typically be set to yes when Type is Primary

;timesource=no
timesource=yes

REM Log is a flag used to indicate that you want an entry in the
REM Application log of the Event Viewer upon every sucessful time set

;Log=no
Log=yes

REM (The following are rarely changed)

REM SecondaryDomain defaults to searching for a timesource in your current
REM domain. Alternatively, it can be set to a domain/workgroup name.
SecondaryDomain=

REM Speed 300 is most accurate for NIST, but 1200 is also allowed
REM and 2400 seems necessary for the PDI pool at MS
REM otherwise speed is forced automatically 300 for NRC/BBC
REM and 1200 for USNO or COMPUTIME (or EUROPE).
REM (For TrueTime, Speed must be set to 9600 or whatever is appropriate)
REM (For many others such as Spectracom, Speed is automatic 9600, etc.)
;Speed=300
;Speed=1200
;Speed=2400
;Speed=9600
;Speed=14400

REM RandomPrimary yes means to choose a random entry in the PrimarySource
REM list, rather than starting at the top. As long as the chosen server
REM remains accessible, it will continue to be used.
RandomPrimary=yes

REM Hour 6 means wait until a little after 6am for the second modem call
REM The purpose is to call daily (or twice/day) at low long distance rates
REM Hour 24 disables such special handling
Hour=6

REM TAsync no means to use TimeAdjustment API to disable CMOS sync
TAsync=no

Many thanks in advance for whatever help you can provide

cheers

Rod.
 

Bruce

Distinguished
Apr 2, 2004
391
0
18,780
Archived from groups: microsoft.public.windowsnt.misc (More info?)

Informate-Rod wrote:
> Hi All,
>
> I'm trying (without much success!!) to get all of our servers and
> workstations synchronised to a single time.
>
> NTP seems to be a way of achieving this.
>
> From what I've read it appears that I need to have ...
> 1. A single m/c (I'll call it "Timemaster") within our domain that
> periodically 'synchs' with an external accurate time source. Currently we are
> trying to use the PDC as the 'timemaster'
> 2. All other m/c's within the domain synch with "Timemaster" on a periodic
> basis.
>
> Many thanks in advance for whatever help you can provide
>

Windows NT includes a command to set one computer's clock from
the clock of another computer. This is the "NET TIME" command. n.b.
the description given by "NET TIME /?" ommits the "/YES" option that
prevents prompting for confirmation. I don't think this command attempts
to allow for network delays so only achieves accuracy of tens of
milliseconds over a LAN and hundreds of milliseconds over a WAN.

NTP is designed to allow a computer to be set accurately (within
milliseconds) to the current time. It does attempt to allow for network
delays.

If you are just worried about computers having obviously wrong times,
then you can forget about timeserver and manually set one computer's
clock and have the other computers use "NET TIME".

You could have the other computers run "NET TIME" command from the task
scheduler ("AT" command) or include it in users' login script.
 
G

Guest

Guest
Archived from groups: microsoft.public.windowsnt.misc (More info?)

A simpler approach might be to use a freeware NTP client:

http://www.boulder.nist.gov/timefreq/service/its.htm
NIST Internet Time Service

The current version will run as a service under NT4, Windows 2000, and
Windows XP. This client will run on Windows 95 and all later versions, so
you could use it on all your Domain machines.

Hal
--
Hal Hostetler, CPBE -- hhh@kvoa.com
Senior Engineer/MIS -- MS MVP-S/U -- WA7BGX
http://www.kvoa.com -- "When News breaks, we fix it!"
KVOA Television, Tucson, AZ. NBC Channel 4
Still Cadillacin' - www.badnewsbluesband.com

"Informate-Rod" <InformateRod@discussions.microsoft.com> wrote in message
news:082389DA-8776-4853-B2E0-0C34A14051C5@microsoft.com...
> Hi All,
>
> I'm trying (without much success!!) to get all of our servers and
> workstations synchronised to a single time.
>
> NTP seems to be a way of achieving this.
>
> From what I've read it appears that I need to have ...
> 1. A single m/c (I'll call it "Timemaster") within our domain that
> periodically 'synchs' with an external accurate time source. Currently we
> are
> trying to use the PDC as the 'timemaster'
> 2. All other m/c's within the domain synch with "Timemaster" on a periodic
> basis.
>
> I have installed the Server res kt (incl supplement 4) on the 'Timemaster'
> machine and copied timeserv.ini into the 'WinNT' directory and
> Timeserv.exe &
> dll into the 'WinNT\System32' directory. A copy of our current
> Timeserv.ini
> file is included at the end of this mail.
>
> On the 'Timemaster' machine I've ...
>
> 1. Configured the time service (via control panel) to start automatically
> on
> NT load using a dedicated account having domain administrative privilege
> and
> able to 'logon as a service'. This account is also permitted to reach the
> web via MS Proxy (Webproxy) to our ADSL router.
>
> 2. Checked the time service and it says it is running - however when I
> look
> at the event log (I've turned on logging) it repeatedly records the
> following
> Event ...
> Description : "Modem timeout - might be BUSY "
> Event Id : 17
> Source : Timeserv
> Type : Warning
> User : N/A
> Also the current system time does not appear to be corrected as expected -
> it is currently about 45 minutes fast.
>
> 3. I've tried stopping and restarting the time service and performing
> 'cold
> boot' - always get the same result (as above).
>
> I imagine the problem is in the Timeserv.ini settings but i have double
> checked the entries and do not see anything that is obviously wrong -
> however
> I have only limited documetation about such settings. I do not see why it
> is
> trying to access a modem (the m/c in question does not have nor has it
> ever
> had a modem attached to it. I've looked at the timeserv.ini settings re
> modem
> based access and I think I've turned everything off - I am trying to get
> the
> service to use NTP
>
> However I'm unsure of the following settings...
> Type=NTP (should this be set to 'primary' ??)
> PrimarySource=\\TIMEMASTER (should this be set to the name of the
> machine??)
> Period=0 (not sure what to set this to)
> SecondaryDomain= (not sure what to set this to)
> Hour=6 (not sure what to set this to)
> TAsync=no
> TAsync (is this relevant ??)
>
>
> And finally even when I do get synch between 'Timemaster' and the external
> time source, how do I then distribute it o the other m/cs within the
> domain.
>
>
> REM This is TimeServ.ini, to be placed in %SystemRoot%
>
> REM Remarks and blank lines are allowed. Following is the section name:
>
> [TimeServ]
>
> REM remove the ; from in front of one of the Types, below.
> REM NISTACTS means dial NIST ACTS using the modem to set the time.
> REM PRIMARY means a networked machine intended in a second "tier"
> REM SECONDARY means a networked machine lower in the tier (a "client")
> REM USNO means dial Naval Observatory using the modem to set the time.
> REM INTERNET means use TCP/IP to access NIST
> REM NTP means use Simple Network Time Protocol over IP
> REM NRC means dial the National Research Council using the modem to set
> time.
> REM BBC means dial the BBC using the modem to set the time.
> REM COMPUTIME means dial Telecom Australia's service to set the time.
> REM EUROPE means dial a European service (Sweden/Austria/Germany/Italy,
> etc).
> REM MSL means dial the New Zealand Measurement Standards Laboratory
> REM GC1000 means use the Heath GC-1000 Most Accurate Clock
> REM GC1001 means use the Heath GC-1001 Most Accurate Clock II
> REM SPECTRACOM means use the Spectracom NETCLOCK/2
> REM HP means use the 58503A Time and Frequency Reference Receiver
> REM TIMELINK means use the TrueTime TL-3 WWV Timing Receiver
> REM TRUETIME means use the serial output from TrueTime product other than
> TL-3
> REM ARBITER means use the serial output from Arbiter Systems
> REM TRIMBLE means use a Trimble GPS with TSIP over RS-232
> REM ROCKWELL means use a Rockwell GPS with messages over RS-232
> REM ZODIAC means use a newer Rockwell GPS with messages over RS-232
> REM MOTOROLA means use a Motorola 8-channel GPS with binary format over
> RS-232
> REM or BC620AT, BC630AT, PC03XT, PCSG2, PCLTC, AMDAT, MOBATIME, RADIOCODE
>
> ;Type=SECONDARY
> ;Type=PRIMARY
> ;Type=NISTACTS
> ;Type=USNO
> ;Type=INTERNET
> Type=NTP
> ;Type=NRC
> ;Type=BBC
> ;Type=COMPUTIME
> ;Type=EUROPE
> ;Type=MSL
> ;Type=GC1000
> ;Type=GC1001
> ;Type=Spectracom
> ;Type=HP
> ;Type=TimeLink
> ;Type=TrueTime
> ;Type=Arbiter
> ;Type=Trimble
> ;Type=Rockwell
> ;Type=Zodiac
> ;Type=Motorola
> ;Type=
>
> REM The PrimarySource list below are the servers which are known good
> REM Each server name should start with \\, separated by a semicolon
>
> ;PrimarySource=\\TIMEMASTER
>
> REM Period 0 below means to use the default delay between each time set
> REM Default is daily for modem or every 8-12 hours for network
> REM Period can also be set to a number which means that many times daily
>
> Period=0
>
> REM Port is the name of the serial port used for modem, GPS, or clock
>
> ;Port=\\.\COM1
> ;Port=\\.\COM2
> ;Port=\\.\COM3
>
> REM ModemCommand below is the string used to setup and dial your modem.
> REM The &Q0 is desirable for high speed Hayes modems
> REM The &D2 is desirable for quickest hangup
> REM The plain ATDT is intended for older Hayes Smartmodem 1200 or 300
> REM A B15 may need to be added to force the BBC V.21 communication
> standard
> REM For USNO, S2 must be 43, S12 must be 50 or less, and must not be X0
> REM The entry with \N1 is intended for Megahertz XJ2288
> REM The entry with &A0&K0&M0 is intended for USR Sportster
> REM The entry with B5 03, is intended for PDI @ MS from 12-button phone
> REM The entry with B26 03, is intended for PDI @ MS from x-button phone
>
> ;ModemCommand=AT&D2&Q0DT
> ;ModemCommand=AT&D2DT
> ;ModemCommand=ATDT
> ;ModemCommand=AT&D2\N1DT
> ;ModemCommand=AT&D2&A0&K0&M0DT
> ;ModemCommand=AT&D2DTB5 03,
> ;ModemCommand=AT&D2DTB26 03,
>
> REM Prefix is the number dialed prior to the phone number, such as for a
> PBX
>
> ;Prefix=9,
> ;Prefix=
>
> REM PhoneNumber is the number of NIST in Colorado (+1 303 494 4774)
> REM or USNO in Washington DC (+1 202 762 1594)
> REM or NRC in Ottawa (+1 613 745 3900)
> REM or BBC in the UK (0891 516880 a special number inside UK only)
> REM or Computime in Australia (+61 03 9600 1641, or 02 9267 4648, or
> REM 07 3221 7033, 08 8941 3423, 09 221 5457, 08 8410 0143, 03 6224 1905)
> REM or Sweden (0900 100 2000 a special number inside Sweden only)
> REM or Sweden (0729 31 00 20 a special number inside Sweden only?)
> REM or Austria (+43 316 472366)
> REM or Germany (+49 531 512038)
> REM or Italy (166 11 46 15 a special number inside Italy only)
> REM or NPL in the UK (0891 516 333 a special number inside UK only)
> REM or Belgium (+32 2 3730320)
> REM or Netherlands (+31 15 2617181)
> REM or Switzerland (+41 313 233 225)
> REM or New Zealand (0900 45222 a special number inside New Zealand only)
>
> ;PhoneNumber=1 303 494 4774
> ;PhoneNumber=1 494 4774
> ;PhoneNumber=494 4774
> ;PhoneNumber=1 202 762 1594
> ;PhoneNumber=1 762 1594
> ;PhoneNumber=762 1594
> ;PhoneNumber=1 613 745 3900
> ;PhoneNumber=0891 516880
> ;PhoneNumber=03 9 600 1641
> ;PhoneNumber=316 472366
>
> REM NTPServer is the name or numeric address of an NTP server
> REM No default is given, since you should contact a timekeeper
> REM (If you don't know what this is, you shouldn't try NTP)
> REM (The names BroadcastClient and MulticastClient are reserved)
>
> NTPServer=swisstime.ethz.ch
>
> REM timesource is a flag used by LanmanServer, placed in the registry
> REM It should typically be set to yes when Type is Primary
>
> ;timesource=no
> timesource=yes
>
> REM Log is a flag used to indicate that you want an entry in the
> REM Application log of the Event Viewer upon every sucessful time set
>
> ;Log=no
> Log=yes
>
> REM (The following are rarely changed)
>
> REM SecondaryDomain defaults to searching for a timesource in your current
> REM domain. Alternatively, it can be set to a domain/workgroup name.
> SecondaryDomain=
>
> REM Speed 300 is most accurate for NIST, but 1200 is also allowed
> REM and 2400 seems necessary for the PDI pool at MS
> REM otherwise speed is forced automatically 300 for NRC/BBC
> REM and 1200 for USNO or COMPUTIME (or EUROPE).
> REM (For TrueTime, Speed must be set to 9600 or whatever is appropriate)
> REM (For many others such as Spectracom, Speed is automatic 9600, etc.)
> ;Speed=300
> ;Speed=1200
> ;Speed=2400
> ;Speed=9600
> ;Speed=14400
>
> REM RandomPrimary yes means to choose a random entry in the PrimarySource
> REM list, rather than starting at the top. As long as the chosen server
> REM remains accessible, it will continue to be used.
> RandomPrimary=yes
>
> REM Hour 6 means wait until a little after 6am for the second modem call
> REM The purpose is to call daily (or twice/day) at low long distance rates
> REM Hour 24 disables such special handling
> Hour=6
>
> REM TAsync no means to use TimeAdjustment API to disable CMOS sync
> TAsync=no
>
> Many thanks in advance for whatever help you can provide
>
> cheers
>
> Rod.
 
G

Guest

Guest
Archived from groups: microsoft.public.windowsnt.misc (More info?)

I'm using timeserv without problems with an INI file looking very similar to
yours.

Two questions, did you change the default CMOS setting at the end? Leave it
as per the example I believe.
Secondly, are you SURE that timeserv can reach your time server? Check your
firewall logs. timeserv _will not_ use the proxy, it will got "direct" so
has to be enabled explicitly.

Finally, search on the web for "NTP pool" and select one of the pool IDs
instead. This spreads the load around multiple servers and gives you some
redundancy.

Hope this helps,
Paul DS.