|T O P I C R E V I E W
||Posted - 04/19/2011 : 1:08:57 PM
For the past few weeks SBS 2003 has not synced with an external time source. The error message I receive is:
Event Type: Warning
Event Source: W32Time
Event Category: None
Event ID: 50
Time: 3:28:05 PM
The time service detected a time difference of greater than 128 milliseconds for 90 seconds. The time difference might be caused by synchronization with low-accuracy time sources or by suboptimal network conditions. The time service is no longer synchronized and cannot provide the time to other clients or update the system clock. When a valid time stamp is received from a time service provider, the time service will correct itself.
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
I use the following as the time source: pool.ntp.org
I configured using the following at the command prompt:
- w32tm /config /manualpeerlist:pool.ntp /syncfromflags:manual /reliable:yes
- w32tm /config /update
- net stop w32time && net start net 32time
- w32tm /resync /rediscover
If I don't run the resync command every couple of days the time never syncs.
|8 L A T E S T R E P L I E S (Newest First)
||Posted - 04/23/2011 : 2:10:13 PM
No changes on the firewall. Until recently it's been syncing fine without port 123 open on the external firewall. I just opened it and will see what happens.
||Posted - 04/23/2011 : 12:10:53 PM
No firewall changes? Needs port 123 TCP.
||Posted - 04/20/2011 : 12:03:15 PM
I'll change it this afternoon, and let you know.
||Posted - 04/20/2011 : 03:05:15 AM
Hmm. This looks like default, except for announceflags. This should be set to 10 (0xA). Worth trying, I think. If it doesn't help the next step would be to enable logging.
||Posted - 04/19/2011 : 4:39:50 PM
Here's the registry key
||Posted - 04/19/2011 : 3:08:44 PM
Let's take a closer look then. Can you dump HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\W32Time\Config, and post it?
||Posted - 04/19/2011 : 2:50:20 PM
Just checked,no policies are applied.
||Posted - 04/19/2011 : 2:29:18 PM
Looks like you may have non-default tuning of w32time. Any policies applied?