Re: W32Time Event Type: Warning

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

You may periodically receive this warning. I wouldn't worry too much about.
I believe the computer's internal clock still displays the correct time
until the servers finally synchronize.

Drew

"BoazBoaz" <pasternak5@xxxxxxxxxxxx> wrote in message
news:emELtFAeGHA.3952@xxxxxxxxxxxxxxxxxxxxxxx
'Update Now' is working fine !!!



"Drew Tognola" <kinggungi@xxxxxxxxx> wrote in message
news:%238KNSCAeGHA.1272@xxxxxxxxxxxxxxxxxxxxxxx
BoazBoaz,

Double-click the clock > select the 'Internet Time' tab. Swith the server
by using the drop menu, click 'Update Now'. Try both servers. You may
receive an error, try again. Still receiving the warning? By the way,
this is not unusual.

Drew

"BoazBoaz" <pasternak5@xxxxxxxxxxxx> wrote in message
news:uJsRQs$dGHA.4720@xxxxxxxxxxxxxxxxxxxxxxx
What can I do with that such events ??

I did see this article http://support.microsoft.com/?id=832936 but the
resolution is not relevant because I'm XP SP2 with all recommended
update !!!

===========================================================================================================
Event Type: Warning
Event Source: W32Time
Event Category: None
Event ID: 36
Date: 5/14/2006
Time: 10:52:56 PM
User: N/A
Computer: BOAZ-202ILHWJ43
Description:
The time service has not been able to synchronize the system time for
49152 seconds because none of the time providers has been able to
provide a usable time stamp. The system clock is unsynchronized.

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
===========================================================================================================







.

Relevant Pages

  • Re: W32Time Event Type: Warning
    ... I believe the computer's internal clock still displays the correct ... time until the servers finally synchronize. ... Double-click the clock> select the 'Internet Time' tab. ...
    (microsoft.public.windowsxp.general)
  • Re: synchronization
    ... At the maximum slew rate of 500 parts per million, it will take several hours to bring your clock into synchronization. ... ntpd should set the clock unconditionally at startup; e.g. it should query the servers to find out what time it is and then set your clock to that time. ... Look for servers near you in geographical space and test them for nearness in net space (low round trip delays). ...
    (comp.protocols.time.ntp)
  • Re: synchronization
    ... At the maximum slew rate of 500 parts per million, it will take several hours to bring your clock into synchronization. ... ntpd should set the clock unconditionally at startup; e.g. it should query the servers to find out what time it is and then set your clock to that time. ... All the public stratum 1 servers are generally loaded to the breaking point and should be avoided if possible. ... Look for servers near you in geographical space and test them for nearness in net space (low round trip delays). ...
    (comp.protocols.time.ntp)
  • Re: ntpq times out if NMEA refclock configured?
    ... I'm trying to add a GPS refclock to my server. ... clock, I'm now using a Garmin GPS25 and the NMEA refclock. ... Running minicom at 4800 Baud with NTPD stopped shows the GPS serial data ... The servers appear to have wildly differing opinions as to what time it is. ...
    (comp.protocols.time.ntp)
  • Re: ntpq times out if NMEA refclock configured?
    ... I'm trying to add a GPS refclock to my server. ... clock, I'm now using a Garmin GPS25 and the NMEA refclock. ... correct of -495.9 PPM is on the ragged edge of the 500 PPM limit. ... Your servers should, ideally, be close to you in net space. ...
    (comp.protocols.time.ntp)