
--------------------------------------------------------------------------
NOV-TIM2.DOC -- 19980217 -- Email thread on NetWare & Time Synchronization
--------------------------------------------------------------------------

	Feel free to add or edit this document and then email
	it back to faq@jelyon.com




Date: Fri, 20 Jun 1997 22:27:50 -0600
From: Joe Doupnik <JRD@CC.USU.EDU>
Subject: Re: RDATE

>I'm already using the /u UDP switch.. This is what confuses me the ICMP
>echo, ping, works but NTP isn't.. I know the NTP server works because our
>U*X work with it fine..Any clues??
-----------
	Hmmmm. Well, let me make a couple of guesses. For openers, NTP is
a real protocol, Network Time Protocol, beloved of Univ Delaware and
xntpd and such, RFC-2030. That stuff; great bedtime reading material.
Rdate is a simple "gimme the time of day" item probing TCP/UDP port 13
"daytime" which we can also do via Telnet host 13. I believe it's
"daytime" (ASCII) rather than port 37 "time" (binary) but I'd have to
look or ask Brad.
	To get a response the serving machine needs to have that service
enabled, most often by not deleting/commenting out the appropriate lines
in (SYS V) Unix file /etc/inet/inetd.conf. Try telnet to the machine to
find out. Below is a section of just such a file with selected items
turned off for security and denial of service protection. There must
be definitions of each service kind, say daytime, in etc/services.
	...
# Finger, systat and netstat give out user information which may be
# valuable to potential "system crackers."  Many sites choose to disable
# some or all of these services to improve security.
#
#finger stream  tcp     nowait  nobody  /usr/sbin/in.fingerd    in.fingerd
#systat stream  tcp     nowait  root    /usr/bin/ps             ps -ef
#netstat stream  tcp     nowait  root    /usr/bin/netstat netstat -f inet
#
# Time service is used for clock syncronization.
#
time    stream  tcp     nowait  root    internal
time    dgram   udp     wait    root    internal
#
# Echo, discard, daytime, and chargen are used primarily for testing.
#
echo    stream  tcp     nowait  root    internal
echo    dgram   udp     wait    root    internal
#discard        stream  tcp     nowait  root    internal
#discard        dgram   udp     wait    root    internal
daytime stream  tcp     nowait  root    internal
daytime dgram   udp     wait    root    internal
#chargen        stream  tcp     nowait  root    internal
	...

	Here is one of my rdate.ncf command files, just for reference:

load rdate.nlm /q /u /p 60 129.123.1.2 129.123.1.7 129.123.1.9

Translation: /q be quiet, /u use UDP rather than TCP, /p 60 poll every 60
minutes, and try one of the three addresses which follow.
Note, these are USU local time standards, please don't use them from your
place without permission from USU. See ftp.udel.edu for time standards
information.
	My Unix machine uses xntpd, the extended NTP daemon, to maintain
time smoothly. Please see netlab1.usu.edu, cd pub/mirror/freebird/internet/
server/xntp for my build of a current version on UnixWare. There is an
sntpclnt.nlm under development and mentioned on this list. The last time I
tried it, a couple of months ago, it had serious problems with NDS time such
that NDS was rapidly shaken out of sync. The authors may have improved it
since but I have not checked. Rumors suggest Novell is writing one too,
but I don't expect anything soon.
	Joe D.

---------

Date: Sat, 21 Jun 1997 12:36:29 +0000
From: Marin Dowlin <mdowlin@DCE.KSU.EDU>
Subject: Re: RDATE

Have you downloaded the new TCP/IP stack from the patch list? I think
the older version caused some problems with rdate on some machines,
at least it did on mine. Just make sure you have the gateways and
other settings right in the inetcfg when you do. Also how long has it
been since you used these servers? Are you sure they haven't been
moved? Might try using the Navy time servers and see if they work.
Took me a while to figure out that someone had given me the wrong
time servers on campus and I switched to the Navy time servers and it
worked.

------------------------------

Date: Mon, 7 Jul 1997 13:51:35 +0200
From: Henrik Olsen <Henrik.Olsen@IAESTE.DK>
Subject: Re: Netware tcpip time Sync

> I've got several 3.12 servers (all running tcpip.nlm) which I would
>like to time sync to a standard.
>
>A good choice for the standard would be our internet gateway router,
>a Cisco 2520. The router is running NTP at stratum 2 and has 4 peers.
>Our Unix machines sync to this router using NTP.
>
>I've tried RDATE.NLM on the servers but they don't seem to reach the
>Cisco. The Cisco supports Daytime (port13) and NTP (port 123) but I
>have no idea what functions RDATE.NLM needs.
>
>Does anyone know where I can find docs on RDATE.NLM or some
>other module that will talk NTP to synchronize a 3.12 server?

