VanguardLH wrote:
Brad wrote:
For some reason the Timestamp on my emails is off by one hour. When I
receive an email at 9am for example, it appears in my Inbox as 8am.A
similar
but opposite problem appears on my emails received by my friends ... they
are showing it as being received one hour later.
My clock shows the correct Time and Time Zone, with and without box
checked
for 'Automatically adjust clock for daylight saving changes'. The problem
was first noticed with the box checked.
One problem within the Date and Time Properties option (in Control Panel)
is
that the 'Automatically synchronize with an Internet time server' does
not
work properly once Update Now button is hit. With time.windows.com I get
the
following message ' 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. With time.nist.com, when it's
successful, I
get the wrong time displayed even when the message states the correct
time
(The time has been successfully synchronized with time.nist.gov ... ).
I'm in the EST time zone (Toronto, Canada).
Any help would be appreciated, thanks in advance.
If you visit http://www.timeanddate.com/worldclock/ and pick a city in
your timezone (Toronto, in your case), does the time on your computer
match with theirs? If not, you need to fix the timezone or DST setting
on your computer. If yes, inquire at cogeco.net as to why their clock
is off by an hour.
From the headers in your post (spaces added to align values in fixed
font display):
NNTP-Posting-Date: Fri, 30 Oct 2009 16:01:10 UTC
Date: Fri, 30 Oct 2009 12:01:05 -0500
The Date header is what you added (assuming it didn't get overwritten).
The NNTP-Post-Date was added by your newsgroups service provider (NSP).
Removing the timezone bias means the times for those headers a
NNTP-Posting-Date: Fri, 30 Oct 2009 16:01:10 GMT
Date: Fri, 30 Oct 2009 17:01:05 GMT
So you are your NSP are different by 1 hour. Contact your NSP.
Microsoft's NTP servers are not reliable because they are overly busy
(and haven't been updated to handle the load). That means you get lots
of timeouts trying to connect to their time server. Use a different NTP
server. The defaults that the Windows install give you are limited to
just the Microsoft and NIST servers and both are heavy accessed (i.e.,
they're very busy so you might not get a time sync).
It seems the "time.windows.com" one for the last week has had some problems.
I don't know if it's working now or not (without constant timeouts), since I
gave up on it for now. Wonder what happened in just the last week to
create this problem? It had been "fairly reliable" up to then.
I use Dimension 4 for the time sync. I don't remember if it was free or
not at this point.