Time error

[Jerry]

I have two computers hardwired through a router but not networked. One has
XP Pro/SP2 and the other has XP Home SP2 and both are fully updated except
both still have IE6. The patch for DST was applied before the time change
and all seemed to be working fine.

In the last few days I have noticed when both PCs are booted up in the
morning, the time is one hour ahead. Both are set to Eastern time as it
should be. When I tell windows to synchronize, I get the following error
message:

"An error occurred while windows was synchronizing with time.windows.com.
The time sample was rejected because: The peers's stratum is less than the
host' stratum."

I can set time manual and it will stay until the next morning, then it will
be one hour ahead again. The one hour is consistent in that if time is NOT
corrected, the next day it still be one hour ahead, NOT two hours.

I know this is a small thing, but is irritating to say the least. Any help
correcting this would be greatly appreciated.

Thank you.

 

[TaurArian [MS-MVP]]

Try another time server, had the same problem -

http://support.microsoft.com/kb/262680
A list of the Simple Network Time Protocol (SNTP) time servers that are available on the
Internet

Just type in the combo listbox.
No registry editing.

--

====================================
TaurArian [MS-MVP] 2005-2007 - Australia
====================================
How to make a good post: http://www.dts-l.org/goodpost.htm
Backup and data recovery: http://www.acronis.com.sg/
Enhancing file system performance: http://www.diskeeper.com/defrag.asp


|I have two computers hardwired through a router but not networked. One has
| XP Pro/SP2 and the other has XP Home SP2 and both are fully updated except
| both still have IE6. The patch for DST was applied before the time change
| and all seemed to be working fine.
|
| In the last few days I have noticed when both PCs are booted up in the
| morning, the time is one hour ahead. Both are set to Eastern time as it
| should be. When I tell windows to synchronize, I get the following error
| message:
|
| "An error occurred while windows was synchronizing with time.windows.com.
| The time sample was rejected because: The peers's stratum is less than the
| host' stratum."
|
| I can set time manual and it will stay until the next morning, then it will
| be one hour ahead again. The one hour is consistent in that if time is NOT
| corrected, the next day it still be one hour ahead, NOT two hours.
|
| I know this is a small thing, but is irritating to say the least. Any help
| correcting this would be greatly appreciated.
|
| Thank you.
|
|

 

[John John]

No need to post twice in less than 30 minutes, this is not a chat room!
It can take a few hours for someone in the know to read your post and
offer a suggestion. If the problem is a complicated one it can take a
day or more before someone knowledgeable answers.

The fix for your problem seems to be to change to a different time
server. Many have had this problem in the last few days and changing to
a different server has fixed it for them.

John

 

[Guest]

Jerry,

I've found that time.xmission.com works for me. It would be nice if someone
could come up with an explanation of why this is happening though.

Milt

 

[Jerry]

God I hate making changes in the registry LOL. Thanks for the info however.

 

[Guest]

Jerry,

There's no need to make a registry change to add another time server to your
list. Just click in the "Server:" window to hilight the existing entry, type
in the new entry and click apply. Your existing entry won't be deleted; the
new one will be added to the drop down list.

Milt

 

[Guest]

Try another time server, had the same problem -

TaurArian, as an MVP, do you have any contacts in the MS infrastructure
group? time.windows.com has been seriously messed up for several days now,
and MS customer service is telling me to open a PSS case about the issue,
which I don't want to do, because it will probably go nowhere.

Diagnostics:

C:\temp>w32tm /monitor /computers:time.windows.com,tick.usno.navy.mil
time.windows.com [207.46.232.182]:
ICMP: error IP_REQ_TIMED_OUT - no response in 1000ms
NTP: +110.9722635s offset from local clock
RefID: unspecified / unsynchronized [0.0.0.0]
tick.usno.navy.mil [192.5.41.40]:
ICMP: error IP_REQ_TIMED_OUT - no response in 1000ms
NTP: +0.0031452s offset from local clock
RefID: 'USNO' [85.83.78.79]

C:\temp>w32tm /monitor /computers:time.windows.com,tick.usno.navy.mil
time.windows.com [207.46.232.182]:
ICMP: error IP_REQ_TIMED_OUT - no response in 1000ms
NTP: +111.5480655s offset from local clock
RefID: unspecified / unsynchronized [0.0.0.0]
tick.usno.navy.mil [192.5.41.40]:
ICMP: error IP_REQ_TIMED_OUT - no response in 1000ms
NTP: +0.0570075s offset from local clock
RefID: 'USNO' [85.83.78.79]

C:\temp>ntpdate -q -d time.windows.com
11 Apr 10:39:22 ntpdate[3148]: ntpdate [email protected] Dec 11 20:58:13
(UTC+01:0
0) 2005 (3)
transmit(207.46.232.182)
receive(207.46.232.182)
transmit(207.46.232.182)
receive(207.46.232.182)
transmit(207.46.232.182)
receive(207.46.232.182)
transmit(207.46.232.182)
receive(207.46.232.182)
transmit(207.46.232.182)
207.46.232.182: Server dropped: strata too high
server 207.46.232.182, port 123
stratum 16, precision -6, leap 11, trust 000
refid [207.46.232.182], delay 0.11935, dispersion 0.00684
transmitted 4, in filter 4
reference time: c9899c8c.10000000 Fri, Feb 23 2007 11:02:04.062
originate timestamp: c9c7801b.10000000 Wed, Apr 11 2007 10:41:15.062
transmit timestamp: c9c77fab.71de428b Wed, Apr 11 2007 10:39:23.444
filter delay: 0.13498 0.13498 0.13498 0.11935
0.00000 0.00000 0.00000 0.00000
filter offset: 111.5708 111.5708 111.5708 111.5786
0.000000 0.000000 0.000000 0.000000
delay 0.11935, dispersion 0.00684
offset 111.578641

11 Apr 10:39:23 ntpdate[3148]: no server suitable for synchronization found

 

[Jerry]

Thank You Milt, it worked perfectly. After changing to time.xmission.com,
the clock updates without any error messages.