Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations wOOdy-Soft on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

W32time

Status
Not open for further replies.

briteeyez

IS-IT--Management
Nov 26, 2001
194
EC
Hi

I am constantly logging the errors 54 and 64 in the my event viewer on my domain controller.

Event ID: 64
Description 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.

Event ID: 54
Description The Windows Time Service was not able to find a Domain Controller. A time and date update was not possible.


Why is this and what do I have to do to ensure it doesn't occur again.
 
I am running in a Windows 2000 Server environment.
 
You could always go to the services and change the startup of W32TIME from automatic to manual.
 
"Windows 2000 computers are attempting to synchronize their time with a domain controller. If none is found this message is generated. The domain controller must run the w32time service. This service can be syncronized with an external source (ie.atomic clocks like the one maintained by Navy Observatory). A syncronized time is very important for Active Directory implemenations due to its distributed nature".

Check out this link to see how to configure your time server



Hope this helps,

Patty [ponytails2]
 
Hi Patti

I read the document which you advised me to read and it is very informative. I only have one question for you to clarify things.

I understand the the Root DC in the forest has to be synchronized with an external time source in order to stop this warning. However in reading your doucment it stated that manual configuration - using the net time dos command, could compromise network securtiy and hence disrupt certain services like file and print sharing. What are your views on this.

Furthermore am I correct in the order of using these commands.

net time /setsntp:ntp2.usno.navy.mil
net stop w32time
w32tm -s
net start w32time




 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top