Thread: NOD32 + Windows automatic clock sync = Fail?

Whenever I have NOD32 enabled the windows clock can't check the internet to make sure it's up to date.
It also prevents 3rd party clock updaters like WebTime from connecting as well.
Is there some setting or something I have to change to get the clock working again?
It worked fine up until about a month ago and stopped shortly after an update to the virus database.

Originally Posted by The Doctor

Whenever I have NOD32 enabled the windows clock can't check the internet to make sure it's up to date.
It also prevents 3rd party clock updaters like WebTime from connecting as well.
Is there some setting or something I have to change to get the clock working again?
It worked fine up until about a month ago and stopped shortly after an update to the virus database.

the time needs to be within 12 hours of the right time.

Actually, what I meant is under the "Internet Time" tab (when you double click your clock) next to the server drop down box there is a button that says "Update Now" when clicked it would only say error connecting to (server name).

However I figured the problem out and it had nothing to do with NOD32.
The three servers you can choose from (comes by default) have been down off and on for about a month.
I put in one of the other servers from the NIST site and it's working fine now.

Also (unknown to me) WebTime uses the same servers and some other outdated servers by default.

Originally Posted by The Doctor

Actually, what I meant is under the "Internet Time" tab (when you double click your clock) next to the server drop down box there is a button that says "Update Now" when clicked it would only say error connecting to (server name).

However I figured the problem out and it had nothing to do with NOD32.
The three servers you can choose from (comes by default) have been down off and on for about a month.
I put in one of the other servers from the NIST site and it's working fine now.

Also (unknown to me) WebTime uses the same servers and some other outdated servers by default.

just use the microsoft one.
and be sure your time is within 12 hours of the correct time(day too)
I had this issue when I was trying to connect to Tor on this computer the first time.

The M$ one was not working either.
That is why I prefer using NIST servers or the US Naval Observatory Master Clock

Originally Posted by The Doctor

The M$ one was not working either.
That is why I prefer using NIST servers or the US Naval Observatory Master Clock

is your time and date set to as close as you can to your local time and is your time zome correct?

It's. working fine now that I stopped using the default servers.

Originally Posted by The Doctor

It's. working fine now that I stopped using the default servers.

ok. what server are you using now?

I'm currently using nist1-ny.ustiming.org
Here is the list of servers and their up/down status for those in the same boat as I was..