Learn how to a build a cloud-first strategyRegister Now

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 2914
  • Last Modified:

Time warnings in System EventLog

Hi,

I get warnings in my event log about the time, here are the warnings.

W32Time - " 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.  "

W32Time - " 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 is no longer synchronized and cannot provide   the time to other clients or update the system
clock. Monitor the   system events displayed in the Event  Viewer to make sure that a more   serious
problem does not exist.   "

What should I do?

Cheers,
IceRaven
0
IceRaven
Asked:
IceRaven
  • 4
  • 3
1 Solution
 
JamesDSCommented:
IceRaven
You don't say if your machine is a DC or member server.

If it's a DC then bahave as if its a member server (below) if it's a PDC Emulator then make sure you allow port 123TCP/UDP outbound and configure the external microsoft time service by entering this at the command line
NET TIME /SETSNTP:time.windows.com

If it's NOT A PDCE:

Members of the Active Directory sync with their local DC (local as in local AD site). The DCs then sync with the PDCEmulator, so the PDCE is the root of all time - as it were!

Diagnosis of timesync errors is difficult but I would not use NET TIME /SETSNTP: (as suggest to many questions like this one, unless it's a PDCE), as it sepcifically overrides the natural internal operation of the time service within Active Directory.

These commands are written for Windows 2003 and Windows XP. There are some equivalents for windows 2000, use W32tm /? or W32Time /? from the command line to look for alternatives on older OSs.

Use NET TIME /SETSNTP:
to clear any entry and return to the default settings

Use NET TIME /SET /YES
to synch NOW with your authenticating DC and begin the diagnosis:

Start by verifying your domain is synching AD by using REPLMON.EXE in the support tools pack on the Windows installation CD.


If this is OK then run this from the command line:
W32TM /monitor

to ensure that each member server/workstation is actually pointing to a DC.

If this is OK then run this from the command line:
W32TM /resync /rediscover

followed by:
W32TM /resync /nowait

and check the system eventlog for W32TIME errors. This process does a full reset and recheck of the time system as it relates to one member machine on your AD.

Post any errors here


Cheers

JamesDS
0
 
IceRavenAuthor Commented:
Hi JamesDS,

The Server is a DC.  I am not sure if PDC Emulation is installed by default in a native mode domain or not? How can I tell? Do I still need those portsa open?  The server is the Root Domain controller, mainly because it is the only DC :)

With this new information about the server what should I do about time?

Cheers,
Ice Raven.



0
 
JamesDSCommented:
IceRaven
PDCE is a FSMO role and all AD domains have one.

If you only have one DC then it will host all 5 FSMO roles, including the PDCE

Given that, it should be synching externally: NET TIME /SETSNTP:time.windows.com
and everything else should be synced to it with the rest of the notes I provided.

Cheers

JamesDS
0
Concerto Cloud for Software Providers & ISVs

Can Concerto Cloud Services help you focus on evolving your application offerings, while delivering the best cloud experience to your customers? From DevOps to revenue models and customer support, the answer is yes!

Learn how Concerto can help you.

 
IceRavenAuthor Commented:
The command completed succesfully and generated no information or errors in the event log.  However the time is still incorrect on the server.  How often does the DC sync time?  Is there a way to force a sync?

Cheers,
Ice Raven
0
 
JamesDSCommented:
IceRaven

Timesync works as follows:

If the local clock time of the client is behind the current time received from the time server, W32Time will change the local clock time immediately.
If the local clock time of the client is more than three minutes ahead of the time on the time server, W32Time will change the local clock time immediately.
If the local clock time of the client is less than three minutes ahead of the time on the server, W32Time will quarter or halve the clock frequency for long enough to bring the clocks into sync. If the client is less that 15 seconds ahead, it will halve the frequency; otherwise, it will quarter the frequency. The amount of time the clock spends running at an unusual frequency depends on the size of the offset that is being corrected.

W32Time will periodically check its local time with the current time by connecting to the time source. This process starts as soon as the service turns on during system start-up. W32Time attempts synchronization every 45 minutes until the clocks have successfully synchronized three times. When the clocks are correctly synchronized, W32Time then synchronizes at eight-hour intervals, unless there is a failure to obtain a timestamp, or a validation failure. If there is a failure, the process starts over from the beginning.

Set it by hand as close as you can and then simply leave it to sort itself out.

Cheers

JamesDS
0
 
IceRavenAuthor Commented:
That is some great information.  I restarted the service and Ta Dah!  Instant right time!

Cheers,
Ice Raven
0
 
JamesDSCommented:
IceRaven
Glad I could help

Timesync can be a bitch and it's not that obvious how it works

Cheers

JamesDS
0

Featured Post

Independent Software Vendors: We Want Your Opinion

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

  • 4
  • 3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now