Re: W32time event id 36
- From: Unk <not@xxxxxxx>
- Date: Tue, 10 Jan 2006 20:34:41 -0500
On Tue, 10 Jan 2006 15:28:04 -0800, Louis Rost <junkie123ATlonepineDOTcom@> wrote:
>On an irregular basis I get the subject message logged in event
>viewer. The text of the message is:
>
>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.
>
>The event occurs in intervals ranging from less than 24 hours to as
>long as 5 days. It occurs on 3 systems, 2 XP home w/SP2 and 1 XP pro
>w/ SP2, networked using a workgroup. The 3 systems are configured to
>update the clock via the internet every 7 days and that function works
>as a message is logged in the event viewer when the clocks are
>updated.
>
>I've read the supporting documentation in help and support about this
>message but find no indication of network problems prior to or after
>this event is logged. My systems are currrent relative to fixes
>provided by Microsoft. I've scanned the systems using Spybot,
>Ad-Aware, CWShredder and HijackThis and found no indications of
>problems.
>
>Thanks, Lou.
Try setting the service up anew:
1. Start->Run-> cmd.exe
2. net stop w32time
3. w32tm.exe /unregister
4. w32tm.exe /register
5. net start w32time
Note spellings w32tm and w32time in different commands
Use all 5 steps regardless of any error messages
.
- Follow-Ups:
- Re: W32time event id 36
- From: Louis Rost
- Re: W32time event id 36
- Prev by Date: Re: Installshield Update Manager
- Next by Date: Re: How to *keep* connected my 'dial-up' connection
- Previous by thread: Re: W32time event id 36
- Next by thread: Re: W32time event id 36
- Index(es):
Relevant Pages
|
