Time Servers

[Cheemag]

Hello,


All of a sudden all but two of the time-servers in my WebTime 2000 gadget have ceased to return any results other than mostly socket errors.


I have changed nothing and I'm rather reluctant to believe that all the world's time machines have changed their systems in some way.


Only Gaithersburg, MD and Uni Colorado, Boulder return the time now.


Puzzled.

 

[file3456]

I have found a great majority of the Windows 7 gadgets don't work anymore. And I read M$ doesn't use them anymore as they can be a security risk.

 

[Cheemag]

I have found a great majority of the Windows 7 gadgets don't work anymore. And I read M$ doesn't use them anymore as they can be a security risk.

Sorry, I meant 'gadget' as a general term. The 'gadget' is an installed programme called WebTime.
This has worked for decades, but suddenly stopped working with the majority of time-servers.


Regards


Cheemag

 

[samuria]

Set your DNS to 1.1.1.1 & 1.0.0.1 see if that solves it

 

[Cheemag]

Set your DNS to 1.1.1.1 & 1.0.0.1 see if that solves it

Thanks for your reply.


Should that be in Windows or in the router ?


I'll have a go.

 

[samuria]

It's a very fast DNS set in Windows and router

 

[file3456]

Those DNS servers are Google. You can also check out OpenDNS which allows content filtering.

 

[Cheemag]

Those DNS servers are Google. You can also check out OpenDNS which allows content filtering.

Yikes !! So they'll be spying on every request I put in and no doubt tracking as well.


I'll change them back to 208.67.222.222 and 208.67.220.220 as they were before.



It made no difference anyway, most time servers are still returning errors.


Thanks for the warning about Google.

 

[samuria]

The dns isnt Google please check facts before posting

 

[file3456]

Yeah, I just noticed that. 1.1.1.1 is CloudFlare. Many people recommend 8.8.8.8 which IS Google.

 

[file3456]

Yikes !! So they'll be spying on every request I put in and no doubt tracking as well.


I'll change them back to 208.67.222.222 and 208.67.220.220 as they were before.



It made no difference anyway, most time servers are still returning errors.


Thanks for the warning about Google.

So this is a program or the computer's time?

 

[Cheemag]

The dns isnt Google please check facts before posting

Simpilot said they were - perhaps mistakenly. 1.1.1.1 is Cloudflare

 

[Cheemag]

Yeah, I just noticed that. 1.1.1.1 is CloudFlare. Many people recommend 8.8.8.8 which IS Google.

No problem. Thanks for the DNS suggestion. Didn't solve the problem, but thanks anyway.

 

[file3456]

You didn't answer my question in post #11.

 

[Cheemag]

So this is a program or the computer's time?

It's a programme not the computer's time setting.


Webtime 2000 by Gregory Braun: Software Design - WebTime for Windows by Gregory Braun


Useful for a quick check on whether you have the Internet (or not).

 

[file3456]

On that webpage is an email contact. You might want to try there. I'm not sure what the issue is. Is there a setting to change the time server by chance?

 

[Cheemag]

On that webpage is an email contact. You might want to try there. I'm not sure what the issue is. Is there a setting to change the time server by chance?

I've Emailed the help page when this first became evident, but so far no reply.


There is a choice of eighteen timeservers, but only Gaithersburg and Univ Colorado work now, the
others usually return a socket error.

 

[file3456]

Take those addresses and ping them.

Open command prompt and type

ping [the address here]

without brackets.

So, like, ping time.nist.gov

If the ping fails then their server is offline.

 

[file3456]

Although, this is not always the case. Some servers prevent pings for security reasons or they limit pings. But with time servers it shouldn't be an issue.

 

[Cheemag]

Pings return timeouts on the subject servers.


With this WebTime app on three computers Win7/Win7/Win8.1 all the servers fail except two. So it's not the OSs.



Kaspersky Internet Security on all three. Disabling it makes no difference, so it's not the firewall.


That leaves the app. Could hardly be the time servers, unless they've all changed something fundamental in the last week or so