Vista: local clock & time sync problems

I have had Vista on a new machine for a while. All of a sudden, it's started losing hours per day. I can reset the time/date, but soon it's way behind again.

I've tried to use the internet time sync. Often I get an error, occasionally it succeeds. Rebooting seems to help sometimes.

Ideas?

-- Bill
LVL 1
BlearyEyeAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

briancassinCommented:
I just noticed you posted a seperate question regarding your wireless router. If you are having reliability and connectivity issues with that then there will be problems with the time sync.

Have you checked your event logs to see what is reported ? Go to the start run command and type eventvwr then look under application and system for errors you will probably see a W32 time error please post that message up here.

Also what are you currently using for a time sync source ? as this may be an issue if it is not 24/7 available.

Is this computer new or older, you will also want to check the BIOS to make sure that the time it set correctly there if not then that needs to be resolved also if the BIOS clock keeps getting off time then you have a bad cmos battery and you will need to replace it.

IS this computer wired or wireless ?
0
BlearyEyeAuthor Commented:
I'm not having serious connectivity issues. Even if the wireless is acting weird, I can get thru on Ethernet.

Event logs are below.

I've tried various time sync sources.

Relatively new computer. Will check bios time & respond separately.

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

From event viewer, there were 67 events, given below.

Log Name:      System
Source:        Microsoft-Windows-Time-Service
Date:          2/12/2008 8:32:34 AM
Event ID:      35
Task Category: None
Level:         Information
Keywords:      Classic
User:          N/A
Computer:      xps-m1330-leal
Description:
The time service is now synchronizing the system time with the time source pool.ntp.org,0x9 (ntp.m|0x9|0.0.0.0:123->64.25.87.54:123).
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Microsoft-Windows-Time-Service" Guid="{06EDCFEB-0FD0-4E53-ACCA-A6F8BBF81BCB}" EventSourceName="W32Time" />
    <EventID Qualifiers="16986">35</EventID>
    <Version>0</Version>
    <Level>4</Level>
    <Task>0</Task>
    <Opcode>0</Opcode>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2008-02-12T14:32:34.000Z" />
    <EventRecordID>16120</EventRecordID>
    <Correlation />
    <Execution ProcessID="0" ThreadID="0" />
    <Channel>System</Channel>
    <Computer>xps-m1330-leal</Computer>
    <Security />
  </System>
  <EventData Name="MSG_TIME_SOURCE_CHOSEN">
    <Data Name="TimeSource">pool.ntp.org,0x9 (ntp.m|0x9|0.0.0.0:123-&gt;64.25.87.54:123)</Data>
  </EventData>
</Event>

Log Name:      System
Source:        Microsoft-Windows-Time-Service
Date:          2/12/2008 8:32:34 AM
Event ID:      52
Task Category: None
Level:         Warning
Keywords:      Classic
User:          N/A
Computer:      xps-m1330-leal
Description:
The time service has set the time with offset 48577 seconds.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Microsoft-Windows-Time-Service" Guid="{06EDCFEB-0FD0-4E53-ACCA-A6F8BBF81BCB}" EventSourceName="W32Time" />
    <EventID Qualifiers="33370">52</EventID>
    <Version>0</Version>
    <Level>3</Level>
    <Task>0</Task>
    <Opcode>0</Opcode>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2008-02-12T14:32:34.000Z" />
    <EventRecordID>16119</EventRecordID>
    <Correlation />
    <Execution ProcessID="0" ThreadID="0" />
    <Channel>System</Channel>
    <Computer>xps-m1330-leal</Computer>
    <Security />
  </System>
  <EventData Name="MSG_TIME_JUMP_AUDIT">
    <Data Name="TimeOffsetSeconds">48577</Data>
  </EventData>
</Event>

Log Name:      System
Source:        Microsoft-Windows-Time-Service
Date:          2/11/2008 7:02:57 PM
Event ID:      37
Task Category: None
Level:         Information
Keywords:      Classic
User:          N/A
Computer:      xps-m1330-leal
Description:
The time provider NtpClient is currently receiving valid time data from pool.ntp.org,0x9 (ntp.m|0x9|0.0.0.0:123->64.25.87.54:123).
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Microsoft-Windows-Time-Service" Guid="{06EDCFEB-0FD0-4E53-ACCA-A6F8BBF81BCB}" EventSourceName="W32Time" />
    <EventID Qualifiers="16986">37</EventID>
    <Version>0</Version>
    <Level>4</Level>
    <Task>0</Task>
    <Opcode>0</Opcode>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2008-02-12T01:02:57.000Z" />
    <EventRecordID>16118</EventRecordID>
    <Correlation />
    <Execution ProcessID="0" ThreadID="0" />
    <Channel>System</Channel>
    <Computer>xps-m1330-leal</Computer>
    <Security />
  </System>
  <EventData Name="MSG_TIME_SOURCE_REACHABLE">
    <Data Name="TimeSource">pool.ntp.org,0x9 (ntp.m|0x9|0.0.0.0:123-&gt;64.25.87.54:123)</Data>
  </EventData>
</Event>

Log Name:      System
Source:        Microsoft-Windows-Time-Service
Date:          2/11/2008 6:33:42 PM
Event ID:      134
Task Category: None
Level:         Warning
Keywords:      Classic
User:          N/A
Computer:      xps-m1330-leal
Description:
NtpClient was unable to set a manual peer to use as a time source because of DNS resolution error on 'time.nist.gov,0x9'. NtpClient will try again in 15 minutes and double the reattempt interval thereafter. The error was: No such host is known. (0x80072AF9)
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Microsoft-Windows-Time-Service" Guid="{06EDCFEB-0FD0-4E53-ACCA-A6F8BBF81BCB}" EventSourceName="W32Time" />
    <EventID Qualifiers="33370">134</EventID>
    <Version>0</Version>
    <Level>3</Level>
    <Task>0</Task>
    <Opcode>0</Opcode>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2008-02-12T00:33:42.000Z" />
    <EventRecordID>15959</EventRecordID>
    <Correlation />
    <Execution ProcessID="0" ThreadID="0" />
    <Channel>System</Channel>
    <Computer>xps-m1330-leal</Computer>
    <Security />
  </System>
  <EventData Name="MSG_MANUAL_PEER_DNS_ERROR">
    <Data Name="ErrorMessage">No such host is known. (0x80072AF9)</Data>
    <Data Name="RetryMinutes">15</Data>
    <Data Name="DomainPeer">time.nist.gov,0x9</Data>
  </EventData>
</Event>

Log Name:      System
Source:        Microsoft-Windows-Time-Service
Date:          2/11/2008 6:33:41 PM
Event ID:      134
Task Category: None
Level:         Warning
Keywords:      Classic
User:          N/A
Computer:      xps-m1330-leal
Description:
NtpClient was unable to set a manual peer to use as a time source because of DNS resolution error on 'time.nist.gov,0x9'. NtpClient will try again in 15 minutes and double the reattempt interval thereafter. The error was: No such host is known. (0x80072AF9)
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Microsoft-Windows-Time-Service" Guid="{06EDCFEB-0FD0-4E53-ACCA-A6F8BBF81BCB}" EventSourceName="W32Time" />
    <EventID Qualifiers="33370">134</EventID>
    <Version>0</Version>
    <Level>3</Level>
    <Task>0</Task>
    <Opcode>0</Opcode>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2008-02-12T00:33:41.000Z" />
    <EventRecordID>15957</EventRecordID>
    <Correlation />
    <Execution ProcessID="0" ThreadID="0" />
    <Channel>System</Channel>
    <Computer>xps-m1330-leal</Computer>
    <Security />
  </System>
  <EventData Name="MSG_MANUAL_PEER_DNS_ERROR">
    <Data Name="ErrorMessage">No such host is known. (0x80072AF9)</Data>
    <Data Name="RetryMinutes">15</Data>
    <Data Name="DomainPeer">time.nist.gov,0x9</Data>
  </EventData>
</Event>

Log Name:      System
Source:        Microsoft-Windows-Time-Service
Date:          2/11/2008 6:32:28 PM
Event ID:      134
Task Category: None
Level:         Warning
Keywords:      Classic
User:          N/A
Computer:      xps-m1330-leal
Description:
NtpClient was unable to set a manual peer to use as a time source because of DNS resolution error on 'time.nist.gov,0x9'. NtpClient will try again in 15 minutes and double the reattempt interval thereafter. The error was: No such host is known. (0x80072AF9)
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Microsoft-Windows-Time-Service" Guid="{06EDCFEB-0FD0-4E53-ACCA-A6F8BBF81BCB}" EventSourceName="W32Time" />
    <EventID Qualifiers="33370">134</EventID>
    <Version>0</Version>
    <Level>3</Level>
    <Task>0</Task>
    <Opcode>0</Opcode>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2008-02-12T00:32:28.000Z" />
    <EventRecordID>15946</EventRecordID>
    <Correlation />
    <Execution ProcessID="0" ThreadID="0" />
    <Channel>System</Channel>
    <Computer>xps-m1330-leal</Computer>
    <Security />
  </System>
  <EventData Name="MSG_MANUAL_PEER_DNS_ERROR">
    <Data Name="ErrorMessage">No such host is known. (0x80072AF9)</Data>
    <Data Name="RetryMinutes">15</Data>
    <Data Name="DomainPeer">time.nist.gov,0x9</Data>
  </EventData>
</Event>

Log Name:      System
Source:        Microsoft-Windows-Time-Service
Date:          2/11/2008 6:31:03 PM
Event ID:      134
Task Category: None
Level:         Warning
Keywords:      Classic
User:          N/A
Computer:      xps-m1330-leal
Description:
NtpClient was unable to set a manual peer to use as a time source because of DNS resolution error on 'time.nist.gov,0x9'. NtpClient will try again in 15 minutes and double the reattempt interval thereafter. The error was: No such host is known. (0x80072AF9)
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Microsoft-Windows-Time-Service" Guid="{06EDCFEB-0FD0-4E53-ACCA-A6F8BBF81BCB}" EventSourceName="W32Time" />
    <EventID Qualifiers="33370">134</EventID>
    <Version>0</Version>
    <Level>3</Level>
    <Task>0</Task>
    <Opcode>0</Opcode>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2008-02-12T00:31:03.000Z" />
    <EventRecordID>15935</EventRecordID>
    <Correlation />
    <Execution ProcessID="0" ThreadID="0" />
    <Channel>System</Channel>
    <Computer>xps-m1330-leal</Computer>
    <Security />
  </System>
  <EventData Name="MSG_MANUAL_PEER_DNS_ERROR">
    <Data Name="ErrorMessage">No such host is known. (0x80072AF9)</Data>
    <Data Name="RetryMinutes">15</Data>
    <Data Name="DomainPeer">time.nist.gov,0x9</Data>
  </EventData>
</Event>

Log Name:      System
Source:        Microsoft-Windows-Time-Service
Date:          2/11/2008 6:30:31 PM
Event ID:      134
Task Category: None
Level:         Warning
Keywords:      Classic
User:          N/A
Computer:      xps-m1330-leal
Description:
NtpClient was unable to set a manual peer to use as a time source because of DNS resolution error on 'time.nist.gov,0x9'. NtpClient will try again in 15 minutes and double the reattempt interval thereafter. The error was: No such host is known. (0x80072AF9)
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Microsoft-Windows-Time-Service" Guid="{06EDCFEB-0FD0-4E53-ACCA-A6F8BBF81BCB}" EventSourceName="W32Time" />
    <EventID Qualifiers="33370">134</EventID>
    <Version>0</Version>
    <Level>3</Level>
    <Task>0</Task>
    <Opcode>0</Opcode>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2008-02-12T00:30:31.000Z" />
    <EventRecordID>15931</EventRecordID>
    <Correlation />
    <Execution ProcessID="0" ThreadID="0" />
    <Channel>System</Channel>
    <Computer>xps-m1330-leal</Computer>
    <Security />
  </System>
  <EventData Name="MSG_MANUAL_PEER_DNS_ERROR">
    <Data Name="ErrorMessage">No such host is known. (0x80072AF9)</Data>
    <Data Name="RetryMinutes">15</Data>
    <Data Name="DomainPeer">time.nist.gov,0x9</Data>
  </EventData>
</Event>

