w32time and me. How important are these errors?
My server had time errors, my workstations have time errors...
How important is this? It seems that the only solution to these problems is to hack up the registry on every single machine.
What happens if I allow these errors to continue?
Is there any easy way to fix these things without editing 40 or so lines in the registry of every computer?
How important is this? It seems that the only solution to these problems is to hack up the registry on every single machine.
What happens if I allow these errors to continue?
Is there any easy way to fix these things without editing 40 or so lines in the registry of every computer?
Noam_Kuilboer
What are the errors ?
You can set time settings through GPO's and Login Scripts So no you probably will not have to touch every machine.
ASKER
On the workstations (XP):
Event Type: Warning
Event Source: W32Time
Event Category: None
Event ID: 36
Date: 29/12/2008
Time: 9:58:33 AM
User: N/A
Computer: SPARE
Description:
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.
For more information, see Help and Support Center at http://go.microsoft.com/fw
On the server (2003 Standard):
Event Type: Error
Event Source: W32Time
Event Category: None
Event ID: 29
Date: 12/18/2008
Time: 3:14:45 AM
User: N/A
Computer: IFL-SERVER
Description:
The time provider NtpClient is configured to acquire time from one or more time sources, however none of the sources are currently accessible. No attempt to contact a source will be made for 15 minutes. NtpClient has no source of accurate time.
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
and
Event Type: Error
Event Source: W32Time
Event Category: None
Event ID: 17
Date: 12/18/2008
Time: 3:14:45 AM
User: N/A
Computer: IFL-SERVER
Description:
Time Provider NtpClient: An error occurred during DNS lookup of the manually configured peer 'tock.usno.navy.mil'. NtpClient will try the DNS lookup again in 15 minutes. The error was: No such service is known. The service cannot be found in the specified name space. (0x8007277C)
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Event Type: Warning
Event Source: W32Time
Event Category: None
Event ID: 36
Date: 29/12/2008
Time: 9:58:33 AM
User: N/A
Computer: SPARE
Description:
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.
For more information, see Help and Support Center at http://go.microsoft.com/fw
On the server (2003 Standard):
Event Type: Error
Event Source: W32Time
Event Category: None
Event ID: 29
Date: 12/18/2008
Time: 3:14:45 AM
User: N/A
Computer: IFL-SERVER
Description:
The time provider NtpClient is configured to acquire time from one or more time sources, however none of the sources are currently accessible. No attempt to contact a source will be made for 15 minutes. NtpClient has no source of accurate time.
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
and
Event Type: Error
Event Source: W32Time
Event Category: None
Event ID: 17
Date: 12/18/2008
Time: 3:14:45 AM
User: N/A
Computer: IFL-SERVER
Description:
Time Provider NtpClient: An error occurred during DNS lookup of the manually configured peer 'tock.usno.navy.mil'. NtpClient will try the DNS lookup again in 15 minutes. The error was: No such service is known. The service cannot be found in the specified name space. (0x8007277C)
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
here's more info, as well...
http://technet.microsoft.com/en-us/library/cc773263.aspx
I really don't think that Time Sync is going to make or break your system though.
http://technet.microsoft.com/en-us/library/cc773263.aspx
I really don't think that Time Sync is going to make or break your system though.
ASKER
what time source should I use?
Try the navel obeservatory ntp.usno.navy.mil or 192.5.41.42
I run this script on my main DC to sync nightly.
net stop w32time
net time /setsntp:"192.5.41.209"
net start w32time
net stop w32time
net time /setsntp:"192.5.41.209"
net start w32time
There's a couple different ways to do it, either internal or external. Check the information in this article..
http://support.microsoft.com/kb/314054
http://support.microsoft.com/kb/314054
ASKER
ok, tried it out. Will see if I get an error tomorrow.
ASKER
Still getting these errors.
Make sure your Firewall / Router allows NTP traffic