Time not synchronizing amoung servers

[natesin]

We have Netware 5.1, 5.5, and 6. 6 is synced with our NT/Windows servers just fine, but our 5.1 and 5.5 servers are about 4-5 minutes fast.

Our main Novell guy is on vacation this week. This is causing issues with trying to change passwords in Console1. We also have Account Management 2.1 installed for password synchronization. I am not a Novell expert, but I thought the servers in the tree were to synchronize automatically. If not.. Is there something I can do to fix this issue?

Any help greatly appreciated.

TIA
Nate

 

[gconnect]

although it is pretty fast sometimes it takes a while for NDS replicas to synchronize between servers

have you tried using:
load dsrepair -a
time synchronization

to see if the server's are in sync

i have never used Account Mgr


when you make changes to an NDS object (accept for file access rights), these changes are not stored directly on any servers file system per-say, rather they are stored in the NDS eDirectory.
all of that information is held within NDS
any changes made to any NDS object (user, etc) and its properties are contained in NDS

so the password change was modified in NDS through Console One on whatever server you were using



p.s. are these servers stretched out over WAN links (if so what speed)?

 

[Lou0686]

Hi Nate,

Type TIME at all the servers. Are they all synchronized to the network? If not, fix that first.

A quick resolution would be to unload reload timesync back on the servers that are off. It will take 1-2 minutes to resync.

Lou

 

[Ronstid]

I am having a similar problem with 2 Novell 6 servers syncronizing with the Windows 2000 server. My Novell servers are sync'd together, but are 10 minutes slower than the Windows server. Novell servers are getting their time from the Win2k server, which is getting it's time from an NTP time source.

I have already unloaded/reloaded TIMESYNC.NLM. I have also added the suffix ":123" to the IP address of the Windows server in "Time Sources" as directed by one of Novell's TID's. Neither worked.

Does anyone have any more info they could share? Thanks.

 

[natesin]

gconnect and lou0686,

Thanks for the input.

I resolved the sync issue. Our Netware 6 was set to primary and is syncing with a internet time source on port 123. Our netware 5 & 5.1 servers were set to single ( Ididn't set these up our Novell guy did). I changed them to secondary, checked some of the other settings and reloaded the timesync.nlm. This seemed to do the trick.

Ronstid,

You may want to set one of your Netware servers to the primary, the other to secondary, and let windows get it's time from Novell (this is done by the Novell client installed on Windows server, assuming you have that installed). You can set the primary timsync server to get its time from an Internet time source. Your gateway router will have to pass port 123 traffic.

I am not as well versed at Novell, that is just a suggestion for you to think about.

Regards,

Natesin

 

[Ronstid]

Thanks for the info. My servers are already set that way, but I don't have the authority to change it (although I wouldn't mind doing that). I appreciate your input. Thanks again.

 

[Ronstid]

I fixed my problem by getting my time from an NTP time source rather than the Windows server here. I had to get permission from the boss first. Works like a charm now! Appreciate all the help.

 

[terry712]

agree

we have one netware as a single which gets it's time from an internet ntp source
all netware are secondary and get it from the single
all nt and 2000 servers point to single as an ntp source
all pc's get it from the local netware server

works sweet as a nut