A year ago I asked Brad Clements about RDATE, and was told that it
uses the RFC 868 "Time protocol" (port 37), NOT the RFC 867 "Daytime
protocol" (port 13), so that's the one it has to provide for you to
use RDATE.

------------------------------

Date: Sun, 20 Jul 1997 11:01:48 +0200
From: Cox Marcel CIE <Marcel.Cox@CIE.SMTP.ETAT.LU>
Subject: Re: HELP: Login Time Restrictions Not Working!

>>Actually, we've found on our servers that login time restrictions ARE
>>adjusted when DST changes.  Individual user's restrictions most
>>definitely change when DST goes on and off -- we always get phone calls
>>from the early birds.  If there is some setting that can keep them from
>>changing, we'd love to know what it is.
>
>At our site too, I've set restrictions for a 3:00-3:30 off period.
>However they seem to kick in anywhere from an hour later on one server
>
>and 90 minutes later on the other server in the same tree, the only
>difference is that each server is in its own context.
>
>I've also noted that you can't even rely on the utility you use to set
>them. I've seen an instance of setting them from the 16 bit version of
>NWADdmin and then setting them from the MWAdmin95 and wind up having
>settings hours apart and get yet another set of settings if you use
>NetAdmin.
>
>Why when you set a time restriction can't it just read the system
>clock and call it a day, fooey on GMT or whether its DST or Standard
>time, if its 3AM, just do it.
>
>The bottomline is; Is there any way to insure that time restrictions
>work when they are supposed to?

A few words about how time restrictions work in a NW 4 environment:

Because NW 4 network can potentially span different time zones, time
restrictions are internally stored in GMT (UTC) time rather than in
local time. The consequenses of this are:
- time restrictions always stay the same in GMT time, so they appear to
change in local time
- in order to define time restrictions in local, the utility (NETADMIN,
NWADMIN, NWADMNxx) to define the time restrictions must know in what
time zone you are residing. This is based on the TZ variable defined on
the workstation. By not setting the TZ variable, the Netware
administrator programs will default to a time zone depending on the
compiler used to generate the utility. So in order to avoid confusion,
you should always set the TZ variable on your workstations (same syntax
as on the server). The easiest way to do this is through the system
login script.

How to solve the DST problem ?

1) Use a fake time zone without DST and do the time change yourself
(attention to syntectic time issues!)

2) Use a safety margin of one hour in your time restrictions so that
they work both in summer and in winter.

3) Use Novell's (unsupported) utility for bulk moving time restrictions.
You will find it in file TIMEFX.EXE at http://support.novell.com/nsd.htm

---------

Date: Sun, 20 Jul 1997 16:21:48 -0700
From: Norm Goodger <Norm@MACINFO.COM>
Subject: Re: HELP: Login Time Restrictions Not Working!

>A few words about how time restrictions work in a NW 4 environment:
<snip>

Marcel, thanks for that feedback, however according to Novell, the
Windows versions of NWAdmin use the time zone setting setup in the
Time/Date Control panel for Win95, the TZ variable only needs to be set
for the DOS NetAdmin.

I've seen a disparity between the 16 & 32 bit versions of NWAdmin of
hours when setting time restrictions.  The disparity between the settings
was if I recall about 5 hours difference from one utility to the other.

When I review the console for each server, despite having set each and
ever user to have an off time of 3:00-3:30am, on one server, the console
indicates that the user is logged off at 4 AM and at 4:35AM on the other.

I think there is a bug here in the admin programs. and I also think that
despite the fact that a tree can span time zones, the server should make
these decisions based on the time of the local server, (its supposed to I
thought) and not worry anything about GMT. In other words, if I log into
a server from California and its in New York, and the time restriction is
3AM, it should bump me at 3AM New York Time. Midnite in California. They
way it seems to be working now, I don't know when I might bump into the
time restriction.

------------------------------

Date: Mon, 21 Jul 1997 10:01:11 +0200
From: Cox Marcel CIE <Marcel.Cox@CIE.SMTP.ETAT.LU>
Subject: Re: HELP: Login Time Restrictions Not Working!

>I think there is a bug here in the admin programs <snip>

The 16 bit versions NWADMIN.EXE and NWADMN3X.EXE need the TZ variable
as Windows 3.x did not yet know timezones. Only the 32 bit versions
NWADMN95.EXE and NWADMNNT.EXE read the timezone information from the OS.
Therefore it is safest to ALWAYS set the TZ variable.Furthermore there
is a known bug in NETADMIN.EXE's handling of the TZ variable. See
http://support.novell.com/cgi-bin/search/tidfinder.cgi?2919090 and
http://support.novell.com/cgi-bin/search/tidfinder.cgi?2919521 for
details about this.
You should know that Novell's utilities rely on standard C runtime
libraries to handle time zones and that t depends on the C compiler used
how the utilities behave with respect of time zones, especially the
default time zone used in case the TZ variable is not set.

