View Single Post
Old October 31st 09, 02:35 AM posted to,microsoft.public.windowsxp.help_and_support
external usenet poster
Posts: 10
Default Time Stamp problem on Incoming and Outgoing emails

Thanks to all who responded. Much of what [email protected] has written is so far
over my head he'd better have a pilots license.
Ill finish off the thread tomorrow letting everyone know whether the problem
has been solved by Updates or whether it was an ISP issue.

"VanguardLH" wrote in message
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
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
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)
that the 'Automatically synchronize with an Internet time server' does
work properly once Update Now button is hit. With I get
following message ' An error occurred while windows was synchronizing
with The time sample was rejected because : The peer's
is less than the host's stratum. With, when it's
successful, I
get the wrong time displayed even when the message states the correct
(The time has been successfully synchronized with ... ).

I'm in the EST time zone (Toronto, Canada).

Any help would be appreciated, thanks in advance.

If you visit 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 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). NIST is more
reliable than Microsoft. Also remember that the Windows Time service in
Windows may not sync your computer for *many* days which means you could
drift quite aways in your time (computer clocks are not very accurate;
well, the hardware clock is okay for a month but that doesn't get used
under an OS and processes generating heavy loads on the host can
generate a lot of drift in the OS-managed clock). I'm not sure that
those are the only 2 NTP servers that Windows will use. On occasion
when looking at the Internet Time tab of the Date and Time applet, I've
seen it mention the time sync was with, a worldwide mesh of
voluntary NTP servers (see You
can add more servers to the list by a registry edit at:

HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Dat eTime\Servers

Yet I know that you can set the NTP server using the command line, like:

net time /

See I use the US pool of NTP servers. You
might want to use the Canadian one ( Using a country
zone for their pool of NTP servers ensures a shorter delay but which one
to which you connect in the pool is random (the list changes every

Yet specifying that NTP pooled server using the "net time" command won't
have it show up in the above registry key (so it isn't available in the
drop-down list in the Internet Time tab in the Date and Time applet).
Instead that value shows up as the NtpServer data item at:

HKLM\SYSTEM\ControlSet001\Services\W32Time\Paramet ers

However, you can add to the list by adding
another data item (next higher numbered) in the above Servers registry
key to see it in the drop-down list (and then make it the default in the
Internet Time tab in the Date and Time applet).

A Google search can find NTP servers in your area (although that does
not guarantee a minimal delay). I use Socke****ch (not free) but there
are other time sync utilities that can poll a list of NTP servers. Some
will even try to determine which ones have the least delay to give you
the most accurate time sync over a network. Although I have my nearby
university's NTP servers in the list that Socke****ch uses, often the
delay to NTP servers a state or two away is shorter and better
candidates for a time sync. Make sure it is a *public* NTP server to
which you are allowed connect.