Log Name:      System
Source:        Microsoft-Windows-Time-Service
Date:          2/11/2008 6:30:27 PM
Event ID:      134
Task Category: None
Level:         Warning
Keywords:      Classic
User:          N/A
Computer:      xps-m1330-leal
Description:
NtpClient was unable to set a manual peer to use as a time source because of DNS resolution error on 'time.nist.gov,0x9'. NtpClient will try again in 15 minutes and double the reattempt interval thereafter. The error was: No such host is known. (0x80072AF9)
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Microsoft-Windows-Time-Service" Guid="{06EDCFEB-0FD0-4E53-ACCA-A6F8BBF81BCB}" EventSourceName="W32Time" />
    <EventID Qualifiers="33370">134</EventID>
    <Version>0</Version>
    <Level>3</Level>
    <Task>0</Task>
    <Opcode>0</Opcode>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2008-02-12T00:30:27.000Z" />
    <EventRecordID>15930</EventRecordID>
    <Correlation />
    <Execution ProcessID="0" ThreadID="0" />
    <Channel>System</Channel>
    <Computer>xps-m1330-leal</Computer>
    <Security />
  </System>
  <EventData Name="MSG_MANUAL_PEER_DNS_ERROR">
    <Data Name="ErrorMessage">No such host is known. (0x80072AF9)</Data>
    <Data Name="RetryMinutes">15</Data>
    <Data Name="DomainPeer">time.nist.gov,0x9</Data>
  </EventData>
</Event>

Log Name:      System
Source:        Microsoft-Windows-Time-Service
Date:          2/11/2008 6:30:26 PM
Event ID:      134
Task Category: None
Level:         Warning
Keywords:      Classic
User:          N/A
Computer:      xps-m1330-leal
Description:
NtpClient was unable to set a manual peer to use as a time source because of DNS resolution error on 'time.nist.gov,0x9'. NtpClient will try again in 15 minutes and double the reattempt interval thereafter. The error was: No such host is known. (0x80072AF9)
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Microsoft-Windows-Time-Service" Guid="{06EDCFEB-0FD0-4E53-ACCA-A6F8BBF81BCB}" EventSourceName="W32Time" />
    <EventID Qualifiers="33370">134</EventID>
    <Version>0</Version>
    <Level>3</Level>
    <Task>0</Task>
    <Opcode>0</Opcode>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2008-02-12T00:30:26.000Z" />
    <EventRecordID>15929</EventRecordID>
    <Correlation />
    <Execution ProcessID="0" ThreadID="0" />
    <Channel>System</Channel>
    <Computer>xps-m1330-leal</Computer>
    <Security />
  </System>
  <EventData Name="MSG_MANUAL_PEER_DNS_ERROR">
    <Data Name="ErrorMessage">No such host is known. (0x80072AF9)</Data>
    <Data Name="RetryMinutes">15</Data>
    <Data Name="DomainPeer">time.nist.gov,0x9</Data>
  </EventData>
</Event>

Log Name:      System
Source:        Microsoft-Windows-Time-Service
Date:          2/11/2008 6:30:22 PM
Event ID:      134
Task Category: None
Level:         Warning
Keywords:      Classic
User:          N/A
Computer:      xps-m1330-leal
Description:
NtpClient was unable to set a manual peer to use as a time source because of DNS resolution error on 'time.nist.gov,0x9'. NtpClient will try again in 15 minutes and double the reattempt interval thereafter. The error was: No such host is known. (0x80072AF9)
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Microsoft-Windows-Time-Service" Guid="{06EDCFEB-0FD0-4E53-ACCA-A6F8BBF81BCB}" EventSourceName="W32Time" />
    <EventID Qualifiers="33370">134</EventID>
    <Version>0</Version>
    <Level>3</Level>
    <Task>0</Task>
    <Opcode>0</Opcode>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2008-02-12T00:30:22.000Z" />
    <EventRecordID>15923</EventRecordID>
    <Correlation />
    <Execution ProcessID="0" ThreadID="0" />
    <Channel>System</Channel>
    <Computer>xps-m1330-leal</Computer>
    <Security />
  </System>
  <EventData Name="MSG_MANUAL_PEER_DNS_ERROR">
    <Data Name="ErrorMessage">No such host is known. (0x80072AF9)</Data>
    <Data Name="RetryMinutes">15</Data>
    <Data Name="DomainPeer">time.nist.gov,0x9</Data>
  </EventData>
</Event>

Log Name:      System
Source:        Microsoft-Windows-Time-Service
Date:          2/11/2008 6:30:17 PM
Event ID:      134
Task Category: None
Level:         Warning
Keywords:      Classic
User:          N/A
Computer:      xps-m1330-leal
Description:
NtpClient was unable to set a manual peer to use as a time source because of DNS resolution error on 'time.nist.gov,0x9'. NtpClient will try again in 15 minutes and double the reattempt interval thereafter. The error was: No such host is known. (0x80072AF9)
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Microsoft-Windows-Time-Service" Guid="{06EDCFEB-0FD0-4E53-ACCA-A6F8BBF81BCB}" EventSourceName="W32Time" />
    <EventID Qualifiers="33370">134</EventID>
    <Version>0</Version>
    <Level>3</Level>
    <Task>0</Task>
    <Opcode>0</Opcode>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2008-02-12T00:30:17.000Z" />
    <EventRecordID>15922</EventRecordID>
    <Correlation />
    <Execution ProcessID="0" ThreadID="0" />
    <Channel>System</Channel>
    <Computer>xps-m1330-leal</Computer>
    <Security />
  </System>
  <EventData Name="MSG_MANUAL_PEER_DNS_ERROR">
    <Data Name="ErrorMessage">No such host is known. (0x80072AF9)</Data>
    <Data Name="RetryMinutes">15</Data>
    <Data Name="DomainPeer">time.nist.gov,0x9</Data>
  </EventData>
</Event>

Log Name:      System
Source:        Microsoft-Windows-Time-Service
Date:          2/11/2008 6:30:16 PM
Event ID:      134
Task Category: None
Level:         Warning
Keywords:      Classic
User:          N/A
Computer:      xps-m1330-leal
Description:
NtpClient was unable to set a manual peer to use as a time source because of DNS resolution error on 'time.nist.gov,0x9'. NtpClient will try again in 15 minutes and double the reattempt interval thereafter. The error was: No such host is known. (0x80072AF9)
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Microsoft-Windows-Time-Service" Guid="{06EDCFEB-0FD0-4E53-ACCA-A6F8BBF81BCB}" EventSourceName="W32Time" />
    <EventID Qualifiers="33370">134</EventID>
    <Version>0</Version>
    <Level>3</Level>
    <Task>0</Task>
    <Opcode>0</Opcode>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2008-02-12T00:30:16.000Z" />
    <EventRecordID>15921</EventRecordID>
    <Correlation />
    <Execution ProcessID="0" ThreadID="0" />
    <Channel>System</Channel>
    <Computer>xps-m1330-leal</Computer>
    <Security />
  </System>
  <EventData Name="MSG_MANUAL_PEER_DNS_ERROR">
    <Data Name="ErrorMessage">No such host is known. (0x80072AF9)</Data>
    <Data Name="RetryMinutes">15</Data>
    <Data Name="DomainPeer">time.nist.gov,0x9</Data>
  </EventData>
</Event>

Log Name:      System
Source:        Microsoft-Windows-Time-Service
Date:          2/11/2008 6:30:05 PM
Event ID:      134
Task Category: None
Level:         Warning
Keywords:      Classic
User:          N/A
Computer:      xps-m1330-leal
Description:
NtpClient was unable to set a manual peer to use as a time source because of DNS resolution error on 'time.nist.gov,0x9'. NtpClient will try again in 15 minutes and double the reattempt interval thereafter. The error was: No such host is known. (0x80072AF9)
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Microsoft-Windows-Time-Service" Guid="{06EDCFEB-0FD0-4E53-ACCA-A6F8BBF81BCB}" EventSourceName="W32Time" />
    <EventID Qualifiers="33370">134</EventID>
    <Version>0</Version>
    <Level>3</Level>
    <Task>0</Task>
    <Opcode>0</Opcode>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2008-02-12T00:30:05.000Z" />
    <EventRecordID>15916</EventRecordID>
    <Correlation />
    <Execution ProcessID="0" ThreadID="0" />
    <Channel>System</Channel>
    <Computer>xps-m1330-leal</Computer>
    <Security />
  </System>
  <EventData Name="MSG_MANUAL_PEER_DNS_ERROR">
    <Data Name="ErrorMessage">No such host is known. (0x80072AF9)</Data>
    <Data Name="RetryMinutes">15</Data>
    <Data Name="DomainPeer">time.nist.gov,0x9</Data>
  </EventData>
</Event>

Log Name:      System
Source:        Microsoft-Windows-Time-Service
Date:          2/11/2008 6:39:04 PM
Event ID:      134
Task Category: None
Level:         Warning
Keywords:      Classic
User:          N/A
Computer:      xps-m1330-leal
Description:
NtpClient was unable to set a manual peer to use as a time source because of DNS resolution error on 'time.nist.gov,0x9'. NtpClient will try again in 15 minutes and double the reattempt interval thereafter. The error was: No such host is known. (0x80072AF9)
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Microsoft-Windows-Time-Service" Guid="{06EDCFEB-0FD0-4E53-ACCA-A6F8BBF81BCB}" EventSourceName="W32Time" />
    <EventID Qualifiers="33370">134</EventID>
    <Version>0</Version>
    <Level>3</Level>
    <Task>0</Task>
    <Opcode>0</Opcode>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2008-02-12T00:39:04.000Z" />
    <EventRecordID>15911</EventRecordID>
    <Correlation />
    <Execution ProcessID="0" ThreadID="0" />
    <Channel>System</Channel>
    <Computer>xps-m1330-leal</Computer>
    <Security />
  </System>
  <EventData Name="MSG_MANUAL_PEER_DNS_ERROR">
    <Data Name="ErrorMessage">No such host is known. (0x80072AF9)</Data>
    <Data Name="RetryMinutes">15</Data>
    <Data Name="DomainPeer">time.nist.gov,0x9</Data>
  </EventData>
</Event>

Log Name:      System
Source:        Microsoft-Windows-Time-Service
Date:          2/11/2008 6:38:39 PM
Event ID:      134
Task Category: None
Level:         Warning
Keywords:      Classic
User:          N/A
Computer:      xps-m1330-leal
Description:
NtpClient was unable to set a manual peer to use as a time source because of DNS resolution error on 'time.nist.gov,0x9'. NtpClient will try again in 15 minutes and double the reattempt interval thereafter. The error was: No such host is known. (0x80072AF9)
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Microsoft-Windows-Time-Service" Guid="{06EDCFEB-0FD0-4E53-ACCA-A6F8BBF81BCB}" EventSourceName="W32Time" />
    <EventID Qualifiers="33370">134</EventID>
    <Version>0</Version>
    <Level>3</Level>
    <Task>0</Task>
    <Opcode>0</Opcode>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2008-02-12T00:38:39.000Z" />
    <EventRecordID>15910</EventRecordID>
    <Correlation />
    <Execution ProcessID="0" ThreadID="0" />
    <Channel>System</Channel>
    <Computer>xps-m1330-leal</Computer>
    <Security />
  </System>
  <EventData Name="MSG_MANUAL_PEER_DNS_ERROR">
    <Data Name="ErrorMessage">No such host is known. (0x80072AF9)</Data>
    <Data Name="RetryMinutes">15</Data>
    <Data Name="DomainPeer">time.nist.gov,0x9</Data>
  </EventData>
</Event>

Log Name:      System
Source:        Microsoft-Windows-Time-Service
Date:          2/11/2008 6:38:32 PM
Event ID:      134
Task Category: None
Level:         Warning
Keywords:      Classic
User:          N/A
Computer:      xps-m1330-leal
Description:
NtpClient was unable to set a manual peer to use as a time source because of DNS resolution error on 'time.nist.gov,0x9'. NtpClient will try again in 15 minutes and double the reattempt interval thereafter. The error was: No such host is known. (0x80072AF9)
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Microsoft-Windows-Time-Service" Guid="{06EDCFEB-0FD0-4E53-ACCA-A6F8BBF81BCB}" EventSourceName="W32Time" />
    <EventID Qualifiers="33370">134</EventID>
    <Version>0</Version>
    <Level>3</Level>
    <Task>0</Task>
    <Opcode>0</Opcode>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2008-02-12T00:38:32.000Z" />
    <EventRecordID>15909</EventRecordID>
    <Correlation />
    <Execution ProcessID="0" ThreadID="0" />
    <Channel>System</Channel>
    <Computer>xps-m1330-leal</Computer>
    <Security />
  </System>
  <EventData Name="MSG_MANUAL_PEER_DNS_ERROR">
    <Data Name="ErrorMessage">No such host is known. (0x80072AF9)</Data>
    <Data Name="RetryMinutes">15</Data>
    <Data Name="DomainPeer">time.nist.gov,0x9</Data>
  </EventData>
