Time Syncronization Consistently Fails

[BarneyB]

Hi All,

My XP Pro machine's fail to sync with time servers, and it does not matter
which time servers I choose.

I have tried netstop w32time, intending to unregister and then re register
the service, but at the ntstop w32time command I get

System error 5 has occurred.

Access is denied.

I will be very grateful for any help you knowledgeable folk can offer to me.

Thanks,

 

[Unknown]

Try server 'tick.usno.navy.mil'

 

[BarneyB]

Thanks, but I have tried that one among other time servers. Any other ideas?

 

[Jose]

Hi All,

My XP Pro machine's fail to sync with time servers, and it does not matter
which time servers I choose.

I have tried netstop w32time, intending to unregister and then re register
the service, but at the ntstop w32time command I get

System error 5 has occurred.

Access is denied.

I will be very grateful for any help you knowledgeable folk can offer to me.

Thanks,

Which of the Google search result have you tried?

Does your XP login have Administrator rights?

Are you using a 3d party firewall?

 

[M.I.5¾]

Hi All,

My XP Pro machine's fail to sync with time servers, and it does not matter
which time servers I choose.

I have tried netstop w32time, intending to unregister and then re register
the service, but at the ntstop w32time command I get

System error 5 has occurred.

Access is denied.

I will be very grateful for any help you knowledgeable folk can offer to
me.

Just you and several million others have this problem at present.
Apparently, the time servers have altered their software so as to detect and
reject denial of dervice attacks. It seems that the way in which windows
interrogates those servers to obtain the current time is interpreted as such
a denial of service attack as Windows makes several interrogations before
correcting the CMOS clock. It further appears that the repetition rate is
somewhat marginal as quite a few people have managed to get their PC to work
with a small handful of time servers.

About the only thing that you can check is that your chosen time server site
is not blocked by your firewall, and that access to port 135 is similarly
not blocked. They probably aren't and like the rest of us, you will have to
await a solution (which may be in the form of an update from MS).

 

[Jose]

Just you and several million others have this problem at present.
Apparently, the time servers have altered their software so as to detect and
reject denial of dervice attacks.  It seems that the way in which windows
interrogates those servers to obtain the current time is interpreted as such
a denial of service attack as Windows makes several interrogations before
correcting the CMOS clock.  It further appears that the repetition rateis
somewhat marginal as quite a few people have managed to get their PC to work
with a small handful of time servers.

About the only thing that you can check is that your chosen time server site
is not blocked by your firewall, and that access to port 135 is similarly
not blocked.  They probably aren't and like the rest of us, you will have to
await a solution (which may be in the form of an update from MS).

Where is this information about the altered time server software?

Which time server are you using?

nist and windows work fine for me.

 

[BarneyB]

I booted my machine today and without changing anything it has syncronized to
time.nist.gov, its not been syncing for weeks so I dont know what has
changed, but it seems sorted, Thanks guys

 

[M.I.5¾]

Just you and several million others have this problem at present.
Apparently, the time servers have altered their software so as to detect
and
reject denial of dervice attacks. It seems that the way in which windows
interrogates those servers to obtain the current time is interpreted as
such
a denial of service attack as Windows makes several interrogations before
correcting the CMOS clock. It further appears that the repetition rate is
somewhat marginal as quite a few people have managed to get their PC to
work
with a small handful of time servers.

About the only thing that you can check is that your chosen time server
site
is not blocked by your firewall, and that access to port 135 is similarly
not blocked. They probably aren't and like the rest of us, you will have
to
await a solution (which may be in the form of an update from MS).

Where is this information about the altered time server software?

Which time server are you using?

nist and windows work fine for me.

------------

Quite a number of other Windows forums have carried the information. I
personally can't get any time server to work using my Desktop (Core 2 quad)
or my laptop (Core 2 Duo). However, my other half's PC seems to syncronise
without problem to most (but not all) servers. But as it uses an old
Pentium 4 processor, it's probably so slow that the time servers are happy.

None of the newer PCs in the office will synchronise.