Discussion Locked

Time Service

0 helpful
7 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

I installed Time Service behind proxy on one of my server having internet connection. I am unable to get Timeserv.dll file from Microsoft FTP site. I see all the time service is running but I am sure it is not working properly. I checked NT Event viewer I get the following message: "The description for event id [6] in source {TimeServ} could not be found. It contains the following insertion string{s}:133.456" I did changed Timeserv.ini file couple of time with different NTP Server and updatedall the time. Let me know where I am doing wrong.

Thanks,

7 replies

by longmwa

There are three types of time sources that must be understood before you set up
the Time Service for your computer running Windows NT.

Top Level Time Source
---------------------

The top level time source represents an accurate time sourcesuch as an atomic
clock. The Time Service Initialization file, Timeserv.ini, lists many different
sources for accurate clocks, that is, NISTACTS, USNO, NTP, and so forth.

Primary Source (Masters of Time)
--------------------------------
These computers get their time from a top level time source and are primary time
sources for the other computers on your Local Area Network (LAN). The Type= line
of the Timeserv.ini file should be set to one of the top level time sources in
order tobe considered a primary time source. You can have as many Primary
Sources (Masters of Time) as you want on your network, but it is usually
sufficient to just have one.

Type=USNO

Secondary Source
----------------
These computers have their Type= line set to Primary and the PrimarySource= line
set to one (or more) of the primary sources separated by a semicolon.

Type=Primary
PrimarySource=\\NTPDC1;\\NTPDC2...

The secondary sources must have their TimeSource=line set to YES. Setting the
TimeSource=YES actually sets the timesource bit to true that allows down-level
clients to determine who the secondary time sources are. Secondary clients issue
a NetRemoteTOD API call to the primary source to get their time set.

TimeSource=YES

by lastsurvivor

Besides what has been describd in the above solution you should also be aware that Timeserv is not Y2K compliant and will not work when you start installing Win2000 servers into your enviroment. Time becomes very important in 2000. The new tool isW32time, it has some very good documentation and can be obtained off of the Technet CD or from the Microsoft site.

by jwildwind

Event code 6 just means your time is off by more than .5 seconds. To test if TimeServ is working, just manually change the server or workstation time to an incorrect time, then stop and start the service again. If the time changes, it's working. W32Time is virtually the same utility, however, as mentioned above, it's been MS certified.

This discussion is closed to new replies.