------------------------------

Date: Wed, 6 Aug 1997 17:00:49 +0200
From: Hans Nellissen <dbphilos@UNI-DUESSELDORF.DE>
Subject: Re: <help> How to synch NT 4.0 WS time to server clock?

If you know the mac-address from NT workstation, then you can do
a station-specific:
	net time \\server /set /y
in the login-script.

------------------------------

Date: Mon, 11 Aug 1997 19:56:39 -0600
From: Joe Doupnik <JRD@CC.USU.EDU>
Subject: Re: time problems

>Network is 10 machines running 4.11 patched to SP2.
>
>Occasionally, on one server only, if I write a file or create a
>directory, the creation time is different than the current time.  The
>two times I have verified this, it was about 4 minutes and 8 minutes
>off.
>
>This will last for about 15 minutes (guess).  This morning, it
>actually started timestamping directories correctly while files were
>still 8 minutes off, after I verified that both were wrong.
>
>It seems to affect all users simultaneously.  The same workstations
>can create files or directories on other servers with no problems
>during this time.
>
>I have verified that the workstation time and the server times are
>within a second or so of each other.  Dsrepair, time sync check, says
>all servers are in sync within a second.
>
>The server in question is the time reference server.
----------
	Seeing no response today let me venture some speculation.
	Are there Win95 machines on the wire advertising themselves
as NW servers? That means sharing files/printers over IPX? If so kill
them. Those objects are network black holes.
	Are your clients picking up time from NW 3 servers? They can,
provided NW 3 servers sync closely to the same time standard as NW 4
servers (many of use use RDATE on both flavors).
	Joe D.

---------

Date: Tue, 12 Aug 1997 11:16:59 EST5EDT
From: "Chris A. Bracy" <CABracy@ACCUSORT.COM>
Subject: Re: time problems

Thanx Joe for trying.  The client time is in sync within a second or
so.  While there are windows 95 machines on the net, they are not on
the same segment (actually none in the same building).  All NW3
servers are in sync.  The last instance (yesterday), from my machine,
if I created a file, the create time was 8 minutes behind.  If I
created a driectory, the create time was correct.  If I create a file
or directory on another server, the create times are correct.  Both
of these servers are in the same tree and in timesync.  I could
alternate any of these actions over a 15 minute period, with the same
results.  At a different time, files and directories acted the same.
After 15 minutes or so, it started working correctly.

---------

Date: Wed, 13 Aug 1997 08:48:44 -0600
From: Joe Doupnik <JRD@CC.USU.EDU>
Subject: Re: time problems

	Most peculiar! This leads one to ask whether there is something
odd on the affected server concerning writing to disk. To ensure we look
in the right places I would suggest trying the experiment again from
another client to the same server.
	Btw, Win95 machines falsely advertizing as NW servers need not be
on the same wire to cause trouble. They are on the network. Or to borrow
from one of Novell's current adverts: "It's not chaos. It is a network."
	Joe D.

------------------------------

Date: Fri, 22 Aug 1997 10:10:22 -0600
From: Joe Doupnik <JRD@CC.USU.EDU>
Subject: CRON for NetWare

	It used to be folks asked for a scheduling NLM for NW servers. Such
requests have decreased of late. But now Novell has issued a CRON.NLM, for
NW 4.1x only. Its description is attached below.
	The file is
	updates\nwos\inw411\cronnlm1.exe
which is obtainable from ftp.novell.com and its official mirrors (such as
netlab2.usu.edu and netlab1.usu.edu).
	Joe D.
---------
NOVELL TECHNICAL INFORMATION DOCUMENT

TITLE:  CRONNLM.EXE; CRON.NLM Server Utility
README FOR:  CRONNLM1.EXE

NOVELL PRODUCTS and VERSIONS:
NetWare 4.11
NetWare 4.1
IntranetWare

ABSTRACT:

Cron schedules commands to be executed on a NetWare server at specified dates
and times.

 NOTE: This utility helps system administrators.  It is provided free of charge
as a courtesy, and therefore, is not a Novell supported product.  Problems or
questions regarding this product can be reported via e-mail to
NTSUTIL@NOVELL.COM.


ISSUE:

 Installation Instructions:

 Copy CRON.NLM to the SYS:\SYSTEM directory on your server.


 Usage:

 Usage: load cron [logfile size]

 Logfile size specifies the size the logfile will reach before restarting.
This keeps the logfile from getting too large and crashing the SYS volume.  The
default is 5 MB (5000000).

 Description:

 CRON.NLM is adapted from the well-known Unix clock daemon.  Cron runs all day,
