• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

better NTP client for windows

Red Squirrel

No Lifer
I find the NTP client built into windows is very flaky and half the time does not even work. I have configured our DC as the time server and pointed all workstations to it, local it seems to work ok, but for the DC to access the online NTP server (time.microsoft.com I think) it fails like 99% of the time. I've seen this in other environments then ours. I think it does not have a big enough time out so it just bails out too fast.

Anyone know of a stand alone app (no need to install) that will set the clock using an NTP time source? I'd code it myself but I don't know much about UDP programming, I've only done TCP. Guessing with UDP I need to handle more stuff myself as there is no error checking like TCP.
 
I like the Meinberg NTP client myself. You can choose to install it as a service, or just use the ntpdate application that it installs in the /bin folder.

AboutTime is also a good application as well.
 
You can set Windows to use a different NTP server other than time.microsoft.com.

I've tried that. Nothing wrong with the NTP server, it's the client that sucks at actually getting the time.

I'll try one of the suggestions and see how it goes.
 
Back
Top