Discussion Locked

Eventlog system log error

0 helpful
3 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

One of our server shows error in System log in a eventlog. Error is "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. "

I execute w32tm/s command in dos prompt. After executing this command also generating same error.

What is the solution for this problem?

3 replies

by mws consulting

Without server resyncronization, your users will begin to log in with incorrect creditials and out of date access privileges.

What to check
~~~~~~~~~~~~~
You will have to check to see if your trust relationship between your 'Primary' domain controller (server) and 'Backup' domain controller. To do this open Server Manager on the 'Primary' domain controller and try to syncronize the problem backup server with the primary domain controller. If this fails, you should recreate the trust relationship between the two servers.

Rename the problem server.
~~~~~~~~~~~~~~~~~~~~~~~~~~
The easiest way is to rename the backup domain controller and ensure that you are logged in as the administrator so the new account can be created on the Primary domain controller.

Once the new account is created for the backup controller, delete the old backup controller entry in Server Manager on the Primary domain controller and rename the backup domain controller back to the original name.

That's should help.

Michael Smith

This discussion is closed to new replies.