<<We have had a repeating problem with raven.utc.edu (which hosts
Listserv and the LSMTP mail server) where on a cold boot of the machine,
it comes up with the year set to 2014.  It doesn't "appear" to be a CMOS
or clock problem as the clock and date are correct; only the year is
incorrect. The server is a 200Mhz Micron running NT 4.0.  We are running
the tardis time service (ring any bells?).  Once we set the date
correctly, it "stays fixed" until the next cold boot.  It is on a UPS
now, so hopefully there won't be another cold boot, but still I'd like it
fixed.>>


I haven't used "TARDIS"; I don't know if it has any known problems or
not. However, we've been using the TIMESERV utility that comes with the
NTS4 Resource Kit, and have had no problems with it at all. The nice
thing is that, in addition to its ability to run as an NT service instead
of an application, it can be configured to operate in either "source" or
"client" mode. So, one "master" machine on the organization/campus net
can run TIMESERV to get the time from NIST or an NTP source (or USNO, or
a WWV(H) receiver, or a GPS receiver, or...), and be the "master clock"
for other NT machines on the net which are also running TIMESERV, but in
"client" mode. Since TIMESERV also allows a machine to identify itself as
a LANMan-style "timesource" provider, these "second tier" machines can be
time sources for Windows (and DOS?) workstations.

Steve Dirickson         WestWin Consulting
(360) 598-6111  [log in to unmask]