There's no external time source. ntpd went down again yesterday. I'll try setting both to 127.127.1.0 and see what happens.

Is this a standalone network or can you use network time servers?

Difficult to know if a process is causing the problem or is it just an undisciplined clock on the server. By undisciplined there is no drift compensation.

If you are connected to the internet then it would be best to add a server pool. You can find the ones closest to you
http://www.pool.ntp.org/en/

It's on a standalone network. No internet.

How many other computers are on the network and what OS are they running?

You can set up a similar fudge time source on the client so when ntp does not like the server's time it will switch to local time and not stop running.

In addition you can manually adjust the clock to improve long term stability. The following link provides some details.

http://www.smartpixie.com/wiki/Tech/...lockGuide.html

How important is keeping accurate time between the server and client? GPS receivers are cheap and it is fairly simple to set up your own time source.

Seems to be working ok now. It hasn't died for a week now. Changing the fudge to 127.127.1.0 seems to have fixed the issue. I had found a guide online that said to set it to 127.127.1.1. Maybe it was a typo/