</Event>

Log Name:      System
Source:        Microsoft-Windows-Time-Service
Date:          2/11/2008 6:38:30 PM
Event ID:      134
Task Category: None
Level:         Warning
Keywords:      Classic
User:          N/A
Computer:      xps-m1330-leal
Description:
NtpClient was unable to set a manual peer to use as a time source because of DNS resolution error on 'time.nist.gov,0x9'. NtpClient will try again in 15 minutes and double the reattempt interval thereafter. The error was: No such host is known. (0x80072AF9)
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Microsoft-Windows-Time-Service" Guid="{06EDCFEB-0FD0-4E53-ACCA-A6F8BBF81BCB}" EventSourceName="W32Time" />
    <EventID Qualifiers="33370">134</EventID>
    <Version>0</Version>
    <Level>3</Level>
    <Task>0</Task>
    <Opcode>0</Opcode>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2008-02-12T00:38:30.000Z" />
    <EventRecordID>15908</EventRecordID>
    <Correlation />
    <Execution ProcessID="0" ThreadID="0" />
    <Channel>System</Channel>
    <Computer>xps-m1330-leal</Computer>
    <Security />
  </System>
  <EventData Name="MSG_MANUAL_PEER_DNS_ERROR">
    <Data Name="ErrorMessage">No such host is known. (0x80072AF9)</Data>
    <Data Name="RetryMinutes">15</Data>
    <Data Name="DomainPeer">time.nist.gov,0x9</Data>
  </EventData>
</Event>

Log Name:      System
Source:        Microsoft-Windows-Time-Service
Date:          2/11/2008 6:38:02 PM
Event ID:      134
Task Category: None
Level:         Warning
Keywords:      Classic
User:          N/A
Computer:      xps-m1330-leal
Description:
NtpClient was unable to set a manual peer to use as a time source because of DNS resolution error on 'time.nist.gov,0x9'. NtpClient will try again in 15 minutes and double the reattempt interval thereafter. The error was: No such host is known. (0x80072AF9)
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Microsoft-Windows-Time-Service" Guid="{06EDCFEB-0FD0-4E53-ACCA-A6F8BBF81BCB}" EventSourceName="W32Time" />
    <EventID Qualifiers="33370">134</EventID>
    <Version>0</Version>
    <Level>3</Level>
    <Task>0</Task>
    <Opcode>0</Opcode>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2008-02-12T00:38:02.000Z" />
    <EventRecordID>15895</EventRecordID>
    <Correlation />
    <Execution ProcessID="0" ThreadID="0" />
    <Channel>System</Channel>
    <Computer>xps-m1330-leal</Computer>
    <Security />
  </System>
  <EventData Name="MSG_MANUAL_PEER_DNS_ERROR">
    <Data Name="ErrorMessage">No such host is known. (0x80072AF9)</Data>
    <Data Name="RetryMinutes">15</Data>
    <Data Name="DomainPeer">time.nist.gov,0x9</Data>
  </EventData>
</Event>

Log Name:      System
Source:        Microsoft-Windows-Time-Service
Date:          2/11/2008 6:38:01 PM
Event ID:      134
Task Category: None
Level:         Warning
Keywords:      Classic
User:          N/A
Computer:      xps-m1330-leal
Description:
NtpClient was unable to set a manual peer to use as a time source because of DNS resolution error on 'time.nist.gov,0x9'. NtpClient will try again in 15 minutes and double the reattempt interval thereafter. The error was: No such host is known. (0x80072AF9)
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Microsoft-Windows-Time-Service" Guid="{06EDCFEB-0FD0-4E53-ACCA-A6F8BBF81BCB}" EventSourceName="W32Time" />
    <EventID Qualifiers="33370">134</EventID>
    <Version>0</Version>
    <Level>3</Level>
    <Task>0</Task>
    <Opcode>0</Opcode>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2008-02-12T00:38:01.000Z" />
    <EventRecordID>15894</EventRecordID>
    <Correlation />
    <Execution ProcessID="0" ThreadID="0" />
    <Channel>System</Channel>
    <Computer>xps-m1330-leal</Computer>
    <Security />
  </System>
  <EventData Name="MSG_MANUAL_PEER_DNS_ERROR">
    <Data Name="ErrorMessage">No such host is known. (0x80072AF9)</Data>
    <Data Name="RetryMinutes">15</Data>
    <Data Name="DomainPeer">time.nist.gov,0x9</Data>
  </EventData>
</Event>

Log Name:      System
Source:        Microsoft-Windows-Time-Service
Date:          2/11/2008 6:38:00 PM
Event ID:      134
Task Category: None
Level:         Warning
Keywords:      Classic
User:          N/A
Computer:      xps-m1330-leal
Description:
NtpClient was unable to set a manual peer to use as a time source because of DNS resolution error on 'time.nist.gov,0x9'. NtpClient will try again in 15 minutes and double the reattempt interval thereafter. The error was: No such host is known. (0x80072AF9)
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Microsoft-Windows-Time-Service" Guid="{06EDCFEB-0FD0-4E53-ACCA-A6F8BBF81BCB}" EventSourceName="W32Time" />
    <EventID Qualifiers="33370">134</EventID>
    <Version>0</Version>
    <Level>3</Level>
    <Task>0</Task>
    <Opcode>0</Opcode>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2008-02-12T00:38:00.000Z" />
    <EventRecordID>15892</EventRecordID>
    <Correlation />
    <Execution ProcessID="0" ThreadID="0" />
    <Channel>System</Channel>
    <Computer>xps-m1330-leal</Computer>
    <Security />
  </System>
  <EventData Name="MSG_MANUAL_PEER_DNS_ERROR">
    <Data Name="ErrorMessage">No such host is known. (0x80072AF9)</Data>
    <Data Name="RetryMinutes">15</Data>
    <Data Name="DomainPeer">time.nist.gov,0x9</Data>
  </EventData>
</Event>

Log Name:      System
Source:        Microsoft-Windows-Time-Service
Date:          2/11/2008 6:21:02 PM
Event ID:      134
Task Category: None
Level:         Warning
Keywords:      Classic
User:          N/A
Computer:      xps-m1330-leal
Description:
NtpClient was unable to set a manual peer to use as a time source because of DNS resolution error on 'time.nist.gov,0x9'. NtpClient will try again in 15 minutes and double the reattempt interval thereafter. The error was: No such host is known. (0x80072AF9)
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Microsoft-Windows-Time-Service" Guid="{06EDCFEB-0FD0-4E53-ACCA-A6F8BBF81BCB}" EventSourceName="W32Time" />
    <EventID Qualifiers="33370">134</EventID>
    <Version>0</Version>
    <Level>3</Level>
    <Task>0</Task>
    <Opcode>0</Opcode>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2008-02-12T00:21:02.000Z" />
    <EventRecordID>15876</EventRecordID>
    <Correlation />
    <Execution ProcessID="0" ThreadID="0" />
    <Channel>System</Channel>
    <Computer>xps-m1330-leal</Computer>
    <Security />
  </System>
  <EventData Name="MSG_MANUAL_PEER_DNS_ERROR">
    <Data Name="ErrorMessage">No such host is known. (0x80072AF9)</Data>
    <Data Name="RetryMinutes">15</Data>
    <Data Name="DomainPeer">time.nist.gov,0x9</Data>
  </EventData>
</Event>

Log Name:      System
Source:        Microsoft-Windows-Time-Service
Date:          2/11/2008 6:44:06 PM
Event ID:      134
Task Category: None
Level:         Warning
Keywords:      Classic
User:          N/A
Computer:      xps-m1330-leal
Description:
NtpClient was unable to set a manual peer to use as a time source because of DNS resolution error on 'time.nist.gov,0x9'. NtpClient will try again in 15 minutes and double the reattempt interval thereafter. The error was: No such host is known. (0x80072AF9)
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Microsoft-Windows-Time-Service" Guid="{06EDCFEB-0FD0-4E53-ACCA-A6F8BBF81BCB}" EventSourceName="W32Time" />
    <EventID Qualifiers="33370">134</EventID>
    <Version>0</Version>
    <Level>3</Level>
    <Task>0</Task>
    <Opcode>0</Opcode>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2008-02-12T00:44:06.000Z" />
    <EventRecordID>15856</EventRecordID>
    <Correlation />
    <Execution ProcessID="0" ThreadID="0" />
    <Channel>System</Channel>
    <Computer>xps-m1330-leal</Computer>
    <Security />
  </System>
  <EventData Name="MSG_MANUAL_PEER_DNS_ERROR">
    <Data Name="ErrorMessage">No such host is known. (0x80072AF9)</Data>
    <Data Name="RetryMinutes">15</Data>
    <Data Name="DomainPeer">time.nist.gov,0x9</Data>
  </EventData>
</Event>

Log Name:      System
Source:        Microsoft-Windows-Time-Service
Date:          2/11/2008 6:23:04 PM
Event ID:      134
Task Category: None
Level:         Warning
Keywords:      Classic
User:          N/A
Computer:      xps-m1330-leal
Description:
NtpClient was unable to set a manual peer to use as a time source because of DNS resolution error on 'time.nist.gov,0x9'. NtpClient will try again in 15 minutes and double the reattempt interval thereafter. The error was: No such host is known. (0x80072AF9)
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Microsoft-Windows-Time-Service" Guid="{06EDCFEB-0FD0-4E53-ACCA-A6F8BBF81BCB}" EventSourceName="W32Time" />
    <EventID Qualifiers="33370">134</EventID>
    <Version>0</Version>
    <Level>3</Level>
    <Task>0</Task>
    <Opcode>0</Opcode>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2008-02-12T00:23:04.000Z" />
    <EventRecordID>15835</EventRecordID>
    <Correlation />
    <Execution ProcessID="0" ThreadID="0" />
    <Channel>System</Channel>
    <Computer>xps-m1330-leal</Computer>
    <Security />
  </System>
  <EventData Name="MSG_MANUAL_PEER_DNS_ERROR">
    <Data Name="ErrorMessage">No such host is known. (0x80072AF9)</Data>
    <Data Name="RetryMinutes">15</Data>
    <Data Name="DomainPeer">time.nist.gov,0x9</Data>
  </EventData>
</Event>

Log Name:      System
Source:        Microsoft-Windows-Time-Service
Date:          2/11/2008 3:40:27 PM
Event ID:      134
Task Category: None
Level:         Warning
Keywords:      Classic
User:          N/A
Computer:      xps-m1330-leal
Description:
NtpClient was unable to set a manual peer to use as a time source because of DNS resolution error on 'time.nist.gov,0x9'. NtpClient will try again in 15 minutes and double the reattempt interval thereafter. The error was: No such host is known. (0x80072AF9)
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Microsoft-Windows-Time-Service" Guid="{06EDCFEB-0FD0-4E53-ACCA-A6F8BBF81BCB}" EventSourceName="W32Time" />
    <EventID Qualifiers="33370">134</EventID>
    <Version>0</Version>
    <Level>3</Level>
    <Task>0</Task>
    <Opcode>0</Opcode>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2008-02-11T21:40:27.000Z" />
    <EventRecordID>15824</EventRecordID>
    <Correlation />
    <Execution ProcessID="0" ThreadID="0" />
    <Channel>System</Channel>
    <Computer>xps-m1330-leal</Computer>
    <Security />
  </System>
  <EventData Name="MSG_MANUAL_PEER_DNS_ERROR">
    <Data Name="ErrorMessage">No such host is known. (0x80072AF9)</Data>
    <Data Name="RetryMinutes">15</Data>
    <Data Name="DomainPeer">time.nist.gov,0x9</Data>
  </EventData>
</Event>

