Time Synchronization Problem 2

[JenniferC]

Hello ..

Have compaq 1600 server loosing 10-20 minutes / day. R/O hardware as cause. Rumor that timesync.nlm problem and need to back rev to 5.09. Anyone else hear of this? Single reference server. NT boxes on Network. Have tried all suggestions on Novell site.

Thank you in advance

 

[DrGreen26]

Well, you could back rev it, that won't hurt...if you have the same results, make sure that in teh server settings that the hardware clock is set to ON.

I can help you out more with this if you have already checked this.

Mark

Mark C. Greenwood, CNE
m_jgreenwood@yahoo.com

CNE 4.11 and CNE 5 certified. BS Degree in MIS. Working in the industry for 8 years.

I work with NT servers, NDS for NT as well.

 

[JenniferC]

Just to let you know .. I used TID 10053068 after query "5.09" only on novell site. This solution worked. Thank you for your follow up and offer to help.

Jennifer

 

[ChrisBzy]

Hello JenniferC

I have just upgraded a Compaq 1600 server to NetWare 5.1 and am losing about 12 minutes a day. Your problem sounds very much like mine and I was interested in maybe getting more details from you on this matter. If you have the time maybe you could send me an outline of your actions in correcting this. Thank you for any help you may be able ot offer in this matter.

chrisb@srminc.net

 

[TheLad]

You guys could update TIMESYNC.NLM if it is not at the latest level. Please note: I do not think that the latest Novell Service Packs update TIMESYNC.NLM as standard. The Service Packs ship the NLM but you have to upgrade manually.

The latest TIMESYNC.NLM is v5.23 (dated 24th August 2001) but this is a beta patch. The previous version that ships with NW5.1 SP3 is 29th June 2001 and NW5.0 SP6a is 22nd August 2000 but you can use the newer one on both NW5.0 and NW5.1

TID 2960018 refers to v5.23 of TIMESYNC.NLM - this address time drift amonst other issues.

 

[JenniferC]

Hello .. this is straight from the TID 10053068. The only difference = timesync.nlm = 5.15 dated 8/29/00 was used - instead of the recommended (TIMESYNC:NLM version 5.15 dated 6/12/99)

Note: We have a single netware 5.1 server (compaq 1600) and feel that the problem encountered was due to hardware conflict.

Configure the server to use an NTP time source to force synchronization with the server's internal hardware clock.

Settings in MONITOR | Server Parameters | Time:

Default Time Server Type: SINGLE
Timesync Configured Sources: ON
Timesync Hardware Clock: ON
Timesync Service Advertising: ON
Timesync Time Sources: 127.0.0.1; (loop back address for NSBS5: 127.127.1.0
Timesync Type: REFERENCE

This combination of SINGLE and REFERENCE server type and server loop back delivers exact time taking the time from DOS/BIOS.

3. Set Timesync Restart Flag = ON

It has been 2 1/2 months without a drift. Hope this works for you. Jen

 

[ChrisBzy]

Hello

Sorry to keep returning to this, but I've made the changes suggested in your post and the server was able to reset the correct time at bootup, but is still losing time while running. I'm thinking I don't have the correct entries in the "Timesync Time Sources:". Could someone explain what I'm looking at in the following line? Is NSBS5 the server name in this case? Shouldn't there be a port number (123) with the IP's?

Timesync Time Sources: 127.0.0.1; (loop back address for NSBS5: 127.127.1.0

I'm not a Novell person by a long shot, but am trying to clear up a problem on a server where our Novell person has moved on.

 

[ChrisBzy]

Jennifer, DrMarkGreen, and the Lad

Thank you, your input here also helped me out. After reviewing your posts with my notes a few blanks most have gotten filled in because it all made sense and I'm running fine now. This is in a single server tree and the workstations get thier time from the server.
My settings ended up as follows

Default Time Server Type: REFERENCE
Timesync Configured Sources: ON
Timesync Hardware Clock: ON
Timesync Service Advertising: ON
Timesync Time Sources: (here I inserted the server name and ip)
Timesync Type: REFERENCE

This has been running now for 5 days now, also as I figured the backup failures have stopped also. Well thanks again!