We have a NW6.5 SP3 server that seems to lose time every 35 minutes after
a reboot. We have timesync running through out our enterprise which
consists of over 40 servers.
This particular problem server is actually running in a VMWare ESX 2.5.1
server, along w/ 2 other Netware 6.5 servers. Of the 3 Netware guest on
this ESX server, only one of them tends to lose time, the other two are
rock solid. The server I'm having an issue with is a Primary time server,
while the other two are Secondary's, I've even reconfigured the problem
server as a Secondary server, and it will still lose time after a
unload/reload of timesync.nlm. This is really causing me to scratch my
head, I've read over a few TID's on timesync, and it's pretty much one of
those things that once it works, it continues to work. All three of the
server on the one ESX server, have the same three time sources, it's just
the problem one is supposed to have about 8 other secondary servers
pointing to it for time. I've since changed every server that was
pointing to the problem server, to point to another server, but that still
leaves me w/ a single server w/ serveral R/W partitions that continually
is out of sync (not a good thing).
I've compared versions of timesync.nlm, nic drivers, and these are the
same, I'm not using the option to sync time w/ the ESX server, mainly
because we are not using it on any of our other 17 or so Netware servers
located within VMWare on different hosts, because we'd like to keep it
default as much as possible, and it's just one server w/ a problem.

Below are the timesync.cfg files, and all servers are run w/ a debug level
of 7.
I've double checked that the Default Server Type and the Server Type are
both set to Primary, other than that and the sources, all configs are
default.


BAD SERVER:
# TimeSync.Cfg is now updated automatically, # when changes are made on
the System Console

# TIMESYNC Configuration Parameters

Configured Sources = ON
DEBUG = 7
Polling Count = 3
Polling Interval = 600
Service Advertising = ON
Synchronization Radius = 2000
Type = PRIMARY
NTP Client Port = 0

# TIMESYNC Configured time source list

TIME SOURCE = SERVER-S1:123
TIME SOURCE = SERVER-S2:123
TIME SOURCE = SERVER-S3.XXXX.XXXXXX.COM:123

GOOD SERVER:
# TimeSync.Cfg is now updated automatically, # when changes are made on
the System Console

# TIMESYNC Configuration Parameters

Configured Sources = ON
DEBUG = 7
Polling Count = 3
Polling Interval = 600
Service Advertising = ON
Synchronization Radius = 2000
Type = SECONDARY
NTP Client Port = 0

# TIMESYNC Configured time source list

TIME SOURCE = SERVER-S1:123
TIME SOURCE = SERVER-S2:123
TIME SOURCE = SERVER-S3.XXXX.XXXXXX.COM:123

OTHER GOOD SERVER:
# TimeSync.Cfg is now updated automatically, # when changes are made on
the System Console

# TIMESYNC Configuration Parameters

Configured Sources = ON
DEBUG = 7
Polling Count = 3
Polling Interval = 600
Service Advertising = ON
Synchronization Radius = 2000
Type = SECONDARY
NTP Client Port = 0

# TIMESYNC Configured time source list

TIME SOURCE = SERVER-S1:123
TIME SOURCE = SERVER-S2:123
TIME SOURCE = SERVER-S3.XXXX.XXXXXX.COM:123

Any suggestions would be appreciated. Chris