spending most of its time asleep.  Once a minute it wakes up and read
SYS:\ETC\CRONTAB.  Any commands scheduled in CRONTAB matching the current date
and time are executed.

 Cron records all actions in the log file SYS:\ETC\CRONLOG.


 CRONTAB SYNTAX:
 Each crontab entry has six fields, each separated by tabs or spaces:

     minute  hour  day-of-month  month  day-of-week  command

 Each entry is checked in turn, and any entry matching the current time is
executed.  The entry * matches anything.  A pound sign (#) is a comment.

      Examples:
	   #Min Hr   Dat  Mo   Day   Command

	   #print time every minute
	   *    *    *    *    *     time

	   #print volumes on the hour
	   0    *    *    *    *     volumes

	   #do backup Mon-Fri at 0430
	   30   4    *    *    1-5   load sbackup

	   #Mon, Wed, Fri at 1930 down server
	   30   19   *    *    1,3,5 down

	   #Xmas morning at 0900 only
	   0    9    25   12   *     load sing


Self-Extracting File Name: cronnlm1.exe

Files Included     Size     Date      Time

..\
    CRONNLM1.TXT     (This file)
	CRON.NLM            6321         8-19-97      3:38:50 pm


Installation Instructions:


 Known Issues:

 This version of Cron, schedules a wakeup call every 60 seconds since the last
time checked or the last command executed.  It does NOT attempt to reschedule
itself exactly on the minute mark.

 The keyboard buffer is stuffed with the command so anyone typing on the
console at the time will have their keystrokes intermingled with the command
Cron is executing.


 Frequently Asked Questions:

 Q: Some NLMs stay loaded even when they have completed.  The next time Cron
tries to load it, it will give a "non-re-entrant" error.  How can I unload
them?

 A: Some NLMs have command-line options for auto-unloading.  If not, you can
schedule an unload command one minute before the load command.  For example, if
you want XYZBACK.NLM to run EVERY night at 3:00 am, you would use "0 3 * * *
load xyzback" in CRONTAB.  Unfortunately, xyzback requires a manual shutdown.
It ran fine early Friday morning, but because the administrator didn't unload
xyzback, the server could not load it fresh again early Saturday and Sunday
mornings.  A new command needs to go in CRONTAB: "59 2 * * * unload xyzback".

 Q: Can I redirect NLM output to keep status reports?

 A: Although you get a status report of cron in CRONLOG, you can NOT get output
from any NLM that cron schedules.

------------------------------

Date: Wed, 10 Sep 1997 22:49:31 +0100
From: Knute Ream <knute@QUAKE.NET>
Subject: Re: NT time synchronizing

>I'd just installed the Netware CLient for Windows NT on some of our
>machines  running NT 4.0 Workstation but after doing so the clock on
>the machines wont sync with the time on our Netware 4.01 server. Even
>manually changing the time on the pc's and rebooting afterwards, it
>will still show the wrong time.

Well, Ed, it's like this:  the hooks that used to automatically synchronize
the workstation with the server at login relied on DOS, and Windows NT
treats system time in a way that DOS set time commands have no effect.  In
other words, in the current configuration, the Netware Client doesn't have
sufficient rights to change the time, and there isn't anything you can do
about it until Novell provides a new feature in the IntraNetware Client for
WinNT 4.0.

For what it's worth, I did get this reply from Forrest Swick (via this
listserv just last month) that may or may not be useful to you:

------------------------------

Date: Mon, 29 Sep 1997 08:51:02 +0200
From: Paddy Verberne <paddy@PI.NET>
Subject: Time Sync (re)

