Time service has 86400 seconds without solving the problem with system time synchronization

Sometimes you will find some sources in the Win2003 system log: W32Time, event ID: 36, event description:

Time service has 86400 seconds without synchronization with system time, because there is no time service The provider provides a timestamp that is available. The time service will no longer be synchronized, nor will it provide time or update the system clock for other clients. Check the system events displayed in the Event Viewer to confirm that no more serious problems have occurred.

This is a warning event. Although it does not have much impact on the use of the system, why is the system default update cycle different from the event log report? Seeing such a warning, the yellow exclamation mark is also very troublesome. In fact, the time synchronization update frequency of WinXP and Win2003 system defaults to 7 days. For WinXP system, this frequency is normal, but it seems to be a bit long for Windows 2003, which requires relatively high time accuracy. In addition, each The yellow exclamation mark, which always reports this warning every other day, is also very troublesome. So for the Win2003 system, you can try to set the time synchronization interval to a smaller value, such as one day, so that the time accuracy is higher and the number of system log reports can be reduced.

You can change the time synchronization interval setting by modifying the registry. Detailed setup tutorial can be found in "Windows 2003 Server Time Synchronization Interval Modify"