Synchronizing WinXP Clock

[Guest]

I am unable to successfully synchronize my internal clock with any available
standard time sources. I downloaded Socket Watch to see if it could work
around the problem (it couldn't). I know that both WinXP clock and Socket
Watch are polling the outside standard sources, but they both show a failure
to reset my clock. I'm wondering if they are being denied permission to
communicate with the clock. I'm running WinXP Media Center on a wireless
network that seems to be performing well. I believe that my problem started
when I ran the Network Setup Wizard to try to get my laptop to communicate
with my desk top machine. Have I made a mistake that effects these programs
ability to communicate with the clock?

 

[Brian A.]

I am unable to successfully synchronize my internal clock with any available
standard time sources. I downloaded Socket Watch to see if it could work
around the problem (it couldn't). I know that both WinXP clock and Socket
Watch are polling the outside standard sources, but they both show a failure
to reset my clock. I'm wondering if they are being denied permission to
communicate with the clock. I'm running WinXP Media Center on a wireless
network that seems to be performing well. I believe that my problem started
when I ran the Network Setup Wizard to try to get my laptop to communicate
with my desk top machine. Have I made a mistake that effects these programs
ability to communicate with the clock?

From what I understand is if you use a third party time synchronization app you
must disable the windows time sync.

First see if one of these sites can sync the time:
http://tf.nist.gov/service/time-servers.html

If not check your firewall to make sure they are not blocked, or you can add them
to the trusted zone of the firewall.

--

Brian A. Sesko { MS MVP_Shell/User }
Conflicts start where information lacks.
http://basconotw.mvps.org/

Suggested posting do's/don'ts: http://www.dts-l.org/goodpost.htm
How to ask a question: http://support.microsoft.com/kb/555375

 

[Val]

I never disable Windows time service, but often use the nistime-32bit.exe
you can download from here:
http://tf.nist.gov/timefreq/service/its.htm

It has built in access to more time servers than Windows does.

Val

 

[Ron Hardin]

My clocks stopped updating when I added zone alarm firewall. The NBS
site needs to be able to get at something like svchost.exe (I may
have the wrong name). It started working again when I set the NBS
site to trusted, which is sort of a hack solution, it seems to me.

 

[Brian A.]

I never disable Windows time service, but often use the nistime-32bit.exe you can
download from here:
http://tf.nist.gov/timefreq/service/its.htm

It has built in access to more time servers than Windows does.

Why bother installing something when you don't have to?
I get it straight from the source: time-a.nist.gov


--

Brian A. Sesko { MS MVP_Shell/User }
Conflicts start where information lacks.
http://basconotw.mvps.org/

Suggested posting do's/don'ts: http://www.dts-l.org/goodpost.htm
How to ask a question: http://support.microsoft.com/kb/555375

 

[Val]

Because frequently I get "An error occured......" from Windows time update.

nistime program, hitting the same server, works almost 100% of the time.

Val

 

[Brian A.]

Because frequently I get "An error occured......" from Windows time update.

nistime program, hitting the same server, works almost 100% of the time.

Almost to me = errors as well.

You do not need the nistime program, simply:
Open Date and Time Properties > Internet Time tab.
Add "time-a.nist.gov" w/o quotes into the dropdown box.
Click Apply > Update Now.
Once syncronized click Ok.

I've never had problems using it.

Another way would be to add the IP address instead (129.6.15.28) to cut out one
process. When using a url it has to be converted to the IP before it can process the
task, using the IP cuts out the conversion process. The time syncronization works
with either a url or IP.

Then again, it's your choice as to what you prefer to use.


--

Brian A. Sesko { MS MVP_Shell/User }
Conflicts start where information lacks.
http://basconotw.mvps.org/

Suggested posting do's/don'ts: http://www.dts-l.org/goodpost.htm
How to ask a question: http://support.microsoft.com/kb/555375

 

[Guest]

Neither the WinXP clock synchronizing utility nor Socket Watch can reset the
clock. I didn't download Socket Watch until I was sure that the Win XP
utility could not reset the clock. Even with the WinXP firewall disabled and
the McAfee firewall set to accept socket watch, neither the WinXP utility nor
socket watch are successful. I'm still wondering if something hasn't been
inadvertently reset and is blocking attempts to access the computer.

 

[Guest]

This issue is resolved, although I don't know how I did it. While I was
working trying to get my home network functioning, I noticed that Socket
Watch had synchronized with its national time servers. I opened the WinXP
Date and Time utility and found that it, too, had synchronized my internal
clock. I suspect that this has something to do with my changing a setting
that gives permission to communicate with my desktop machine.