Time Synchronization

EMcGrath_at_HCA_NOSPAM_Vendor.com
Date: 11/15/04


Date: Mon, 15 Nov 2004 11:23:02 -0800

Event Type: Warning
Event Source: w32time

My network will not sychc. correctly. I am reading the following error in
my event logs. What can I do to resolve this?

Because of repeated network problems, the time service has not been able to
find a domain controller to synchronize with for a long time. To reduce
network traffic, the time service will wait 960 minutes before trying again.
No synchronization will take place during this interval, even if network
connectivity is restored. Accumulated time errors may cause certain network
operations to fail. To tell the time service that network connectivity has
been restored and that it should resynchronize, execute "w32tm /s" from the
command line.



Relevant Pages

  • Re: Users cannot log onto local Workstation, when connection is lost to the PDC
    ... > If the Satellite office loses the connect to the PDC, ... > Because of repeated network problems, the time service has not been ... > able to find a domain controller to synchronize with for a long time. ...
    (microsoft.public.win2000.active_directory)
  • Re: Time server
    ... How to Synchronize an Internal Time Server with an External Source ... which provides the NIST Network Time service. ... > I have tried to syncronise the DC with the correct time, ...
    (microsoft.public.windows.server.active_directory)
  • RE: w32time.dll
    ... that the attempts to contact a time server have not succeeded recently. ... time service needs port 123 open between the client and the time server. ... >Because of repeated network problems, the time service has not been able to ... >find a domain controller to synchronize with for a long time. ...
    (microsoft.public.win2000.security)
  • Timesync probs
    ... Event Source: w32time ... The Windows Time Service was not able to find a Domain Controller. ... network traffic, the time service will wait 960 minutes before trying again. ...
    (microsoft.public.windows.server.active_directory)
  • w32Time
    ... have two 2003 Servers as DCs and two NT BDCs. ... The time service detected a time difference of greater ... Because of repeated network problems, ... No synchronization will take place during ...
    (microsoft.public.windows.server.general)

Quantcast