Discussion Locked

Novell server 5.1 loose time day after d

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

After I upgrade novell from 4.11 to 5.1 the server looses time I upgrade the timsync.nlm
no change. I need your help!

Thank you.

14 replies

by jose mir

Can you give more details?
Have you obtained some kind of message (like synthetic time, or something similar)?
If you giveme more details I will help you!

Jose P. Mir.-

by grbeckmeyer

I have seen this with TIMESYNC.NLM version 5.12 and higher. I have had success correcting this by back revving to v5.09 and also v5.07

by jimbb

Change these timesync parameters:
-SET TIMESYNC CONFIGURED SOURCES=ON
-SET TIMESYNC TIME SOURCES=127.0.0.1:123
-SET TIMESYNC HARDWARE CLOCK=OFF
-SET TIMESYNC DIRECTORY TREE MODE=ON
-SET TIMESYNC DEFAULT TIME SERVER TYPE=REFERENCE
-SET TIMESYNCTYPE=SINGLE
That should make the server run on time. You can set all of these in Monitor|Server Parameters|Time.

Jim

by jimbb

What this "trick" does is force the server to check his own hardware clock, but make it assume it is an external NTP time source ("127.0.0.1" is the server's own address, ":123" is telling him to use NTP). For some reason that does keep the server running on time, while doing the same but without the NTP makes the server's time drift up to 2 hours per week.

Jim

by tx-netware

I'm having the same problem on one. New IBM x220 and NW5.1. No messages. Default time server set as single. The system loses about 15 minutes a day. IBM is helping me troubleshoot but they also tell me that there are some time reporting issues with Netwre 5.1 that there are patches out on. I haven't had time to really look for them yet. I'll keep watching this thread.

by theitfish

I had same problem with IBM Netfinity 3000 and Netware 5.0. Found a TID on Novells site that recommended diasabling the IDE CD drive.
type at the console
unload IDECD
unload IDEATA
It worked for me, I don't use the cd in server so there is no issue.
Andrew

by sanjeevk

I had faced the similar problem earlier after I installed Support Pack 2 from Novell.
After taking up the matter with the support team of Novell, I came to know that they have released a few more patches which take care of this problem. After I loaded thiese patches, the problem vanished.

The patches are :
OS5PT2A.EXE, TS520J.EXE, WSOCK4B.EXE.

All these patches are downloadable from Novell's website.

Regards
Sanjeev Khanna

This discussion is closed to new replies.