Log Name:      System
Source:        Microsoft-Windows-Time-Service
Date:          2/11/2008 3:40:01 PM
Event ID:      134
Task Category: None
Level:         Warning
Keywords:      Classic
User:          N/A
Computer:      xps-m1330-leal
Description:
NtpClient was unable to set a manual peer to use as a time source because of DNS resolution error on 'pool.ntp.org,0x9'. NtpClient will try again in 15 minutes and double the reattempt interval thereafter. The error was: No such host is known. (0x80072AF9)
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Microsoft-Windows-Time-Service" Guid="{06EDCFEB-0FD0-4E53-ACCA-A6F8BBF81BCB}" EventSourceName="W32Time" />
    <EventID Qualifiers="33370">134</EventID>
    <Version>0</Version>
    <Level>3</Level>
    <Task>0</Task>
    <Opcode>0</Opcode>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2008-02-11T21:40:01.000Z" />
    <EventRecordID>15823</EventRecordID>
    <Correlation />
    <Execution ProcessID="0" ThreadID="0" />
    <Channel>System</Channel>
    <Computer>xps-m1330-leal</Computer>
    <Security />
  </System>
  <EventData Name="MSG_MANUAL_PEER_DNS_ERROR">
    <Data Name="ErrorMessage">No such host is known. (0x80072AF9)</Data>
    <Data Name="RetryMinutes">15</Data>
    <Data Name="DomainPeer">pool.ntp.org,0x9</Data>
  </EventData>
</Event>

Log Name:      System
Source:        Microsoft-Windows-Time-Service
Date:          2/11/2008 3:30:21 PM
Event ID:      35
Task Category: None
Level:         Information
Keywords:      Classic
User:          N/A
Computer:      xps-m1330-leal
Description:
The time service is now synchronizing the system time with the time source pool.ntp.org,0x9 (ntp.m|0x9|0.0.0.0:123->64.202.112.65:123).
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Microsoft-Windows-Time-Service" Guid="{06EDCFEB-0FD0-4E53-ACCA-A6F8BBF81BCB}" EventSourceName="W32Time" />
    <EventID Qualifiers="16986">35</EventID>
    <Version>0</Version>
    <Level>4</Level>
    <Task>0</Task>
    <Opcode>0</Opcode>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2008-02-11T21:30:21.000Z" />
    <EventRecordID>15747</EventRecordID>
    <Correlation />
    <Execution ProcessID="0" ThreadID="0" />
    <Channel>System</Channel>
    <Computer>xps-m1330-leal</Computer>
    <Security />
  </System>
  <EventData Name="MSG_TIME_SOURCE_CHOSEN">
    <Data Name="TimeSource">pool.ntp.org,0x9 (ntp.m|0x9|0.0.0.0:123-&gt;64.202.112.65:123)</Data>
  </EventData>
</Event>

Log Name:      System
Source:        Microsoft-Windows-Time-Service
Date:          2/11/2008 3:30:21 PM
Event ID:      52
Task Category: None
Level:         Warning
Keywords:      Classic
User:          N/A
Computer:      xps-m1330-leal
Description:
The time service has set the time with offset 43206 seconds.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Microsoft-Windows-Time-Service" Guid="{06EDCFEB-0FD0-4E53-ACCA-A6F8BBF81BCB}" EventSourceName="W32Time" />
    <EventID Qualifiers="33370">52</EventID>
    <Version>0</Version>
    <Level>3</Level>
    <Task>0</Task>
    <Opcode>0</Opcode>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2008-02-11T21:30:21.000Z" />
    <EventRecordID>15746</EventRecordID>
    <Correlation />
    <Execution ProcessID="0" ThreadID="0" />
    <Channel>System</Channel>
    <Computer>xps-m1330-leal</Computer>
    <Security />
  </System>
  <EventData Name="MSG_TIME_JUMP_AUDIT">
    <Data Name="TimeOffsetSeconds">43206</Data>
  </EventData>
</Event>

Log Name:      System
Source:        Microsoft-Windows-Time-Service
Date:          2/11/2008 3:30:15 AM
Event ID:      37
Task Category: None
Level:         Information
Keywords:      Classic
User:          N/A
Computer:      xps-m1330-leal
Description:
The time provider NtpClient is currently receiving valid time data from pool.ntp.org,0x9 (ntp.m|0x9|0.0.0.0:123->64.202.112.65:123).
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Microsoft-Windows-Time-Service" Guid="{06EDCFEB-0FD0-4E53-ACCA-A6F8BBF81BCB}" EventSourceName="W32Time" />
    <EventID Qualifiers="16986">37</EventID>
    <Version>0</Version>
    <Level>4</Level>
    <Task>0</Task>
    <Opcode>0</Opcode>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2008-02-11T09:30:15.000Z" />
    <EventRecordID>15745</EventRecordID>
    <Correlation />
    <Execution ProcessID="0" ThreadID="0" />
    <Channel>System</Channel>
    <Computer>xps-m1330-leal</Computer>
    <Security />
  </System>
  <EventData Name="MSG_TIME_SOURCE_REACHABLE">
    <Data Name="TimeSource">pool.ntp.org,0x9 (ntp.m|0x9|0.0.0.0:123-&gt;64.202.112.65:123)</Data>
  </EventData>
</Event>

Log Name:      System
Source:        Microsoft-Windows-Time-Service
Date:          2/11/2008 10:14:16 AM
Event ID:      36
Task Category: None
Level:         Warning
Keywords:      Classic
User:          N/A
Computer:      xps-m1330-leal
Description:
The time service has not synchronized the system time for 86400 seconds because none of the time service providers provided a usable time stamp. The time service will not update the local system time until it is able to synchronize with a time source. If the local system is configured to act as a time server for clients, it will stop advertising as a time source to clients. The time service will continue to retry and sync time with its time sources. Check system event log for other W32time events for more details. Run 'w32tm /resync' to force an instant time synchronization.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Microsoft-Windows-Time-Service" Guid="{06EDCFEB-0FD0-4E53-ACCA-A6F8BBF81BCB}" EventSourceName="W32Time" />
    <EventID Qualifiers="33370">36</EventID>
    <Version>0</Version>
    <Level>3</Level>
    <Task>0</Task>
    <Opcode>0</Opcode>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2008-02-11T16:14:16.000Z" />
    <EventRecordID>15515</EventRecordID>
    <Correlation />
    <Execution ProcessID="0" ThreadID="0" />
    <Channel>System</Channel>
    <Computer>xps-m1330-leal</Computer>
    <Security />
  </System>
  <EventData Name="MSG_TIME_SOURCE_NONE">
    <Data Name="UnsynchronizedTimeSeconds">86400</Data>
  </EventData>
</Event>

Log Name:      System
Source:        Microsoft-Windows-Time-Service
Date:          2/10/2008 9:23:05 AM
Event ID:      34
Task Category: None
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      xps-m1330-leal
Description:
The time service has detected that the system time needs to be  changed by +88310 seconds. The time service will not change the system time by more than +54000 seconds. Verify that your time and time zone are correct, and that the time source pool.ntp.org,0x9 (ntp.m|0x9|0.0.0.0:123->216.75.55.11:123) is working properly.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Microsoft-Windows-Time-Service" Guid="{06EDCFEB-0FD0-4E53-ACCA-A6F8BBF81BCB}" EventSourceName="W32Time" />
    <EventID Qualifiers="49754">34</EventID>
    <Version>0</Version>
    <Level>2</Level>
    <Task>0</Task>
    <Opcode>0</Opcode>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2008-02-10T15:23:05.000Z" />
    <EventRecordID>15508</EventRecordID>
    <Correlation />
    <Execution ProcessID="0" ThreadID="0" />
    <Channel>System</Channel>
    <Computer>xps-m1330-leal</Computer>
    <Security />
  </System>
  <EventData Name="MSG_TIME_CHANGE_TOO_BIG">
    <Data Name="SystemTimeChangeSeconds">+88310</Data>
    <Data Name="MaxSystemTimeChangeSeconds">+54000</Data>
    <Data Name="TimeSource">pool.ntp.org,0x9 (ntp.m|0x9|0.0.0.0:123-&gt;216.75.55.11:123)</Data>
  </EventData>
</Event>

Log Name:      System
Source:        Microsoft-Windows-Time-Service
Date:          2/10/2008 9:23:05 AM
Event ID:      37
Task Category: None
Level:         Information
Keywords:      Classic
User:          N/A
Computer:      xps-m1330-leal
Description:
The time provider NtpClient is currently receiving valid time data from pool.ntp.org,0x9 (ntp.m|0x9|0.0.0.0:123->216.75.55.11:123).
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Microsoft-Windows-Time-Service" Guid="{06EDCFEB-0FD0-4E53-ACCA-A6F8BBF81BCB}" EventSourceName="W32Time" />
    <EventID Qualifiers="16986">37</EventID>
    <Version>0</Version>
    <Level>4</Level>
    <Task>0</Task>
    <Opcode>0</Opcode>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2008-02-10T15:23:05.000Z" />
    <EventRecordID>15507</EventRecordID>
    <Correlation />
    <Execution ProcessID="0" ThreadID="0" />
    <Channel>System</Channel>
    <Computer>xps-m1330-leal</Computer>
    <Security />
  </System>
  <EventData Name="MSG_TIME_SOURCE_REACHABLE">
    <Data Name="TimeSource">pool.ntp.org,0x9 (ntp.m|0x9|0.0.0.0:123-&gt;216.75.55.11:123)</Data>
  </EventData>
</Event>

Log Name:      System
Source:        Microsoft-Windows-Time-Service
Date:          2/10/2008 9:45:51 AM
Event ID:      34
Task Category: None
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      xps-m1330-leal
Description:
The time service has detected that the system time needs to be  changed by +86438 seconds. The time service will not change the system time by more than +54000 seconds. Verify that your time and time zone are correct, and that the time source pool.ntp.org,0x9 (ntp.m|0x9|0.0.0.0:123->38.99.80.156:123) is working properly.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Microsoft-Windows-Time-Service" Guid="{06EDCFEB-0FD0-4E53-ACCA-A6F8BBF81BCB}" EventSourceName="W32Time" />
    <EventID Qualifiers="49754">34</EventID>
    <Version>0</Version>
    <Level>2</Level>
    <Task>0</Task>
    <Opcode>0</Opcode>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2008-02-10T15:45:51.000Z" />
    <EventRecordID>15503</EventRecordID>
    <Correlation />
    <Execution ProcessID="0" ThreadID="0" />
    <Channel>System</Channel>
    <Computer>xps-m1330-leal</Computer>
    <Security />
  </System>
  <EventData Name="MSG_TIME_CHANGE_TOO_BIG">
    <Data Name="SystemTimeChangeSeconds">+86438</Data>
    <Data Name="MaxSystemTimeChangeSeconds">+54000</Data>
    <Data Name="TimeSource">pool.ntp.org,0x9 (ntp.m|0x9|0.0.0.0:123-&gt;38.99.80.156:123)</Data>
  </EventData>
</Event>

Log Name:      System
Source:        Microsoft-Windows-Time-Service
Date:          2/10/2008 9:45:51 AM
Event ID:      37
Task Category: None
Level:         Information
Keywords:      Classic
User:          N/A
Computer:      xps-m1330-leal
Description:
The time provider NtpClient is currently receiving valid time data from pool.ntp.org,0x9 (ntp.m|0x9|0.0.0.0:123->38.99.80.156:123).
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Microsoft-Windows-Time-Service" Guid="{06EDCFEB-0FD0-4E53-ACCA-A6F8BBF81BCB}" EventSourceName="W32Time" />
    <EventID Qualifiers="16986">37</EventID>
    <Version>0</Version>
    <Level>4</Level>
    <Task>0</Task>
    <Opcode>0</Opcode>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2008-02-10T15:45:51.000Z" />
    <EventRecordID>15502</EventRecordID>
    <Correlation />
    <Execution ProcessID="0" ThreadID="0" />
    <Channel>System</Channel>
    <Computer>xps-m1330-leal</Computer>
    <Security />
  </System>
  <EventData Name="MSG_TIME_SOURCE_REACHABLE">
    <Data Name="TimeSource">pool.ntp.org,0x9 (ntp.m|0x9|0.0.0.0:123-&gt;38.99.80.156:123)</Data>
  </EventData>
</Event>

