#43 jumps to 2062

[Anonymous]

we have nettime running on some of our servers and workstations...
we have it configured to a internal clock source and also 2 external clock sources.

Twice now, anyone Server or workstation that has that software installed has had their time "jump" to the year 2062. Note again, it is only on the machines and/or servers running nettime.

the ones that are not running them, nothing happens to them...and for them we use the W32time command included with windows...and they are fine.

Any reason why this is happening to only the machines that have nettime installed?

Thanks.

dshah@alhurra.com

[Nobody/Anonymous]

Logged In: NO

Perhaps one of your external clock sources is sending out wrong data, either inadvertently or intentionally?

[Mark Griffiths]

It could be bad results being returned by one of your time servers, or it could have been a bug in NetTime - it's hard to tell without more information.

NetTime Version 3 has additional checks so that as long as you have more than 1 server configured, no single server can accidentally or intentionally put your time out like that.

In the event that something like this does happen with Version 3, please post a follow up comment so that I can look into it further.