My guess would be 3 minutes off across the domain and wrong time zone on Doug's server.

The 3-minutes off is true. But the time zone is the the time zone they want to use -- one time zone for everybody. Mountain Standard Time without daylight savings, I think. Since the idea was to have time synchronization to the workstations turned off, it really doesn't matter what time the server is set to.

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?

The timestamp dependent licensing is a completely separate software system, running on a different server, and does not interact with the Prophet (Novell) software or server in any way, other than once a day creating a set of text files containing logging information that is uploaded to the prophet server. I am guessing that it was during this upload process that the time on my workstation was being reset to the Novell time. But it only happened occasionally. I am sure that now we know what is causing the problem, we will be able to find a common thread linking all of the "problem" workstations (about 20 out of the 50 or 60 in the building) that are/were having timestamp problems.

tanstaafl.