Log Name:      System
Source:        Microsoft-Windows-Time-Service
Date:          2/10/2008 9:24:31 AM
Event ID:      34
Task Category: None
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      xps-m1330-leal
Description:
The time service has detected that the system time needs to be  changed by +86438 seconds. The time service will not change the system time by more than +54000 seconds. Verify that your time and time zone are correct, and that the time source TOCK.USNO.NAVY.MIL,0x9 (ntp.m|0x9|0.0.0.0:123->192.5.41.41:123) is working properly.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Microsoft-Windows-Time-Service" Guid="{06EDCFEB-0FD0-4E53-ACCA-A6F8BBF81BCB}" EventSourceName="W32Time" />
    <EventID Qualifiers="49754">34</EventID>
    <Version>0</Version>
    <Level>2</Level>
    <Task>0</Task>
    <Opcode>0</Opcode>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2008-02-10T15:24:31.000Z" />
    <EventRecordID>15486</EventRecordID>
    <Correlation />
    <Execution ProcessID="0" ThreadID="0" />
    <Channel>System</Channel>
    <Computer>xps-m1330-leal</Computer>
    <Security />
  </System>
  <EventData Name="MSG_TIME_CHANGE_TOO_BIG">
    <Data Name="SystemTimeChangeSeconds">+86438</Data>
    <Data Name="MaxSystemTimeChangeSeconds">+54000</Data>
    <Data Name="TimeSource">TOCK.USNO.NAVY.MIL,0x9 (ntp.m|0x9|0.0.0.0:123-&gt;192.5.41.41:123)</Data>
  </EventData>
</Event>

Log Name:      System
Source:        Microsoft-Windows-Time-Service
Date:          2/10/2008 9:24:30 AM
Event ID:      34
Task Category: None
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      xps-m1330-leal
Description:
The time service has detected that the system time needs to be  changed by +86438 seconds. The time service will not change the system time by more than +54000 seconds. Verify that your time and time zone are correct, and that the time source TOCK.USNO.NAVY.MIL,0x9 (ntp.m|0x9|0.0.0.0:123->192.5.41.41:123) is working properly.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Microsoft-Windows-Time-Service" Guid="{06EDCFEB-0FD0-4E53-ACCA-A6F8BBF81BCB}" EventSourceName="W32Time" />
    <EventID Qualifiers="49754">34</EventID>
    <Version>0</Version>
    <Level>2</Level>
    <Task>0</Task>
    <Opcode>0</Opcode>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2008-02-10T15:24:30.000Z" />
    <EventRecordID>15485</EventRecordID>
    <Correlation />
    <Execution ProcessID="0" ThreadID="0" />
    <Channel>System</Channel>
    <Computer>xps-m1330-leal</Computer>
    <Security />
  </System>
  <EventData Name="MSG_TIME_CHANGE_TOO_BIG">
    <Data Name="SystemTimeChangeSeconds">+86438</Data>
    <Data Name="MaxSystemTimeChangeSeconds">+54000</Data>
    <Data Name="TimeSource">TOCK.USNO.NAVY.MIL,0x9 (ntp.m|0x9|0.0.0.0:123-&gt;192.5.41.41:123)</Data>
  </EventData>
</Event>

Log Name:      System
Source:        Microsoft-Windows-Time-Service
Date:          2/10/2008 9:24:30 AM
Event ID:      37
Task Category: None
Level:         Information
Keywords:      Classic
User:          N/A
Computer:      xps-m1330-leal
Description:
The time provider NtpClient is currently receiving valid time data from TOCK.USNO.NAVY.MIL,0x9 (ntp.m|0x9|0.0.0.0:123->192.5.41.41:123).
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Microsoft-Windows-Time-Service" Guid="{06EDCFEB-0FD0-4E53-ACCA-A6F8BBF81BCB}" EventSourceName="W32Time" />
    <EventID Qualifiers="16986">37</EventID>
    <Version>0</Version>
    <Level>4</Level>
    <Task>0</Task>
    <Opcode>0</Opcode>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2008-02-10T15:24:30.000Z" />
    <EventRecordID>15484</EventRecordID>
    <Correlation />
    <Execution ProcessID="0" ThreadID="0" />
    <Channel>System</Channel>
    <Computer>xps-m1330-leal</Computer>
    <Security />
  </System>
  <EventData Name="MSG_TIME_SOURCE_REACHABLE">
    <Data Name="TimeSource">TOCK.USNO.NAVY.MIL,0x9 (ntp.m|0x9|0.0.0.0:123-&gt;192.5.41.41:123)</Data>
  </EventData>
</Event>

Log Name:      System
Source:        Microsoft-Windows-Time-Service
Date:          2/10/2008 9:23:07 AM
Event ID:      34
Task Category: None
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      xps-m1330-leal
Description:
The time service has detected that the system time needs to be  changed by +86438 seconds. The time service will not change the system time by more than +54000 seconds. Verify that your time and time zone are correct, and that the time source time-b.nist.gov,0x9 (ntp.m|0x9|0.0.0.0:123->129.6.15.29:123) is working properly.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Microsoft-Windows-Time-Service" Guid="{06EDCFEB-0FD0-4E53-ACCA-A6F8BBF81BCB}" EventSourceName="W32Time" />
    <EventID Qualifiers="49754">34</EventID>
    <Version>0</Version>
    <Level>2</Level>
    <Task>0</Task>
    <Opcode>0</Opcode>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2008-02-10T15:23:07.000Z" />
    <EventRecordID>15483</EventRecordID>
    <Correlation />
    <Execution ProcessID="0" ThreadID="0" />
    <Channel>System</Channel>
    <Computer>xps-m1330-leal</Computer>
    <Security />
  </System>
  <EventData Name="MSG_TIME_CHANGE_TOO_BIG">
    <Data Name="SystemTimeChangeSeconds">+86438</Data>
    <Data Name="MaxSystemTimeChangeSeconds">+54000</Data>
    <Data Name="TimeSource">time-b.nist.gov,0x9 (ntp.m|0x9|0.0.0.0:123-&gt;129.6.15.29:123)</Data>
  </EventData>
</Event>

Log Name:      System
Source:        Microsoft-Windows-Time-Service
Date:          2/10/2008 9:23:06 AM
Event ID:      34
Task Category: None
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      xps-m1330-leal
Description:
The time service has detected that the system time needs to be  changed by +86438 seconds. The time service will not change the system time by more than +54000 seconds. Verify that your time and time zone are correct, and that the time source time-b.nist.gov,0x9 (ntp.m|0x9|0.0.0.0:123->129.6.15.29:123) is working properly.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Microsoft-Windows-Time-Service" Guid="{06EDCFEB-0FD0-4E53-ACCA-A6F8BBF81BCB}" EventSourceName="W32Time" />
    <EventID Qualifiers="49754">34</EventID>
    <Version>0</Version>
    <Level>2</Level>
    <Task>0</Task>
    <Opcode>0</Opcode>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2008-02-10T15:23:06.000Z" />
    <EventRecordID>15482</EventRecordID>
    <Correlation />
    <Execution ProcessID="0" ThreadID="0" />
    <Channel>System</Channel>
    <Computer>xps-m1330-leal</Computer>
    <Security />
  </System>
  <EventData Name="MSG_TIME_CHANGE_TOO_BIG">
    <Data Name="SystemTimeChangeSeconds">+86438</Data>
    <Data Name="MaxSystemTimeChangeSeconds">+54000</Data>
    <Data Name="TimeSource">time-b.nist.gov,0x9 (ntp.m|0x9|0.0.0.0:123-&gt;129.6.15.29:123)</Data>
  </EventData>
</Event>

Log Name:      System
Source:        Microsoft-Windows-Time-Service
Date:          2/10/2008 9:23:06 AM
Event ID:      37
Task Category: None
Level:         Information
Keywords:      Classic
User:          N/A
Computer:      xps-m1330-leal
Description:
The time provider NtpClient is currently receiving valid time data from time-b.nist.gov,0x9 (ntp.m|0x9|0.0.0.0:123->129.6.15.29:123).
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Microsoft-Windows-Time-Service" Guid="{06EDCFEB-0FD0-4E53-ACCA-A6F8BBF81BCB}" EventSourceName="W32Time" />
    <EventID Qualifiers="16986">37</EventID>
    <Version>0</Version>
    <Level>4</Level>
    <Task>0</Task>
    <Opcode>0</Opcode>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2008-02-10T15:23:06.000Z" />
    <EventRecordID>15481</EventRecordID>
    <Correlation />
    <Execution ProcessID="0" ThreadID="0" />
    <Channel>System</Channel>
    <Computer>xps-m1330-leal</Computer>
    <Security />
  </System>
  <EventData Name="MSG_TIME_SOURCE_REACHABLE">
    <Data Name="TimeSource">time-b.nist.gov,0x9 (ntp.m|0x9|0.0.0.0:123-&gt;129.6.15.29:123)</Data>
  </EventData>
</Event>

Log Name:      System
Source:        Microsoft-Windows-Time-Service
Date:          2/10/2008 9:22:47 AM
Event ID:      34
Task Category: None
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      xps-m1330-leal
Description:
The time service has detected that the system time needs to be  changed by +86438 seconds. The time service will not change the system time by more than +54000 seconds. Verify that your time and time zone are correct, and that the time source time-a.nist.gov,0x9 (ntp.m|0x9|0.0.0.0:123->129.6.15.28:123) is working properly.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Microsoft-Windows-Time-Service" Guid="{06EDCFEB-0FD0-4E53-ACCA-A6F8BBF81BCB}" EventSourceName="W32Time" />
    <EventID Qualifiers="49754">34</EventID>
    <Version>0</Version>
    <Level>2</Level>
    <Task>0</Task>
    <Opcode>0</Opcode>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2008-02-10T15:22:47.000Z" />
    <EventRecordID>15479</EventRecordID>
    <Correlation />
    <Execution ProcessID="0" ThreadID="0" />
    <Channel>System</Channel>
    <Computer>xps-m1330-leal</Computer>
    <Security />
  </System>
  <EventData Name="MSG_TIME_CHANGE_TOO_BIG">
    <Data Name="SystemTimeChangeSeconds">+86438</Data>
    <Data Name="MaxSystemTimeChangeSeconds">+54000</Data>
    <Data Name="TimeSource">time-a.nist.gov,0x9 (ntp.m|0x9|0.0.0.0:123-&gt;129.6.15.28:123)</Data>
  </EventData>
</Event>

Log Name:      System
Source:        Microsoft-Windows-Time-Service
Date:          2/10/2008 9:22:45 AM
Event ID:      37
Task Category: None
Level:         Information
Keywords:      Classic
User:          N/A
Computer:      xps-m1330-leal
Description:
The time provider NtpClient is currently receiving valid time data from time-a.nist.gov,0x9 (ntp.m|0x9|0.0.0.0:123->129.6.15.28:123).
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Microsoft-Windows-Time-Service" Guid="{06EDCFEB-0FD0-4E53-ACCA-A6F8BBF81BCB}" EventSourceName="W32Time" />
    <EventID Qualifiers="16986">37</EventID>
    <Version>0</Version>
    <Level>4</Level>
    <Task>0</Task>
    <Opcode>0</Opcode>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2008-02-10T15:22:45.000Z" />
    <EventRecordID>15478</EventRecordID>
    <Correlation />
    <Execution ProcessID="0" ThreadID="0" />
    <Channel>System</Channel>
    <Computer>xps-m1330-leal</Computer>
    <Security />
  </System>
  <EventData Name="MSG_TIME_SOURCE_REACHABLE">
    <Data Name="TimeSource">time-a.nist.gov,0x9 (ntp.m|0x9|0.0.0.0:123-&gt;129.6.15.28:123)</Data>
  </EventData>
</Event>