>>I have a network with 32 servers running a mixed 4.1 & 4.11
>>environment. I have the latest DS NLM's loaded ( 5.06 for 4.1,
>>and 5.81 on 4.11).  I had some problems with my NDS and replication.
>>I fixed the replication problems (1 crashed server and 1 DS version
>>issue), however i can't seem to get the servers to sync up the time.
>>Most of these servers are remote (T1's to all sites) and have checked
>>all my links everything appears normal except for the time stuff.

Well, at our site we experienced the same problems.
What did we do to resolve it?

1. We explicitly "told" our primary servers to get the time from the
reference server (TIMESYNC Add Timesource = "reference server", TIMESYNC
configured sources = on).

2. We turned of the SAP time-broadcast on the reference server (TIMESYNC
Service Advertising = off)

!!! Don't forget to activate the changes on each server with the TIMESYNC
Restart Flag = on.

This did the job!!

Why????? The SAP-broadcast of our reference server somehow got lost before
it was picked up by the primary servers. By forcing the primary servers to
get the time from our reference server SAP was no longer needed (at least
for the communication between the reference and primary servers).

By the way, we have 32+ Novell 4.1 / 4.11 servers which communicate over
both LAN and WAN.

------------------------------

From: "Angel Galan Galan" <agalan@paradis.ird.ub.es>
To: floyd@DIRECT.CA
Date: Thu, 23 Oct 1997 16:32:21 GMT+1
Subject: Time Zones

Here is a short file with some information for severals Time Zones
in the world. If you want, I can also send information about the
beginning and ending of daylight for each zone. Please, add to
the Novell NetWare FAQ and let me know if you want more information.

[australia-tasmania]
time-zone-name = EST
time-zone-full-name = Australia/Tasmania
time-zone-offset = -10:00
dst-name = none

[australia-queensland]
time-zone-name = EST
time-zone-full-name = Australia/Queensland
time-zone-offset = -10:00
dst-rule = none

[australia-north]
time-zone-name = CST
time-zone-full-name = Australia/North
time-zone-offset = -9:30
dst-rule = none

[australia-west]
time-zone-name = WST
time-zone-full-name = Australia/West
time-zone-offset = -8:00
dst-rule = none

[australia-south]
time-zone-name = CST
time-zone-full-name = Australia/South
time-zone-offset = -9:30
dst-name = none

[britain]
time-zone-name = GMT
time-zone-full-name = Britain
time-zone-offset = 0:00
dst-name = BST

[canada-nst]
time-zone-name = NST
time-zone-full-name = Canada/Newfoundland Standard Time
time-zone-offset = 3:30
dst-name = NDT

[canada-ast]
time-zone-name = AST
time-zone-full-name = Canada/Atlantic Standard Time
time-zone-offset = 4:00
dst-name = AST

[canada-est]
time-zone-name = EST
time-zone-full-name = Canada/Eastern Standard Time
time-zone-offset = 5:00
dst-name = EDT

[canada-cst]
time-zone-name = CST
time-zone-full-name = Canada/Central Standard Time
time-zone-offset = 6:00
dst-name = CDT

[canada-mst]
time-zone-name = MST
time-zone-full-name = Canada/Mountain Standard Time
time-zone-offset = 7:00
dst-name = MDT

[canada-pst]
time-zone-name = PST
time-zone-full-name = Canada/Pacific Standard Time
time-zone-offset = 8:00
dst-name = PDT

[canada-yukon]
time-zone-name = YST
time-zone-full-name = Canada/Yukon Standard Time
time-zone-offset = 9:00
dst-name = YDT

[europe-western]
time-zone-name = WET
time-zone-full-name = Europe/Western
time-zone-offset = 0:00
dst-name = WET-DST

[europe-middle]
time-zone-name = MET
time-zone-full-name = Europe/Middle
time-zone-offset = -1:00
dst-name = MET-DST

[europe-central]
time-zone-name = CET
time-zone-full-name = Europe/Central
time-zone-offset = -1:00
dst-name = CET-DST

[europe-eastern]
time-zone-name = EET
time-zone-full-name = Europe/Eastern
time-zone-offset = -2:00
dst-name = EET-DST

[iceland]
time-zone-name = WET
time-zone-full-name = Iceland
time-zone-offset = 0:00
dst-rule = none

[japan]
time-zone-name = JST
time-zone-full-name = Japan
time-zone-offset = -9:00
dst-rule = none

[new-zealand]
time-zone-name = NZST
time-zone-full-name = New Zealand
time-zone-offset = -12:00
dst-name = NZDT

[poland]
time-zone-name = MET
time-zone-full-name = Europe/Poland
time-zone-offset = -1:00
dst-name = MET-DST

[singapore]
time-zone-name = SST
time-zone-full-name = Singapore
time-zone-offset = -8:00
dst-rule = none

[turkey]
time-zone-name = EET
time-zone-full-name = Turkey
time-zone-offset = -3:00
dst-name = EET-DST

[us-est]
time-zone-name = EST
time-zone-full-name = US/Eastern Standard Time
time-zone-offset = 5:00
dst-name = EDT

[us-cst]
time-zone-name = CST
time-zone-full-name = US/Central Standard Time
time-zone-offset = 6:00
dst-name = CDT

[us-mst]
time-zone-name = MST
time-zone-full-name = US/Mountain Standard Time
time-zone-offset = 7:00
dst-name = MDT

[us-pst]
time-zone-name = PST
time-zone-full-name = US/Pacific Standard Time
time-zone-offset = 8:00
dst-name = PDT

[us-yukon]
time-zone-name = YST
time-zone-full-name = US/Yukon Standard Time
time-zone-offset = 9:00
dst-name = YDT

[us-hawaii]
time-zone-name = HST
time-zone-full-name = US/Hawaii Standard Time
time-zone-offset = 10:00
dst-rule = none

[us-east-indiana]
time-zone-name = EST
time-zone-full-name = US/East-Indiana
time-zone-offset = 5:00
dst-rule = none

[us-arizona]
time-zone-name = MST
time-zone-full-name = US/Arizona
time-zone-offset = 7:00
dst-rule = none

------------------------------

Date: Fri, 24 Oct 1997 10:50:21 -0600
From: Joe Doupnik <JRD@CC.USU.EDU>
Subject: Re: Daylight to Standard Time

>Being this is the first year I've run NDS, what do servers running NDS do
>when the time change from Daylight to standard time occurs, does it act
>like a program that would automatically change the time appropriately on
>the servers? Or does it require manually changing it from the console on
>each server and then letting it sync for the next couple hours or
>whatever it might take?
-----------
	NW 4 servers don't keep time in local units, but rather in global
units. Thus the TimeZone variable is used to convert back to local form,
including daylight's saving time effects, for presentation to mere humans.
Unix systems do the same, and have a TZ variable too.
	Joe D.

------------------------------

Date: Wed, 29 Oct 1997 12:18:31 +0800
From: Leonard Holling <lholling@RANDOMWA.COM.AU>
Subject: Re: Time Synchro - "Synthetic Time"

>I have one single and three secondary servers.  The single server has the
>correct update DST time, but the secondaries do not.  Three servers have the
>entire NDS database, one has none.
>
>Synthetic time has been issued.  I've read in a few books about synthetic
>time and I understand the relationships between the single and secondary
>servers.  No time config parameters have been made and all the defaults are
>in place.
>
>Time synchronization is active, but time is not synchronized.
>
>How do I reset the time correctly?  I'm leaning towards either doing an
>unattended full with dsrepair or rebooting the servers.  The book talks of
>unloading timesync to correct local time?

If the time is synchronised on all of the servers then you can go to the
master replica and choose the following option from within DSREPAIR

Goto the Advanced Options Menu
Replica and Partition Operations
Choose a Replica
Repair time stamps and declare a new epoch.

BEFORE doing this make sure that you run DSREPAIR on your servers to ensure
that NDS on your master replica is OK. If you have any doubts about it you
must fix it because what these options above do is wipe out on the
information on the Read/Write replicas and send down a new complete copy
to them from the master replica.

If you have WAN links to these other servers a lot of traffic will be
created as it resends all the data.

We had this problem when our time source service provider did some
Year 2000 testing and the Master Replica jumped forward 3 years and all
of the other servers played catch up to the new date and time. (Our
master replica for all servers is also our single time server and yes
I know all about primary, single and secondary time servers)

------------------------------

Date: Wed, 29 Oct 1997 10:12:28 +0200
From: Mike Glassman - Admin <admin@IAA.GOV.IL>
Subject: Re: Time Synchro - "Synthetic Time"

>>How do I reset the time correctly?  I'm leaning towards either doing
>>an unattended full with dsrepair or rebooting the servers.  The book
>>talks of unloading timesync to correct local time?
>
>We had a similar problem four weeks ago (after we modified time
>parameters), but we have only one stand alone server (IntraNetWare
>4.11).  DSREPAIR couldn't repair it in an unanttended operation.
>But DSREPAIR has got more options in its sub-menus. And one of these
>options (I can't remember, which option it was) solved the problem at
>our server and corrected the time stamp.

It is simple enough to set Time on the server (SET TIME...) and then
unload and load your timesync.nlm (unload....load), answer yes to the
question it asks you.

In regards to forcing a timesync + New Epoch in Dsrepair, that is not
recomended by Novell unless you are ABSOLUTELY sure that your NDS is
100% in sync, and they are right. If you are not in sync and you force a
new Epoch which as Joe stated forces a new full sync of the databases,
you will end up with more than just a timesync problem.

Dsrepair is a very friendly and easy to use tool, but if you are not
sure about something, an option, even if it seems to answer what you are
looking for, don't try it and then say oops.  Oops and Novell do not go
together.

------------------------------

Date: Wed, 29 Oct 1997 18:59:09 +0200
From: Mike Glassman - Admin <admin@IAA.GOV.IL>
Subject: Re: Time Synchro - "Synthetic Time"

>>It works, believe me :)
>
>UNLOADing and LOADing Timesync works for me also.
>
>>I had to change all my servers from primary to secondary and I had
>>to run thru almost all of them to do it.
>>
>>>>It is simple enough to set Time on the server (SET TIME......)
>
>It's this part that doesn't work.  type SET TIME=10:10 gives you the
>syntax of the SET command, and doing a plain TIME=10:10 is the same
>as typing TIME.

Don't type SET TIME=XX:XX, type SET TIME XX:XX (take out the equals sign
and replace with a space).

