Time Sync (NW 4.11)

No way to preoperly answer this one without knowing a bit how timesync is set up. Reference? Single? Primary? Secondary? External sources?
One thing to start with, is to type "set timesync debug=7", and see with which server(s) this slow one is trying to exchange things. Maybe that already gives a hint.

By the way, "10mins out of sync" is already a l?t. By default time is polled/exchanged/corrected every 10 minutes, so that would mean that the clock of your server is as good as standing still, if not running backwards...

Jim

You can never be in sync if all 5 are secondary. You have to think a little about what you want to do, since time-traffic will travel across your WAN.

If every site has one server, I would consider having one Single, and the others Secondary.If there are sites with more servers, I would consider one Primary server in each site with more than one server, and all the others secondary.
The "voting" process between the Primary servers takes a little more traffic that the polling process ofthe Secondaries, but if you configure the secondary servers to have the Primary on their own LAN as their "Configured Source", the voting traffic will be less than having two or more secondary servers from the same LAN poll time over the WAN.

Anyway, you need at least one Single or Reference, or at least 2 Primary, or a Reference and at least one Primary, to have one or a few servers "decide" what time it is. The rest can be secondaries that simply ask the time. In your cases, nobody had the authority to decide, so they were all on their own.

Jim

I had a similar problem on one of our servers. It turned out to be a RTC hardware problem, I found a work around was to just unload then reload timesync.nlm . I put a novell batch file (stuffkey.nlm) in the autoexec.ncf to do this automaticly upon boot-up.

Les