W32Time ID 50 on Windows 2003 Server

  • Thread starter Thread starter The poet
  • Start date Start date
T

The poet

Guest
Hi all,

I've 2 machines with Windows 2003 Server Enterprise Edition R2 (Engliah
version) SP2, up and running from few days, one is a DC (and hold the PDC
Emulator role), the other is a Exchange Server (Exchange Server 2003 SP1).
In both machines I see this warning in the event log:

Source: W32Time
Category: None
Type: Warning
Event ID: 50
Description:
The time service detected a time difference of greater than 5000
milliseconds for 900 seconds. The time difference might be caused by
synchronization with low-accuracy time sources or by suboptimal network
conditions. The time service is no longer synchronized and cannot provide
the time to other clients or update the system clock. When a valid time
stamp is received from a time service provider, the time service will
correct itself.

I've found the following KB:
http://support.microsoft.com/kb/830092

Wich says to get the latest service pack or to obtain an hotfix, the hotfix
(i.e. the w32time.dll file) has this version:

Windows Server 2003, x86-based versions
Date Time Version Size File name
------------------------------------------------------
31-Jan-2004 02:15 5.2.3790.125 221,696 W32time.dll

but my system has this version
5.2.3790.3959

wich is newer (I guess).
Any ideas?
 
Re: W32Time ID 50 on Windows 2003 Server


Ensure that your PDC is syncrhonizing time with an authoratitive external source.

- Duelund

"The poet" <software-livquist@3techsrl.com> wrote in message news:Oms1K96QIHA.5524@TK2MSFTNGP05.phx.gbl...
> Hi all,
>
> I've 2 machines with Windows 2003 Server Enterprise Edition R2 (Engliah version) SP2, up and running from few days, one is a DC
> (and hold the PDC Emulator role), the other is a Exchange Server (Exchange Server 2003 SP1). In both machines I see this warning
> in the event log:
>
> Source: W32Time
> Category: None
> Type: Warning
> Event ID: 50
> Description:
> The time service detected a time difference of greater than 5000
> milliseconds for 900 seconds. The time difference might be caused by
> synchronization with low-accuracy time sources or by suboptimal network
> conditions. The time service is no longer synchronized and cannot provide
> the time to other clients or update the system clock. When a valid time
> stamp is received from a time service provider, the time service will
> correct itself.
>
> I've found the following KB:
> http://support.microsoft.com/kb/830092
>
> Wich says to get the latest service pack or to obtain an hotfix, the hotfix (i.e. the w32time.dll file) has this version:
>
> Windows Server 2003, x86-based versions
> Date Time Version Size File name
> ------------------------------------------------------
> 31-Jan-2004 02:15 5.2.3790.125 221,696 W32time.dll
>
> but my system has this version
> 5.2.3790.3959
>
> wich is newer (I guess).
> Any ideas?
>
>
 
Re: W32Time ID 50 on Windows 2003 Server

Bjarne Duelund wrote:
> Ensure that your PDC is syncrhonizing time with an authoratitive
> external source.
> - Duelund
>

My PDC is syncronizing with two external NTP server (italian NTP server wich
are available, I've checked), and I've set the type of Time Server in the
registry to "NTP"
 
Back
Top