Log Name:      System
Source:        Microsoft-Windows-Time-Service
Date:          2/10/2008 9:22:11 AM
Event ID:      34
Task Category: None
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      xps-m1330-leal
Description:
The time service has detected that the system time needs to be  changed by +86438 seconds. The time service will not change the system time by more than +54000 seconds. Verify that your time and time zone are correct, and that the time source time.windows.com,0x9 (ntp.m|0x9|0.0.0.0:123->207.46.232.182:123) is working properly.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Microsoft-Windows-Time-Service" Guid="{06EDCFEB-0FD0-4E53-ACCA-A6F8BBF81BCB}" EventSourceName="W32Time" />
    <EventID Qualifiers="49754">34</EventID>
    <Version>0</Version>
    <Level>2</Level>
    <Task>0</Task>
    <Opcode>0</Opcode>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2008-02-10T15:22:11.000Z" />
    <EventRecordID>15477</EventRecordID>
    <Correlation />
    <Execution ProcessID="0" ThreadID="0" />
    <Channel>System</Channel>
    <Computer>xps-m1330-leal</Computer>
    <Security />
  </System>
  <EventData Name="MSG_TIME_CHANGE_TOO_BIG">
    <Data Name="SystemTimeChangeSeconds">+86438</Data>
    <Data Name="MaxSystemTimeChangeSeconds">+54000</Data>
    <Data Name="TimeSource">time.windows.com,0x9 (ntp.m|0x9|0.0.0.0:123-&gt;207.46.232.182:123)</Data>
  </EventData>
</Event>

Log Name:      System
Source:        Microsoft-Windows-Time-Service
Date:          2/10/2008 9:22:04 AM
Event ID:      34
Task Category: None
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      xps-m1330-leal
Description:
The time service has detected that the system time needs to be  changed by +86438 seconds. The time service will not change the system time by more than +54000 seconds. Verify that your time and time zone are correct, and that the time source time.windows.com,0x9 (ntp.m|0x9|0.0.0.0:123->207.46.232.182:123) is working properly.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Microsoft-Windows-Time-Service" Guid="{06EDCFEB-0FD0-4E53-ACCA-A6F8BBF81BCB}" EventSourceName="W32Time" />
    <EventID Qualifiers="49754">34</EventID>
    <Version>0</Version>
    <Level>2</Level>
    <Task>0</Task>
    <Opcode>0</Opcode>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2008-02-10T15:22:04.000Z" />
    <EventRecordID>15476</EventRecordID>
    <Correlation />
    <Execution ProcessID="0" ThreadID="0" />
    <Channel>System</Channel>
    <Computer>xps-m1330-leal</Computer>
    <Security />
  </System>
  <EventData Name="MSG_TIME_CHANGE_TOO_BIG">
    <Data Name="SystemTimeChangeSeconds">+86438</Data>
    <Data Name="MaxSystemTimeChangeSeconds">+54000</Data>
    <Data Name="TimeSource">time.windows.com,0x9 (ntp.m|0x9|0.0.0.0:123-&gt;207.46.232.182:123)</Data>
  </EventData>
</Event>

Log Name:      System
Source:        Microsoft-Windows-Time-Service
Date:          2/10/2008 9:21:57 AM
Event ID:      34
Task Category: None
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      xps-m1330-leal
Description:
The time service has detected that the system time needs to be  changed by +86438 seconds. The time service will not change the system time by more than +54000 seconds. Verify that your time and time zone are correct, and that the time source time.windows.com,0x9 (ntp.m|0x9|0.0.0.0:123->207.46.232.182:123) is working properly.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Microsoft-Windows-Time-Service" Guid="{06EDCFEB-0FD0-4E53-ACCA-A6F8BBF81BCB}" EventSourceName="W32Time" />
    <EventID Qualifiers="49754">34</EventID>
    <Version>0</Version>
    <Level>2</Level>
    <Task>0</Task>
    <Opcode>0</Opcode>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2008-02-10T15:21:57.000Z" />
    <EventRecordID>15475</EventRecordID>
    <Correlation />
    <Execution ProcessID="0" ThreadID="0" />
    <Channel>System</Channel>
    <Computer>xps-m1330-leal</Computer>
    <Security />
  </System>
  <EventData Name="MSG_TIME_CHANGE_TOO_BIG">
    <Data Name="SystemTimeChangeSeconds">+86438</Data>
    <Data Name="MaxSystemTimeChangeSeconds">+54000</Data>
    <Data Name="TimeSource">time.windows.com,0x9 (ntp.m|0x9|0.0.0.0:123-&gt;207.46.232.182:123)</Data>
  </EventData>
</Event>

Log Name:      System
Source:        Microsoft-Windows-Time-Service
Date:          2/10/2008 9:21:57 AM
Event ID:      37
Task Category: None
Level:         Information
Keywords:      Classic
User:          N/A
Computer:      xps-m1330-leal
Description:
The time provider NtpClient is currently receiving valid time data from time.windows.com,0x9 (ntp.m|0x9|0.0.0.0:123->207.46.232.182:123).
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Microsoft-Windows-Time-Service" Guid="{06EDCFEB-0FD0-4E53-ACCA-A6F8BBF81BCB}" EventSourceName="W32Time" />
    <EventID Qualifiers="16986">37</EventID>
    <Version>0</Version>
    <Level>4</Level>
    <Task>0</Task>
    <Opcode>0</Opcode>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2008-02-10T15:21:57.000Z" />
    <EventRecordID>15474</EventRecordID>
    <Correlation />
    <Execution ProcessID="0" ThreadID="0" />
    <Channel>System</Channel>
    <Computer>xps-m1330-leal</Computer>
    <Security />
  </System>
  <EventData Name="MSG_TIME_SOURCE_REACHABLE">
    <Data Name="TimeSource">time.windows.com,0x9 (ntp.m|0x9|0.0.0.0:123-&gt;207.46.232.182:123)</Data>
  </EventData>
</Event>

Log Name:      System
Source:        Microsoft-Windows-Time-Service
Date:          2/8/2008 10:11:34 PM
Event ID:      36
Task Category: None
Level:         Warning
Keywords:      Classic
User:          N/A
Computer:      xps-m1330-leal
Description:
The time service has not synchronized the system time for 86400 seconds because none of the time service providers provided a usable time stamp. The time service will not update the local system time until it is able to synchronize with a time source. If the local system is configured to act as a time server for clients, it will stop advertising as a time source to clients. The time service will continue to retry and sync time with its time sources. Check system event log for other W32time events for more details. Run 'w32tm /resync' to force an instant time synchronization.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Microsoft-Windows-Time-Service" Guid="{06EDCFEB-0FD0-4E53-ACCA-A6F8BBF81BCB}" EventSourceName="W32Time" />
    <EventID Qualifiers="33370">36</EventID>
    <Version>0</Version>
    <Level>3</Level>
    <Task>0</Task>
    <Opcode>0</Opcode>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2008-02-09T04:11:34.000Z" />
    <EventRecordID>15099</EventRecordID>
    <Correlation />
    <Execution ProcessID="0" ThreadID="0" />
    <Channel>System</Channel>
    <Computer>xps-m1330-leal</Computer>
    <Security />
  </System>
  <EventData Name="MSG_TIME_SOURCE_NONE">
    <Data Name="UnsynchronizedTimeSeconds">86400</Data>
  </EventData>
</Event>

Log Name:      System
Source:        Microsoft-Windows-Time-Service
Date:          2/7/2008 3:13:51 PM
Event ID:      36
Task Category: None
Level:         Warning
Keywords:      Classic
User:          N/A
Computer:      xps-m1330-leal
Description:
The time service has not synchronized the system time for 86400 seconds because none of the time service providers provided a usable time stamp. The time service will not update the local system time until it is able to synchronize with a time source. If the local system is configured to act as a time server for clients, it will stop advertising as a time source to clients. The time service will continue to retry and sync time with its time sources. Check system event log for other W32time events for more details. Run 'w32tm /resync' to force an instant time synchronization.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Microsoft-Windows-Time-Service" Guid="{06EDCFEB-0FD0-4E53-ACCA-A6F8BBF81BCB}" EventSourceName="W32Time" />
    <EventID Qualifiers="33370">36</EventID>
    <Version>0</Version>
    <Level>3</Level>
    <Task>0</Task>
    <Opcode>0</Opcode>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2008-02-07T21:13:51.000Z" />
    <EventRecordID>14746</EventRecordID>
    <Correlation />
    <Execution ProcessID="0" ThreadID="0" />
    <Channel>System</Channel>
    <Computer>xps-m1330-leal</Computer>
    <Security />
  </System>
  <EventData Name="MSG_TIME_SOURCE_NONE">
    <Data Name="UnsynchronizedTimeSeconds">86400</Data>
  </EventData>
</Event>

Log Name:      System
Source:        Microsoft-Windows-Time-Service
Date:          2/6/2008 3:13:50 PM
Event ID:      35
Task Category: None
Level:         Information
Keywords:      Classic
User:          N/A
Computer:      xps-m1330-leal
Description:
The time service is now synchronizing the system time with the time source time.windows.com,0x9 (ntp.m|0x9|0.0.0.0:123->207.46.232.182:123).
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Microsoft-Windows-Time-Service" Guid="{06EDCFEB-0FD0-4E53-ACCA-A6F8BBF81BCB}" EventSourceName="W32Time" />
    <EventID Qualifiers="16986">35</EventID>
    <Version>0</Version>
    <Level>4</Level>
    <Task>0</Task>
    <Opcode>0</Opcode>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2008-02-06T21:13:50.000Z" />
    <EventRecordID>14509</EventRecordID>
    <Correlation />
    <Execution ProcessID="0" ThreadID="0" />
    <Channel>System</Channel>
    <Computer>xps-m1330-leal</Computer>
    <Security />
  </System>
  <EventData Name="MSG_TIME_SOURCE_CHOSEN">
    <Data Name="TimeSource">time.windows.com,0x9 (ntp.m|0x9|0.0.0.0:123-&gt;207.46.232.182:123)</Data>
  </EventData>
</Event>

Log Name:      System
Source:        Microsoft-Windows-Time-Service
Date:          2/6/2008 3:13:20 PM
Event ID:      37
Task Category: None
Level:         Information
Keywords:      Classic
User:          N/A
Computer:      xps-m1330-leal
Description:
The time provider NtpClient is currently receiving valid time data from time.windows.com,0x9 (ntp.m|0x9|0.0.0.0:123->207.46.232.182:123).
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Microsoft-Windows-Time-Service" Guid="{06EDCFEB-0FD0-4E53-ACCA-A6F8BBF81BCB}" EventSourceName="W32Time" />
    <EventID Qualifiers="16986">37</EventID>
    <Version>0</Version>
    <Level>4</Level>
    <Task>0</Task>
    <Opcode>0</Opcode>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2008-02-06T21:13:20.000Z" />
    <EventRecordID>14508</EventRecordID>
    <Correlation />
    <Execution ProcessID="0" ThreadID="0" />
    <Channel>System</Channel>
    <Computer>xps-m1330-leal</Computer>
    <Security />
  </System>
  <EventData Name="MSG_TIME_SOURCE_REACHABLE">
    <Data Name="TimeSource">time.windows.com,0x9 (ntp.m|0x9|0.0.0.0:123-&gt;207.46.232.182:123)</Data>
  </EventData>
</Event>

Log Name:      System
Source:        Microsoft-Windows-Time-Service
Date:          2/6/2008 9:38:09 AM
Event ID:      36
Task Category: None
Level:         Warning
Keywords:      Classic
User:          N/A
Computer:      xps-m1330-leal
Description:
The time service has not synchronized the system time for 86400 seconds because none of the time service providers provided a usable time stamp. The time service will not update the local system time until it is able to synchronize with a time source. If the local system is configured to act as a time server for clients, it will stop advertising as a time source to clients. The time service will continue to retry and sync time with its time sources. Check system event log for other W32time events for more details. Run 'w32tm /resync' to force an instant time synchronization.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Microsoft-Windows-Time-Service" Guid="{06EDCFEB-0FD0-4E53-ACCA-A6F8BBF81BCB}" EventSourceName="W32Time" />
    <EventID Qualifiers="33370">36</EventID>
    <Version>0</Version>
    <Level>3</Level>
    <Task>0</Task>
    <Opcode>0</Opcode>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2008-02-06T15:38:09.000Z" />
    <EventRecordID>14318</EventRecordID>
    <Correlation />
    <Execution ProcessID="0" ThreadID="0" />
    <Channel>System</Channel>
    <Computer>xps-m1330-leal</Computer>
    <Security />
  </System>
  <EventData Name="MSG_TIME_SOURCE_NONE">
    <Data Name="UnsynchronizedTimeSeconds">86400</Data>
  </EventData>
</Event>

