time.windows.com sync failure...

April 2, 2007 at 14:32:34
Specs: Windows XP SP2, Athlon 64 3200+ 2.0Ghz, 1
Is anyone having this problem and know how to fix it. I had already updated my OS via Windows Update, and I checked to see if firewall was causing the problem and it was not. "time.nist.gov" doesn't even work as well.

My time zone settings: (GMT -05:00) Eastern Time (US & Canada).

The error message I got when I turn on DST is...

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

"An error occurred while Windows was synchronizing with time.nist.gov."

The error message I got when I turn off DST is...

"Windows has never attempted to synchronize with an Internet server."


What really weird error messages!


See More: time.windows.com sync failure...

Report •


#1
April 2, 2007 at 17:35:23
yes i am. it says an error has occured while syncronizing with time.windows.com

Report •

#2
April 2, 2007 at 18:18:49
Me too

Interestingly, using a different app (Tclock2) synchronization was successful

I'm not one of those who think Bill Gates is the devil. I simply suspect that if Microsoft ever met up with the devil, it wouldn't need an interpreter.


Report •

#3
April 2, 2007 at 19:55:10
Had the same trouble yesterday. Found the solution here. http://www.onecomputerguy.com/windo...

Look for the heading "Adding Time Servers"
This will involve editing the registry. It will add more time servers to xp to the default two that are already there.
The ones I added are:

time-nw.nist.gov
note the hyphen and since I live in Alberta, Canada I also added these two:
ntp.cpsc.ucalgary.ca
ntp1.cpsc.ucalgary.ca

Works like a charm.



Report •

Related Solutions

#4
April 2, 2007 at 21:20:21
Directly, it's Adding Time Servers

Fine - but since I can synchronize using a different app, that indicates it's not a problem with the default time servers (hyphens be damned)

I'm not one of those who think Bill Gates is the devil. I simply suspect that if Microsoft ever met up with the devil, it wouldn't need an interpreter.


Report •

#5
April 3, 2007 at 05:35:09
This never happened before. It just recently I am seeing error messages show up when it starts to sync. I checked to make sure it wasn't some router-networking settings I changed and it wasn't the culprit (tried plugging the ethernet cable directly into the cable modem; it's not firewall either). Could this problem be with the time servers itself or one of the windows updates Microsoft had released?

Report •

#6
April 3, 2007 at 08:08:09
http://computing.net/windowsxp/wwwb...

Select a different server from it's drop down.

Bryan


Report •

#7
April 3, 2007 at 08:24:28
"Select a different server from it's drop down."
...? Well it looks like I would have already tried that. Still no luck. If you mean a totally different time server other than the two default ones, then I'll probably check into that (although I want to make the default ones work; why didn't Microsoft informed us about this issue?)

"Interestingly, using a different app (Tclock2) synchronization was successful"
Why I am forced to use a different app, just to make the time synchronize? I am just curious, that's all : )

"This will involve editing the registry."
Well I want to make the default time servers work properly before I do any of those complicated and risky stuff. : /


* I think I may have to uninstall the DST patch or contact Microsoft.


Report •

#8
April 3, 2007 at 15:31:23
"Why I am forced to use a different app"

'Forcing'? - that information was provided to illustrate that the problem doesn't appear to be with the default servers - - mind you (imo) it's superior to the Windows one

I'm not one of those who think Bill Gates is the devil. I simply suspect that if Microsoft ever met up with the devil, it wouldn't need an interpreter.


Report •

#9
April 4, 2007 at 03:38:17
When I open the clock and go to Internet Time tab I find 9 different servers listed. I do not know why you would find less.

Bryan


Report •

#10
April 4, 2007 at 09:17:41
What the hell did Microsoft do to our computers now? Well it's weird that I didn't have the problem before, so I guess I have to try uninstalling the DST patch to make the default time servers work or use Tclock2. http://support.microsoft.com/gp/cp_dst

Thanks Bryco, I tried one of the time servers here and it did the trick: http://tf.nist.gov/service/time-ser... And I didn't had to enter anything into the registry, just typed it in the combo listbox and it worked.


Report •

#11
April 4, 2007 at 11:53:51
Doubt it has anything to do with the DST patch. According to my event log synchronization was successful on March 17th & 24th. The first failure appears on this week’s synchronization attempt.

Report •

#12
April 8, 2007 at 17:18:08
Melody’sTip: Hey guys, I read all your suggestions. I found a much simplier solution by reading a combination of your solutions:
1)ctrl copy time-nw.nist.gov link suggested by trek1701A and rt click time found low right corner in start bar and in paste into date and time properties> internet time dropbox > apply > update now
This worked to fix:
"An error occurred while Windows was synchronizing with time.windows.com. The time sample was rejected because the peer's stratum is less than the host's stratum."

OR (2) link to http://tf.nist.gov/service/time-ser... suggested by trashmaster
and select your own time server > ctrl copy .... and paste directly into time date dropbox ..update


Report •

#13
April 10, 2007 at 07:43:08
Im having another with the clock time!

It keep reseting the year to 1970 or 2070 for some reason, AVG and Avast! can't find no virus, and AdAware can't find spywares...

What should I do?


Report •

#14
April 10, 2007 at 10:40:41
Kage,

You will want to start a new thread for your issue.
You may want to refer to this post in your new posting.

Regards,
Bryan


Report •

#15
April 14, 2007 at 13:04:58
Has anyone identified the root cause and solution for the issue with time.windows.com?? It's all fine and good to have workarounds like using other servers, but it would be more appropriate to actually fix the problem as the underlying problem could begin appearing with additional servers. I can't find anything on Microsoft's own knowledgebase either.

The path to Hell begins with Microsoft.


Report •

#16
April 16, 2007 at 03:23:11
The problem would be with the server.
Nothing to fix from our end.

If and when that server is brought back online then we could return to using that server.

In the mean time there are plenty of others to choose from.

HTH
Bryan


Report •

#17
April 17, 2007 at 12:15:21
Word has it that MS couldn't fix time.windows.com in time for the recent DST changes so they just shut it down and hoped no-one would notice.

Right.



Report •

#18
April 18, 2007 at 04:15:47
RDA is correct simplest solution.

Click on the clock go to internest time and type the following over the top of whatever server you have

130.149.17.8 (if you're in europe)
132.163.4.102 (if your in north america)

click update it should synch then click apply.

dont mess about with your registry to add new ones to the drop down list.


Report •

#19
June 21, 2007 at 00:33:43
John Bloomfields solution works for me just copy and paste the address in the server drop down list.

130.149.17.8 (if you're in europe)
132.163.4.102 (if your in north america)

Updated no problem, cheers John all sorted.



Report •

#20
July 21, 2007 at 19:19:48
time.windows.com worked for me after I set the date correctly. If the date on your computer is wrong then it won't work.

Report •


Ask Question