At least you've identified the problem.

Is that a subtle dig??

Client time synch in the Novell client is about the same as Windows NET TIME, IIRC -- fire and forget. Synch time at logon then that's it. PCs that logon and off more frequently tend to have more accurate time! PCs that remain logged in for long periods risk more drift.

Server time synch used to be a big weak point on Novell -- very weak tools to get external time, people had to rely on odd assortments of (sometimes unsupported) NLMs to do it.

With Netware 4/5, time synch is critical to correct NDS replication. If servers get seriously out of whack, VERY BAD THINGS (tm) are likely to happen as Doug's contact suggests. Nowadays, the process for inter-server time synch in Netware is very good; it has to be. However, the important thing is not that the servers have the correct time, but that they *agree* on the time. Sounds like this is either an older Netware config or that someone didn't take appropriate measures to synch to a correct time source outside of their immediate domain. My guess would be 3 minutes off across the domain and wrong time zone on Doug's server.

Doug, given what you said about timestamp-dependent licensing, one risk of unsynching time from your (incorrect) server or of synching independently to an NTP source would seem to be that your clients could be either ahead or behind of that server's time. Is that (incorrect) server the ultimate authority on the licensing thing?

FYI, I stumbled across Prophet's download page