Then unload and load the TIMESYNC.NLM

That works.

------------------------------

Date: Mon, 3 Nov 1997 17:53:07 +0100
From: Hans Nellissen <dbphilos@UNI-DUESSELDORF.DE>
Subject: Re: location of sync.nlm?

>Can someone direct me to the present location of sync.nlm (used to set
>time for 3.x servers off of a 4.x server)?
>
>According to the faq links, it should be at:
>	ftp.novell.com/netwire/novuser/07/sync.zip
>
>However, it ain't there!
>
>I've looked around a bit and even tried Novell's file finder, with no
>success.

   ftp://ftp.uni-paderborn.de/ftp/disk6/simtel.net/msdos/novell/sync.zip

------------------------------

Date: Thu, 4 Dec 1997 07:00:00 MST
From: "Forrest H. Swick" <fswick@UNCO.EDU>
Subject: Re: NT Wkstn Time Redux - Solution

>> Per the faqs, I try to set my NT workstation time in the login
>> script (or at command prompt) with this: NET TIME \\BIGDOG /SET /Y
>> This yeilds "System Error 53 has occured _ The network path was not
>> found."
>>
>> 4.11 smp
>> Windows NT 4.0
>> 16mb token ring
>
>Is \\BIGDOG an NT or NW System?
>
>NW 4.11 BTW, I get that message at the command prompt, it doesn't
>show up in the login results box. I found a problem with our naval
>obs. time sync program that may be the real culprit. thanks

