Clock Update Error Still Exists!

[deputylynch]

My clock will not update either manually or automatically from any of the
internet time sites!

Whenever I try it maually all I get is an error occurred while Windows was
synchronizing with (what ever time server I tried)


I turned off all Firewall Protection and still it won't update!

I can ping the time.nist.gov site but not the time.windows.com

I can disable the windows and mcafee together or seperatley and it still
will not work!

Even though I can ping the nist site I still get the same error message!

My 123 port is open!

Please help!

 

[Nonny]

I still need help with this problem, I turn off all firewalls and can
ping the sites but clock will not update!

PLEASE HELP!

http://tf.nist.gov/service/its.htm

On the right, you will find some downloads.

Download the top one and run it.

 

[Nonny]

Could not find anything there to help!
I can ping a bunch of different servers but the clock will not update!

I think you need to do some reading:

Click the start orb

Select Help and Support

Type in CLOCK

Read the top item (set the clock) in its entirety.

 

[Ronc]

I'm not sure if your problem is the same as mine, so I'll describe mine:

First of all I've been using PC's for 12+ years (98 and Vista) and
throughout most of that time I've managed to get the clock to sync to a GOOD
time server automatically as often as I want. I have a T1 network provided
by Covad through the modem/router they supply. My year-old Vista Ultimate
computer includes Ethernet as well as Sprint and WiFi for portable use. I
was happy to see
Windows Time built-in and thought that it's so nice that I would not have to
use a 3rd party program, like NISTIME as I did on Win98. After typing in a
known good time server in the server box and adjusting the special poll
interval in the registry, I found that the Windows time client syncs fine
in portable mode (using WiFi hotspots or Sprint WWAN) but not via my
T1-Ethernet
jack. I, as you, thought it might be a firewall thing so I turned off both
the router's firewall and Vista's firewall as a test which made no
difference. (I didn't really expect it to make a difference since I had
previously made sure that for TCP and UDP, port 123 was open on both the
input and
output filters on both Vista and the router.) I finally gave up and
installed
NISTIME on Vista so that
it now syncs on Ethernet just like my Win98 computers. Also, I've tried
plugging in a friend's Mac which also syncs fine. At this point I've
narrowed down the problem to these possibilities (both of which seem
absurd):

1)Covad's network blocks Windows Time client but let's others through.

2)The Ethernet jack (on the Vista machine) is incompatible with Vista's
Windows Time client, but compatible with NISTIME.

In order to narrow things down further I'd have to purchase or gain access
to
something I don't currently have (like a different internet source for my
Ethernet jack, a different Vista computer, or a WiFi access point sourced
from Covad). I did confirm that my computer manufacturer was able to
duplicate the problem on their own set up (i.e. works on wireless but
not on the Ethernet jack) but they have no solution yet. I doubt if they
are even working on the problem since it can be worked around via another
time client.

Does anyone else have a similar problem (syncs on WWAN or WiFi hotspots but
not on wired Ethernet)?

 

[Charlie Tame]

Pinging them will NOT update your clock.

Reading comprehension problems again? He never expected it to set the clock.

 

[Charlie Tame]

I think you need to do some reading:

Click the start orb

Select Help and Support

Type in CLOCK

Read the top item (set the clock) in its entirety.

FYI

http://en.wikipedia.org/wiki/Ping

 

[Charlie Tame]

Answering both of you I guess...

Well I have seen the server time.windows.com inoperative several times,
so I would try substituting that for another server. Make sure the
router allows port 123 both ways for both protocols and that the
checkbox next to the entry (if there) is also checked. Linsys for
example allow you to enter a rule but you also have a checkbox and if
you forget to check it the rule stays dormant.

Either wireless or wired has worked fine for me in the past (except for
the above instances where the server temporarily didn't seem to be up)
but I have not used wireless for several months so do not know about the
present.

 

[Ronc]

As I said (although in somewhat different words):

Yes, 123 both ways for both protocols and for both firewalls (Vista and
Router). In addition, I turned off both firewalls just to prove it is NOT a
firewall
issue.

Regarding the server, yes it is a "GOOD" server. By good, I mean it works
on all computers using the NISTIME client including the Vista computer on
which Windows time will not sync over Ethernet but does sync over wireless.
(No it's definitely not time.windows.com which as you say has been
unreliable.) In other words, I've proven it's NOT a bad server issue.

This is why, hard as it may be to believe I'm left with two possibilities:

1)Covad's network blocks Windows Time client but let's others through.

2)The Ethernet jack (on the Vista machine) is incompatible with Vista's
Windows Time client, but compatible with NISTIME on the same Vista computer.

Answering both of you I guess...

Well I have seen the server time.windows.com inoperative several times, so
I would try substituting that for another server. Make sure the router
allows port 123 both ways for both protocols and that the checkbox next to
the entry (if there) is also checked. Linsys for example allow you to
enter a rule but you also have a checkbox and if you forget to check it
the rule stays dormant.

Either wireless or wired has worked fine for me in the past (except for
the above instances where the server temporarily didn't seem to be up) but
I have not used wireless for several months so do not know about the
present.