Set Time on server 1

[AGA]

Time on a Netware 5.0 server is always behind and we have to manualy set the time every day. Will the latest service pack solve this problem or is there any other alternative solution to this problem. At the moment I am Not sure what which version of servce pack it has.Thanks

 

[TheOtherKiwi]

You need to read an FAQ on NTP and time sync in NetWare. If you have a single server then it is likely that the time is based on its CMOS clock and probably inaccurate. Reference its time to an accurate source and your problems go away.

Look on

http://www.novell.com

for info on NTP..ona nd apply the latest service packs as there were many fixes for time sync in older releases or even better...upgrade to NW5.1

 

[TheLad]

To find out the Service Pack, type VERSION at the console. The latest TIMESYNC.NLM will certainly help, but as already suggested have a look at NTP.

-----------------------------------------------------
"It's true, its damn true!"
-----------------------------------------------------

 

[Depthcharge]

I had the same problem. service pack 6 fixed it.

 

[fitzdr]

Assuming that your hardware clock stays up to date you can do the following.

If TIMESYNC.CFG is set to "hardware clock = on" it will reset to the hardware clock which is not losing time.

The otherkiwi's idea of setting the NTP time source to a source on the Internet will be your most reliable. Also if you have several servers geographically dispersed you should use the model of Reference-Primary-secondary. You can point the Reference to a time source on the Internet then all of your WS and servers will be up to date.

Below is an example of what the config for the reference server would look like,
-------------------------------------
Default Time Server Type: Reference
TIMESYNC Configured Sources: On
TIMESYNC Time Sources: 192.6.38.127:123; 204.152.184.72:123;

To configure see the following support articles,
TID10050215, TID10070057, TID10060982,

 

[macfoxx]

Hello
I think that is very old problem made by CDROM.NLM.
This module if loaded from startup.ncf makes difference in time. If you don't need use cdrom, you can remove this line in startup.ncf or autoexec.ncf

Bye

 

[AGA]

The Problem is Solved by using precision time on one of the workstation and the Novell server syncronizes with the workstation. No need to apply the services pack for Novell server.

http://www.precision-time.com/

 

[marvhuffaker]

That seems backwards. Why not point the novell server to a global timesource on the Internet? It's common for Hardware clocks to run fast or slow, and that usually fixes it.

The workstations will then get the time from the server, the way it was intended to be.



Marvin Huffaker MCNE, CNE
Marvin Huffaker Consulting

http://www.redjuju.com

 

[AGA]

But the Novell server has no web access

 

[AGA]

But the Novell server has no web access

 

[marvhuffaker]

Ok, slap me with a wet noodle if I'm wrong here.. But, if your workstation can sync with a time source out on the internet, then your server should also be able to. Precision Time is just going out to a time source on the internet, that is all. And with Precision Time, you're also getting spyware (Gator/Gain) unless you pay extra, something you wouldn't have to do with Novell as it's a built in feature.

I don't understand your logic. Do you have something that specifically blocks traffic from the server, and what would be the point of blocking the server from making outbound requests of this type?

Maybe someone else could back me up here, but it seems to me like you're implementing a solution for a problem that doesn't even really exist. I could go on and on but then David will send me an email.

Marv

Marvin Huffaker MCNE, CNE
Marvin Huffaker Consulting

http://www.redjuju.com