Log Name:      System
Source:        Microsoft-Windows-Time-Service
Date:          2/1/2008 4:44:21 PM
Event ID:      36
Task Category: None
Level:         Warning
Keywords:      Classic
User:          N/A
Computer:      xps-m1330-leal
Description:
The time service has not synchronized the system time for 86400 seconds because none of the time service providers provided a usable time stamp. The time service will not update the local system time until it is able to synchronize with a time source. If the local system is configured to act as a time server for clients, it will stop advertising as a time source to clients. The time service will continue to retry and sync time with its time sources. Check system event log for other W32time events for more details. Run 'w32tm /resync' to force an instant time synchronization.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Microsoft-Windows-Time-Service" Guid="{06EDCFEB-0FD0-4E53-ACCA-A6F8BBF81BCB}" EventSourceName="W32Time" />
    <EventID Qualifiers="33370">36</EventID>
    <Version>0</Version>
    <Level>3</Level>
    <Task>0</Task>
    <Opcode>0</Opcode>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2008-02-01T22:44:21.000Z" />
    <EventRecordID>13397</EventRecordID>
    <Correlation />
    <Execution ProcessID="0" ThreadID="0" />
    <Channel>System</Channel>
    <Computer>xps-m1330-leal</Computer>
    <Security />
  </System>
  <EventData Name="MSG_TIME_SOURCE_NONE">
    <Data Name="UnsynchronizedTimeSeconds">86400</Data>
  </EventData>
</Event>

Log Name:      System
Source:        Microsoft-Windows-Time-Service
Date:          1/30/2008 3:14:13 PM
Event ID:      35
Task Category: None
Level:         Information
Keywords:      Classic
User:          N/A
Computer:      xps-m1330-leal
Description:
The time service is now synchronizing the system time with the time source time.windows.com,0x9 (ntp.m|0x9|0.0.0.0:123->207.46.232.182:123).
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Microsoft-Windows-Time-Service" Guid="{06EDCFEB-0FD0-4E53-ACCA-A6F8BBF81BCB}" EventSourceName="W32Time" />
    <EventID Qualifiers="16986">35</EventID>
    <Version>0</Version>
    <Level>4</Level>
    <Task>0</Task>
    <Opcode>0</Opcode>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2008-01-30T21:14:13.000Z" />
    <EventRecordID>13046</EventRecordID>
    <Correlation />
    <Execution ProcessID="0" ThreadID="0" />
    <Channel>System</Channel>
    <Computer>xps-m1330-leal</Computer>
    <Security />
  </System>
  <EventData Name="MSG_TIME_SOURCE_CHOSEN">
    <Data Name="TimeSource">time.windows.com,0x9 (ntp.m|0x9|0.0.0.0:123-&gt;207.46.232.182:123)</Data>
  </EventData>
</Event>

Log Name:      System
Source:        Microsoft-Windows-Time-Service
Date:          1/30/2008 3:13:20 PM
Event ID:      37
Task Category: None
Level:         Information
Keywords:      Classic
User:          N/A
Computer:      xps-m1330-leal
Description:
The time provider NtpClient is currently receiving valid time data from time.windows.com,0x9 (ntp.m|0x9|0.0.0.0:123->207.46.232.182:123).
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Microsoft-Windows-Time-Service" Guid="{06EDCFEB-0FD0-4E53-ACCA-A6F8BBF81BCB}" EventSourceName="W32Time" />
    <EventID Qualifiers="16986">37</EventID>
    <Version>0</Version>
    <Level>4</Level>
    <Task>0</Task>
    <Opcode>0</Opcode>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2008-01-30T21:13:20.000Z" />
    <EventRecordID>13045</EventRecordID>
    <Correlation />
    <Execution ProcessID="0" ThreadID="0" />
    <Channel>System</Channel>
    <Computer>xps-m1330-leal</Computer>
    <Security />
  </System>
  <EventData Name="MSG_TIME_SOURCE_REACHABLE">
    <Data Name="TimeSource">time.windows.com,0x9 (ntp.m|0x9|0.0.0.0:123-&gt;207.46.232.182:123)</Data>
  </EventData>
</Event>

Log Name:      System
Source:        Microsoft-Windows-Time-Service
Date:          1/25/2008 4:27:42 PM
Event ID:      36
Task Category: None
Level:         Warning
Keywords:      Classic
User:          N/A
Computer:      xps-m1330-leal
Description:
The time service has not synchronized the system time for 86400 seconds because none of the time service providers provided a usable time stamp. The time service will not update the local system time until it is able to synchronize with a time source. If the local system is configured to act as a time server for clients, it will stop advertising as a time source to clients. The time service will continue to retry and sync time with its time sources. Check system event log for other W32time events for more details. Run 'w32tm /resync' to force an instant time synchronization.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Microsoft-Windows-Time-Service" Guid="{06EDCFEB-0FD0-4E53-ACCA-A6F8BBF81BCB}" EventSourceName="W32Time" />
    <EventID Qualifiers="33370">36</EventID>
    <Version>0</Version>
    <Level>3</Level>
    <Task>0</Task>
    <Opcode>0</Opcode>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2008-01-25T22:27:42.000Z" />
    <EventRecordID>12135</EventRecordID>
    <Correlation />
    <Execution ProcessID="0" ThreadID="0" />
    <Channel>System</Channel>
    <Computer>xps-m1330-leal</Computer>
    <Security />
  </System>
  <EventData Name="MSG_TIME_SOURCE_NONE">
    <Data Name="UnsynchronizedTimeSeconds">86400</Data>
  </EventData>
</Event>

Log Name:      System
Source:        Microsoft-Windows-Time-Service
Date:          1/23/2008 3:13:30 PM
Event ID:      37
Task Category: None
Level:         Information
Keywords:      Classic
User:          N/A
Computer:      xps-m1330-leal
Description:
The time provider NtpClient is currently receiving valid time data from time.windows.com,0x9 (ntp.m|0x9|0.0.0.0:123->207.46.197.32:123).
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Microsoft-Windows-Time-Service" Guid="{06EDCFEB-0FD0-4E53-ACCA-A6F8BBF81BCB}" EventSourceName="W32Time" />
    <EventID Qualifiers="16986">37</EventID>
    <Version>0</Version>
    <Level>4</Level>
    <Task>0</Task>
    <Opcode>0</Opcode>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2008-01-23T21:13:30.000Z" />
    <EventRecordID>11742</EventRecordID>
    <Correlation />
    <Execution ProcessID="0" ThreadID="0" />
    <Channel>System</Channel>
    <Computer>xps-m1330-leal</Computer>
    <Security />
  </System>
  <EventData Name="MSG_TIME_SOURCE_REACHABLE">
    <Data Name="TimeSource">time.windows.com,0x9 (ntp.m|0x9|0.0.0.0:123-&gt;207.46.197.32:123)</Data>
  </EventData>
</Event>

Log Name:      System
Source:        Microsoft-Windows-Time-Service
Date:          1/23/2008 3:13:25 PM
Event ID:      134
Task Category: None
Level:         Warning
Keywords:      Classic
User:          N/A
Computer:      xps-m1330-leal
Description:
NtpClient was unable to set a manual peer to use as a time source because of DNS resolution error on 'time.windows.com,0x9'. NtpClient will try again in 15 minutes and double the reattempt interval thereafter. The error was: No such host is known. (0x80072AF9)
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Microsoft-Windows-Time-Service" Guid="{06EDCFEB-0FD0-4E53-ACCA-A6F8BBF81BCB}" EventSourceName="W32Time" />
    <EventID Qualifiers="33370">134</EventID>
    <Version>0</Version>
    <Level>3</Level>
    <Task>0</Task>
    <Opcode>0</Opcode>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2008-01-23T21:13:25.000Z" />
    <EventRecordID>11727</EventRecordID>
    <Correlation />
    <Execution ProcessID="0" ThreadID="0" />
    <Channel>System</Channel>
    <Computer>xps-m1330-leal</Computer>
    <Security />
  </System>
  <EventData Name="MSG_MANUAL_PEER_DNS_ERROR">
    <Data Name="ErrorMessage">No such host is known. (0x80072AF9)</Data>
    <Data Name="RetryMinutes">15</Data>
    <Data Name="DomainPeer">time.windows.com,0x9</Data>
  </EventData>
</Event>

Log Name:      System
Source:        Microsoft-Windows-Time-Service
Date:          1/23/2008 9:30:06 AM
Event ID:      36
Task Category: None
Level:         Warning
Keywords:      Classic
User:          N/A
Computer:      xps-m1330-leal
Description:
The time service has not synchronized the system time for 86400 seconds because none of the time service providers provided a usable time stamp. The time service will not update the local system time until it is able to synchronize with a time source. If the local system is configured to act as a time server for clients, it will stop advertising as a time source to clients. The time service will continue to retry and sync time with its time sources. Check system event log for other W32time events for more details. Run 'w32tm /resync' to force an instant time synchronization.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Microsoft-Windows-Time-Service" Guid="{06EDCFEB-0FD0-4E53-ACCA-A6F8BBF81BCB}" EventSourceName="W32Time" />
    <EventID Qualifiers="33370">36</EventID>
    <Version>0</Version>
    <Level>3</Level>
    <Task>0</Task>
    <Opcode>0</Opcode>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2008-01-23T15:30:06.000Z" />
    <EventRecordID>11720</EventRecordID>
    <Correlation />
    <Execution ProcessID="0" ThreadID="0" />
    <Channel>System</Channel>
    <Computer>xps-m1330-leal</Computer>
    <Security />
  </System>
  <EventData Name="MSG_TIME_SOURCE_NONE">
    <Data Name="UnsynchronizedTimeSeconds">86400</Data>
  </EventData>
</Event>

Log Name:      System
Source:        Microsoft-Windows-Time-Service
Date:          1/19/2008 11:13:01 AM
Event ID:      36
Task Category: None
Level:         Warning
Keywords:      Classic
User:          N/A
Computer:      xps-m1330-leal
Description:
The time service has not synchronized the system time for 86400 seconds because none of the time service providers provided a usable time stamp. The time service will not update the local system time until it is able to synchronize with a time source. If the local system is configured to act as a time server for clients, it will stop advertising as a time source to clients. The time service will continue to retry and sync time with its time sources. Check system event log for other W32time events for more details. Run 'w32tm /resync' to force an instant time synchronization.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Microsoft-Windows-Time-Service" Guid="{06EDCFEB-0FD0-4E53-ACCA-A6F8BBF81BCB}" EventSourceName="W32Time" />
    <EventID Qualifiers="33370">36</EventID>
    <Version>0</Version>
    <Level>3</Level>
    <Task>0</Task>
    <Opcode>0</Opcode>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2008-01-19T17:13:01.000Z" />
    <EventRecordID>10724</EventRecordID>
    <Correlation />
    <Execution ProcessID="0" ThreadID="0" />
    <Channel>System</Channel>
    <Computer>xps-m1330-leal</Computer>
    <Security />
  </System>
  <EventData Name="MSG_TIME_SOURCE_NONE">
    <Data Name="UnsynchronizedTimeSeconds">86400</Data>
  </EventData>
</Event>

Log Name:      System
Source:        Microsoft-Windows-Time-Service
Date:          1/17/2008 3:08:17 PM
Event ID:      36
Task Category: None
Level:         Warning
Keywords:      Classic
User:          N/A
Computer:      xps-m1330-leal
Description:
The time service has not synchronized the system time for 86400 seconds because none of the time service providers provided a usable time stamp. The time service will not update the local system time until it is able to synchronize with a time source. If the local system is configured to act as a time server for clients, it will stop advertising as a time source to clients. The time service will continue to retry and sync time with its time sources. Check system event log for other W32time events for more details. Run 'w32tm /resync' to force an instant time synchronization.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Microsoft-Windows-Time-Service" Guid="{06EDCFEB-0FD0-4E53-ACCA-A6F8BBF81BCB}" EventSourceName="W32Time" />
    <EventID Qualifiers="33370">36</EventID>
    <Version>0</Version>
    <Level>3</Level>
    <Task>0</Task>
    <Opcode>0</Opcode>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2008-01-17T21:08:17.000Z" />
    <EventRecordID>7907</EventRecordID>
    <Correlation />
    <Execution ProcessID="0" ThreadID="0" />
    <Channel>System</Channel>
    <Computer>xps-m1330-leal</Computer>
    <Security />
  </System>
  <EventData Name="MSG_TIME_SOURCE_NONE">
    <Data Name="UnsynchronizedTimeSeconds">86400</Data>
  </EventData>
