Time Server

[tim-from-pa]

I want to know if anyone here synchronizes their computer clock with a reliable service other than Microsoft or nist time servers? I use nist and my one computer constantly gets errors. I have a repair program that fixes it (before it would not work at all even with manual updating) but I have to hit the button a few times before it will take. I even upped the frequency to once daily instead of once weekly and yet it has not synchronized in several days which means it gets far more errors than successful syncs.

And the answer is no, I do not have my firewall on, only avast as with the computer downstairs here and this one has no issue with nist. It's probably a quirk with my computer, but I would like to try another service first before just turning it off and resorting to typing in the time every so often.

 

[inhopeofglory]

Try Atomic Clock Sync. I've been using version 2.6 for years with no problems, although I manually start the program whenever I want to correct the time, rather than have it run automatically. However, I've had no problems whatsoever with it syncing to the server...

http://www.worldtimeserver.com/atomic-clock/

 

[tim-from-pa]

You know what? I'm really stupid (or lazy) at times. This is the very program I used that I mentioned earlier that repaired my windows synchronization service. But when I reread it more carefully, I see they do have their own time server as well. Let me try that now. Or as Home Simpson would say, "Duh!"

Thanks.

 

[Nick]

What's wrong with the Windows one?

 

[Vic C.]

I look at my cell phone. If the time on the PC doesn't match, I adjust it. :D It take a whopping 5-6 seconds.

 

[Nick]

I look at my cell phone. If the time on the PC doesn't match, I adjust it. :D It take a whopping 5-6 seconds.

Same here!

 

[tim-from-pa]

I know it's been awhile, but I finally fixed the issue. Ironically I did a search on the error message and I got a Microsoft page that addressed it. I was dubious at first, but I tried it out and now I rarely if ever gets any more errors. (When's the last time one of those Microsoft pages actually helped someone?) :D In short, it was some sort of fix where I went into the registry, changed some values and also reentering the SAME registry values over again! (why that worked I don't know).

Since it now works, I check it every so often and I create restore points so that if something gets corrupted in registry I can redo it without having to change anything.