Re: W32Time

Domain-joined client PCs should sync to the SBS automatically, with no configuration on your part whatsoever. XP clients will log an event indicating a successful sync when you restart them (not sure if Vista logs it or not).

To get the server to sync properly, try this:

w32tm /config /manualpeerlist:"0.pool.ntp.org 1.pool.ntp.org 2.pool.ntp.org",0x8 /syncfromflags:MANUAL
w32tm /config /update
net stop w32time
net start w32time
w32tm /resync /nowait



"Steve Wofford" <intrarely@xxxxxxxxx> wrote in message news:ul9vQ05uIHA.5448@xxxxxxxxxxxxxxxxxxxxxxx
I have tried every which way to keep our network sync via our DC (SBS 2003).

Couple Messages:

Event Log
==========
Event Type: Warning
Event Source: W32Time
Event Category: None
Event ID: 36
Date: 5/12/2008
Time: 9:52:33 PM
User: N/A
Computer: SERVER
Description:
The time service has not synchronized the system time for 86400 seconds because none of the time service providers provided a usable time stamp. The time service is no longer synchronized and cannot provide the time to other clients or update the system clock. Monitor the system events displayed in the Event Viewer to make sure that a more serious problem does not exist.

CMD
==========
"The computer did not resync because no time data was available"

Originally I created a GP and added the default Time Server Enabled settings and believe everything had worked up until a few months ago. However, now I cannot get it to sync w/ an external Time Server at all and have tried the following::

net stop w32time
w32tm /unregister [ignore error message]
w32tm /unregister [enter a second time]
w32tm /register
reg add hklm\system\currentcontrolset\services\w32time\parameters\ /v NtpServer /t reg_sz /d time.nist.gov /f
net start w32time
w32tm /resync

So I guess it would be best to start over I would like the DC to sync to an external source and the clients would sync to the DC. Correct me if I am wrong, but doesnt this happen automatically after they login?

TIA,

Steve


.

Relevant Pages

  • Re: Domain Time Syncing
    ... how do you allow your other devices to sync time? ... "The time service detected a time difference of greater than 128 ... server, but clients still can't sync to the server. ...
    (microsoft.public.windows.server.active_directory)
  • Re: Domain Time Syncing
    ... may want to start with the event logs on the clients that don't work. ... problem of why the server wasn't sync'ing with an outside source. ... see if their time will sync to the PDC. ... "The time service detected a time difference of greater than 128 ...
    (microsoft.public.windows.server.active_directory)
  • Re: Exchange clock settings/issue
    ... Your clients sync with their authenticating DC. ... the PDC emulator role, at the root of the forest. ... We use an exchanger server 2003 and all of our clients PC's ... exchange server runs 6 minutes faster than the atomic clock. ...
    (microsoft.public.exchange.admin)
  • W32Time
    ... I have tried every which way to keep our network sync via our DC. ... Event Source: W32Time ... because none of the time service providers provided a usable time stamp. ...
    (microsoft.public.windows.server.sbs)
  • Re: Domain Time Syncing
    ... problem of why the server wasn't sync'ing with an outside source. ... some member servers and clients respond positively to the "w32tm ... how do you allow your other devices to sync time? ... "The time service detected a time difference of greater than 128 ...
    (microsoft.public.windows.server.active_directory)
Loading