</Event>

Log Name:      System
Source:        Microsoft-Windows-Time-Service
Date:          1/16/2008 3:08:17 PM
Event ID:      35
Task Category: None
Level:         Information
Keywords:      Classic
User:          N/A
Computer:      xps-m1330-leal
Description:
The time service is now synchronizing the system time with the time source time.windows.com,0x9 (ntp.m|0x9|0.0.0.0:123->207.46.197.32:123).
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Microsoft-Windows-Time-Service" Guid="{06EDCFEB-0FD0-4E53-ACCA-A6F8BBF81BCB}" EventSourceName="W32Time" />
    <EventID Qualifiers="16986">35</EventID>
    <Version>0</Version>
    <Level>4</Level>
    <Task>0</Task>
    <Opcode>0</Opcode>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2008-01-16T21:08:17.000Z" />
    <EventRecordID>7811</EventRecordID>
    <Correlation />
    <Execution ProcessID="0" ThreadID="0" />
    <Channel>System</Channel>
    <Computer>xps-m1330-leal</Computer>
    <Security />
  </System>
  <EventData Name="MSG_TIME_SOURCE_CHOSEN">
    <Data Name="TimeSource">time.windows.com,0x9 (ntp.m|0x9|0.0.0.0:123-&gt;207.46.197.32:123)</Data>
  </EventData>
</Event>

Log Name:      System
Source:        Microsoft-Windows-Time-Service
Date:          1/16/2008 3:06:40 PM
Event ID:      37
Task Category: None
Level:         Information
Keywords:      Classic
User:          N/A
Computer:      xps-m1330-leal
Description:
The time provider NtpClient is currently receiving valid time data from time.windows.com,0x9 (ntp.m|0x9|0.0.0.0:123->207.46.197.32:123).
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Microsoft-Windows-Time-Service" Guid="{06EDCFEB-0FD0-4E53-ACCA-A6F8BBF81BCB}" EventSourceName="W32Time" />
    <EventID Qualifiers="16986">37</EventID>
    <Version>0</Version>
    <Level>4</Level>
    <Task>0</Task>
    <Opcode>0</Opcode>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2008-01-16T21:06:40.000Z" />
    <EventRecordID>7810</EventRecordID>
    <Correlation />
    <Execution ProcessID="0" ThreadID="0" />
    <Channel>System</Channel>
    <Computer>xps-m1330-leal</Computer>
    <Security />
  </System>
  <EventData Name="MSG_TIME_SOURCE_REACHABLE">
    <Data Name="TimeSource">time.windows.com,0x9 (ntp.m|0x9|0.0.0.0:123-&gt;207.46.197.32:123)</Data>
  </EventData>
</Event>

Log Name:      System
Source:        Microsoft-Windows-Time-Service
Date:          1/16/2008 5:49:02 AM
Event ID:      36
Task Category: None
Level:         Warning
Keywords:      Classic
User:          N/A
Computer:      xps-m1330-leal
Description:
The time service has not synchronized the system time for 86400 seconds because none of the time service providers provided a usable time stamp. The time service will not update the local system time until it is able to synchronize with a time source. If the local system is configured to act as a time server for clients, it will stop advertising as a time source to clients. The time service will continue to retry and sync time with its time sources. Check system event log for other W32time events for more details. Run 'w32tm /resync' to force an instant time synchronization.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Microsoft-Windows-Time-Service" Guid="{06EDCFEB-0FD0-4E53-ACCA-A6F8BBF81BCB}" EventSourceName="W32Time" />
    <EventID Qualifiers="33370">36</EventID>
    <Version>0</Version>
    <Level>3</Level>
    <Task>0</Task>
    <Opcode>0</Opcode>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2008-01-16T11:49:02.000Z" />
    <EventRecordID>7629</EventRecordID>
    <Correlation />
    <Execution ProcessID="0" ThreadID="0" />
    <Channel>System</Channel>
    <Computer>xps-m1330-leal</Computer>
    <Security />
  </System>
  <EventData Name="MSG_TIME_SOURCE_NONE">
    <Data Name="UnsynchronizedTimeSeconds">86400</Data>
  </EventData>
</Event>

Log Name:      System
Source:        Microsoft-Windows-Time-Service
Date:          1/13/2008 6:49:17 PM
Event ID:      36
Task Category: None
Level:         Warning
Keywords:      Classic
User:          N/A
Computer:      xps-m1330-leal
Description:
The time service has not synchronized the system time for 86400 seconds because none of the time service providers provided a usable time stamp. The time service will not update the local system time until it is able to synchronize with a time source. If the local system is configured to act as a time server for clients, it will stop advertising as a time source to clients. The time service will continue to retry and sync time with its time sources. Check system event log for other W32time events for more details. Run 'w32tm /resync' to force an instant time synchronization.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Microsoft-Windows-Time-Service" Guid="{06EDCFEB-0FD0-4E53-ACCA-A6F8BBF81BCB}" EventSourceName="W32Time" />
    <EventID Qualifiers="33370">36</EventID>
    <Version>0</Version>
    <Level>3</Level>
    <Task>0</Task>
    <Opcode>0</Opcode>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2008-01-14T00:49:17.000Z" />
    <EventRecordID>6328</EventRecordID>
    <Correlation />
    <Execution ProcessID="0" ThreadID="0" />
    <Channel>System</Channel>
    <Computer>xps-m1330-leal</Computer>
    <Security />
  </System>
  <EventData Name="MSG_TIME_SOURCE_NONE">
    <Data Name="UnsynchronizedTimeSeconds">86400</Data>
  </EventData>
</Event>

Log Name:      System
Source:        Microsoft-Windows-Time-Service
Date:          1/11/2008 1:53:33 PM
Event ID:      36
Task Category: None
Level:         Warning
Keywords:      Classic
User:          N/A
Computer:      xps-m1330-leal
Description:
The time service has not synchronized the system time for 86400 seconds because none of the time service providers provided a usable time stamp. The time service will not update the local system time until it is able to synchronize with a time source. If the local system is configured to act as a time server for clients, it will stop advertising as a time source to clients. The time service will continue to retry and sync time with its time sources. Check system event log for other W32time events for more details. Run 'w32tm /resync' to force an instant time synchronization.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Microsoft-Windows-Time-Service" Guid="{06EDCFEB-0FD0-4E53-ACCA-A6F8BBF81BCB}" EventSourceName="W32Time" />
    <EventID Qualifiers="33370">36</EventID>
    <Version>0</Version>
    <Level>3</Level>
    <Task>0</Task>
    <Opcode>0</Opcode>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2008-01-11T19:53:33.000Z" />
    <EventRecordID>5776</EventRecordID>
    <Correlation />
    <Execution ProcessID="0" ThreadID="0" />
    <Channel>System</Channel>
    <Computer>xps-m1330-leal</Computer>
    <Security />
  </System>
  <EventData Name="MSG_TIME_SOURCE_NONE">
    <Data Name="UnsynchronizedTimeSeconds">86400</Data>
  </EventData>
</Event>

Log Name:      System
Source:        Microsoft-Windows-Time-Service
Date:          1/9/2008 3:08:19 PM
Event ID:      35
Task Category: None
Level:         Information
Keywords:      Classic
User:          N/A
Computer:      xps-m1330-leal
Description:
The time service is now synchronizing the system time with the time source time.windows.com,0x9 (ntp.m|0x9|0.0.0.0:123->207.46.197.32:123).
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Microsoft-Windows-Time-Service" Guid="{06EDCFEB-0FD0-4E53-ACCA-A6F8BBF81BCB}" EventSourceName="W32Time" />
    <EventID Qualifiers="16986">35</EventID>
    <Version>0</Version>
    <Level>4</Level>
    <Task>0</Task>
    <Opcode>0</Opcode>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2008-01-09T21:08:19.000Z" />
    <EventRecordID>1683</EventRecordID>
    <Correlation />
    <Execution ProcessID="0" ThreadID="0" />
    <Channel>System</Channel>
    <Computer>xps-m1330-leal</Computer>
    <Security />
  </System>
  <EventData Name="MSG_TIME_SOURCE_CHOSEN">
    <Data Name="TimeSource">time.windows.com,0x9 (ntp.m|0x9|0.0.0.0:123-&gt;207.46.197.32:123)</Data>
  </EventData>
</Event>

Log Name:      System
Source:        Microsoft-Windows-Time-Service
Date:          1/9/2008 3:08:13 PM
Event ID:      37
Task Category: None
Level:         Information
Keywords:      Classic
User:          N/A
Computer:      xps-m1330-leal
Description:
The time provider NtpClient is currently receiving valid time data from time.windows.com,0x9 (ntp.m|0x9|0.0.0.0:123->207.46.197.32:123).
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Microsoft-Windows-Time-Service" Guid="{06EDCFEB-0FD0-4E53-ACCA-A6F8BBF81BCB}" EventSourceName="W32Time" />
    <EventID Qualifiers="16986">37</EventID>
    <Version>0</Version>
    <Level>4</Level>
    <Task>0</Task>
    <Opcode>0</Opcode>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2008-01-09T21:08:13.000Z" />
    <EventRecordID>1682</EventRecordID>
    <Correlation />
    <Execution ProcessID="0" ThreadID="0" />
    <Channel>System</Channel>
    <Computer>xps-m1330-leal</Computer>
    <Security />
  </System>
  <EventData Name="MSG_TIME_SOURCE_REACHABLE">
    <Data Name="TimeSource">time.windows.com,0x9 (ntp.m|0x9|0.0.0.0:123-&gt;207.46.197.32:123)</Data>
  </EventData>
</Event>
0
briancassinCommented:
It looks like there may be some DNS resolution problems going on...

Try doing an nslookup of the time servers you are using from a command prompt while connected wired and then wirelessly see if you get a response.

also try pinging by name.
0
Introducing Cloud Class® training courses

Tech changes fast. You can learn faster. That’s why we’re bringing professional training courses to Experts Exchange. With a subscription, you can access all the Cloud Class® courses to expand your education, prep for certifications, and get top-notch instructions.

BlearyEyeAuthor Commented:
I called tech support; the  repair guy showed up & replaced the motherboard. Now it's keeping time ok. However, time sync still doesn't work. Ideas?

-- Bill
0
briancassinCommented:
IS it still giving time sync errors ?

try following this guide here

http://www.howtogeek.com/howto/windows-vista/dealing-with-windows-vista-time-sync-problems/
0
BlearyEyeAuthor Commented:
After replacing the motherboard & the battery, i'm now keeping time (yay). However, timesync still isn't working. I had seen the link indicated by briancassin, and have tried all the usual time sync servers. All I get is "An error occurred while Windows as synchronizing with (site)"

Ideas?
0
briancassinCommented:
Did you open the firewall in Vista to allow Port 123 UDP out and in ?

Are you using An anti virus security suite (one that comes with a firewall if so then the exception will have to made in this software) it may also be possible it is your router blocking if it has firewall capabilities you may have to go into the routers configuration and port forward port 123 to this computers IP address.
0
briancassinCommented:
0
BlearyEyeAuthor Commented:
I'm using the Win firewall. I opened the port. No joy ... from server time-nw.nist.gov to the message that "the time sample was rejected because the peer's stratum is is less than the host's stratum."
0
briancassinCommented:
If you ping time-nw.nist.gov there is no reply I don't think that time server is operating or they are rejecting ICMP

try setting it to time.nist.gov I was able to ping this with no issue

if that does not work
try also this procedure

net stop w32time
w32tm /unregister [ignore error message]
w32tm /unregister [enter a second time]
w32tm /register
reg add hklm\system\currentcontrolset\services\w32time\parameters\ /v NtpServer /t reg_sz /d time.nist.gov /f
net start w32time
w32tm /resync

And then restart.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
briancassinCommented:
The correct procedure was given for fixing this issue. The time server when I checked it during at the moment this problem was occurring was not responding.
0
BlearyEyeAuthor Commented:
seemed to be just a matter of finding a server that's responding. i wound up using mit's.
0
briancassinCommented:
Thanks for coming back to the question, glad I could help. :)
0
koilaCommented:
could you please advise on my question. my time is behind and my timezone is correct.
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows Vista

From novice to tech pro — start learning today.