I have tried to use NET TIME from an NT Workstation to a Netware
Server and I always get errors. If anyone has ever gotten it to run
they haven't posted it - or else I was sleeping.

What I have gotten to work though is a Microsoft NT program called
TimeServ that synch's the time between an NT Workstation and either a
NT Server or Domain.

Get the latest Timeserv Documention from Doug Hogarth timeserv page
on the internet. He authored the majority of TimeServ (although
TimeServ is owned by Microsoft Corp.)

http://home1.gte.net/dougho/TimeServ.html

Then you can download the latest version from:

ftp://ftp.microsoft.com/bussys/winnt/winnt-public/reskit/nt40/i386/Tim
serv.exe

Though you need to still get the NT Resource Kit to have a license to
run it. The Resource kit has a really old verion of it that has some
bugs.

Load timeserv on an NT Server (it can be a PDC, server and maybe
an NT Workstation - I haven't tried the former though). I have it
set up here to do NTP on an NT4.0 server. Then load timeserv on your
clients to get their time from the "primary time server". Works like
a charm.  Much better then doing net time \\blahblah /set in the
login script. Only draw back is that you have to install it on each
NT workstation.

------------------------------

Date: Tue, 6 Jan 1998 00:30:30 +0100
From: "Arthur B." <arthur-b@ZEELANDNET.NL>
Subject: Re: Timesync Issue

>I have a primary time server with the wrong time and
>date. The server was down for about 10 hours
>because of a nic card failure when it came back up the
>time never resynced. If I unload timesync and reset the
>time and date as soon as I reload timesync it changes
>to the wrong time/date  and says that time is
>syncronized to the network. I have 4 other 4.11 servers
>that are set up as secondary time servers, they are
>fine. What to do?

Within SERVMAN there's an option to ADJUST time.

However, you may choose to reconfigure the current 'primary' to a
'secondary' and a 'secondary' to a 'reference' and another 'secondary'
to a 'primary' in this case. 'reference' servers do not adjust their
time. So in the end everything is equal to it (except for other
'reference' servers ofcourse).

BTW you need at least two 'primary' and/or 'reference' server.
An option is to have *one* 'single reference' and everything else a
'secondary'.

So, in short.
A 'single reference' may only exist if other servers are all
'secondary'.
A 'primary' and/or 'reference' only work if there's at least one other
of that kind.
'Reference' servers do not adjust their time. So please connect them to
a reliable time source. Unless you like cleaning up from a time drop
back to 1987 or so (eg BIOS time glitch).

If all fails simply perform a SET TIME on *all* servers. And after that
a TIME RESET using SERVMAN.
It may not be recommended by some but up to now this has worked for me.

---------

Date: Tue, 6 Jan 1998 09:29:09 -0500
From: "Davon L. Fay" <davon_fay@LESCREW.COM>
Subject: Re: Timesync Issue

I also had problems with timesync between two servers.  The problem was
resolved when I changed the configuration to a Single and Secondary
relationship.

Novell doc # 2930686 from kb was very helpful.

---------

Date: Tue, 6 Jan 1998 16:53:45 +0200
From: Jirka Hanika <HANIKA@KSVI.MFF.CUNI.CZ>
Subject: Re: Timesync Issue

>If all fails simply perform a SET TIME on *all* servers. And after that
>a TIME RESET using SERVMAN.  It may not be recommended by some but up
>to now this has worked for me.

I believe this is absolutely safe under 4.11, not really safe under 4.0
and I don't know for 4.1. I assume we're talking about an hour or so of
difference, not half a year, though. The INW can change the time in a
smooth manner (with a few "Synthetic time is being issued..." messages
at the console).

But first, please check ALL your time zone and Daylight Savings Time
settings - if you're wrong by 60 or 120 minutes, please take your server
back home from a foreign time zone before touching the time. I'd
recommend checking your BIOS time on all your servers once a year and
some simple scheme of Internet sychronization (e.g. rdate.nlm) to keep
your reference server reliable as well.

------------------------------

Date: Thu, 15 Jan 1998 01:07:46 +0100
From: "Arthur B." <arthur-b@ZEELANDNET.NL>
Subject: Re: Timesync Again

>>After setting up a Reference, 2 Primary and 5
>>Secondary Time Servers, I still can not get one of my
>>File Server to display the correct time (it is one of the
>>Primarys). I have schedualed a time reset, no good
>>the time resets and then goes right back after a bunch
>>of synthetic time messages. I have set the hardware
>>clock correctly, no good because the Server syncs to
>>the network with the wrong time again. It seems no
>>matter what I do, this particular server will only sync to
>>the network with the incorrect time excatly 10 hours
>>ahead of est. The Time Zone string is set for est5edt
>>and utc is 5 hours ahead. Any ideas?
>
>PRIMARY will always converge to REF time server.  Is your REF time
>server correct?

Compare output from the commands TIME and LOAD SERVMAN, Server...,
Time... with that of other servers. Make sure they comply. Make sure
AUTOEXEC.NCF and TIMESYNC.CFG contain what you see on the screens.
Update them if need be.

Don't be afraid to make use of DSREPAIR, ..., Declare New Epoch if
Synthetic Time re-occur *if* settings are what they should be.
DSREPAIR also has an option concerning Time Synchronization. That may
pop-up some helpfull errorcodes.

Another option, perhaps, is to swap a Primary and Secondary server.

In case of different NDS Tree names other rules may apply.

You're finished when time is correct and stays correct *and* the
command TIME states that "Time is synchronized to the net" on all
servers.

------------------------------

Date: Wed, 4 Feb 1998 07:00:00 MST
From: "Forrest H. Swick" <fswick@UNCO.EDU>
Subject: Re: Time sync on hybrid networks

>I have a Lan made up of NT4.0 servers, NT3.51 servers, NW4.1 and
>NW3.12 servers.  I am attached to a WAN on which there is a Primary
>timeserver running on an NT server.  The NT servers are thus a snap
>to sync, but how do I include the Novell servers in this?
>
>I would prefer to sync them to the same source as all my other
>servers, rather than having two master clocks.

For NT boxes use Timeserv from the NT resource kit there is an update
on the Microsoft Web site. Be sure to use this update for other
versions are very buggy. The timeserv homepage is
http://home1.gte.net/dougho/TimeServ.html

For Netware products use RDATE and have them point to the same
TimeSource the NT boxes use.

I have not found any tools for syncing time between NT and Netware
boxes. Following is what I do here. Use Timeserv to setup a primary
time source for NT boxes, this primary time source sets its time from
an atomic clock available via the Internet using UDP. I then run
Timeserv on all NT clients and have them point to the primary NT time
server. Thus all NT boxes get time off of one source.

I then have RDATE running in UDP mode on the Netware 3.11 boxes and
our lone Netware 4.11 server and then the non NT boxes get their time
setup upon login. RDATE is setup to get its time from the same atomic
clock that I use for Timeserv on the NT boxes.

Novell's NDS tools for NT MAY include a time syncing tool for NT
that would allow NT to get its time from the NDS tree. Though I'm
sure Microsoft will deny that it exists if it does and then deny
support for it :-), and then say it was one of their minions who did
it without management support. Couldn't resist.

------------------------------

Date: Tue, 17 Feb 1998 12:18:30 +0100
From: Schneck Axel <aschneck@DE.WANG.COM>
Subject: AW: AW: Info - Adaptec 2940/AIC7870.DSK and abends

>>Actually there is definitely a problem when using arcserve 6.1, inw,
>>iwsp4 and arcserve sp1. There are some tids about this. Novell's
>>temporary solution is to rollback the server.exe file (copy server.old
>>to server.exe). Also I tested on two different machines to find another
>>solution. On both machines the abends/hang ups went away after I set
>>the server to not synchronize the hardware clock (timesync).
>
>How do I set the server to not synchronize the hardware clock
>(timesync). Also would this command help a server whose clock
>runs fast or slow?

Go to Server Console: Load servman, Server Parameters, Timesync
Parameters, Parameter TIMESYNC Hardware Clock. Set this to off.

But be care and reading the help informations. If you have only one
server and its running as a reference or single, the server normally
would use the hardware clock to sync the time. On secondary and primary
the serve will set the hardware clock. In the last case you should be
aware when restarting the server to set date and time under dos before
starting. Also I always recommend to use an atomic clock module with
software.

------------------------------

