NetTime works very well for me. There is a little thing about its behaviour at startup, which I couldn't call a problem, because the time is adjusted just as it is later in the day. Here is the most recent part of my log file:
11/10/2014 1:22:51 AM ntp0.nl.net: Good +493ms (13ms)
11/10/2014 1:22:52 AM Time Updated: +493ms Regular Update
11/10/2014 10:26:50 AM Time Sync Failed! Time jumped forward!
11/10/2014 10:26:50 AM Failure Reason: Network Down
11/10/2014 10:27:05 AM ntp0.nl.net: Good -912ms (0ms)
11/10/2014 10:27:04 AM Time Updated: -912ms Network became active
11/10/2014 5:29:20 PM ntp0.nl.net: Good +519ms (10ms)
11/10/2014 5:29:21 PM Time Updated: +519ms Regular Update
11/11/2014 12:29:31 AM ntp0.nl.net: Good +491ms (7ms)
11/11/2014 12:29:31 AM Time Updated: +491ms Regular Update
11/11/2014 9:12:25 AM Time Sync Failed! Time jumped forward!
11/11/2014 9:12:26 AM Failure Reason: Network Down
11/11/2014 9:12:41 AM ntp0.nl.net: Good -932ms (0ms)
11/11/2014 9:12:40 AM Time Updated: -932ms Network became active
As you can see, I get a message that "time sync failed" after startup. The only reason seems to be that the system is not yet ready to process the request. 15 seconds later the time is updated, in an improbable 0ms. It's not bothersome at all (I could just leave the log file alone), but I thought I should mention it. My OS is Windows 8.1.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Sorry for the delay in responding - for some reason, I didn't get a notification from SourceForge when you posted this. (It's better to email me directly through timesynctool.com so that I get the message straight away)
When starting up, it should hold off on attempting the first sync if it detects that the network connection isn't yet ready - it looks like in your case, it's not doing that though, so it would be worthwhile investigating further.
The reported 0ms delay is also rather curious, so I would like to look into that as well.
Can you try turning on debug level logging and then email a copy of the log to me please?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
NetTime works very well for me. There is a little thing about its behaviour at startup, which I couldn't call a problem, because the time is adjusted just as it is later in the day. Here is the most recent part of my log file:
11/10/2014 1:22:51 AM ntp0.nl.net: Good +493ms (13ms)
11/10/2014 1:22:52 AM Time Updated: +493ms Regular Update
11/10/2014 10:26:50 AM Time Sync Failed! Time jumped forward!
11/10/2014 10:26:50 AM Failure Reason: Network Down
11/10/2014 10:27:05 AM ntp0.nl.net: Good -912ms (0ms)
11/10/2014 10:27:04 AM Time Updated: -912ms Network became active
11/10/2014 5:29:20 PM ntp0.nl.net: Good +519ms (10ms)
11/10/2014 5:29:21 PM Time Updated: +519ms Regular Update
11/11/2014 12:29:31 AM ntp0.nl.net: Good +491ms (7ms)
11/11/2014 12:29:31 AM Time Updated: +491ms Regular Update
11/11/2014 9:12:25 AM Time Sync Failed! Time jumped forward!
11/11/2014 9:12:26 AM Failure Reason: Network Down
11/11/2014 9:12:41 AM ntp0.nl.net: Good -932ms (0ms)
11/11/2014 9:12:40 AM Time Updated: -932ms Network became active
As you can see, I get a message that "time sync failed" after startup. The only reason seems to be that the system is not yet ready to process the request. 15 seconds later the time is updated, in an improbable 0ms. It's not bothersome at all (I could just leave the log file alone), but I thought I should mention it. My OS is Windows 8.1.
Hi Gerrit,
Sorry for the delay in responding - for some reason, I didn't get a notification from SourceForge when you posted this. (It's better to email me directly through timesynctool.com so that I get the message straight away)
When starting up, it should hold off on attempting the first sync if it detects that the network connection isn't yet ready - it looks like in your case, it's not doing that though, so it would be worthwhile investigating further.
The reported 0ms delay is also rather curious, so I would like to look into that as well.
Can you try turning on debug level logging and then email a copy of the log to me please?