Re: -- force clients to get time from the server --

Roger!

Tnx for your answ. The clients are joined to the domain, but they
don't do time sync. at all. (i think).
For exm. >the server time is : 8:18
the client time is: 8:07, other clients 8:11, other
8:18

So, i try the command, what u said (w32tm), but ... nothing. Before i
used this cmd. i set a client to ((server time)-15min), then run the
command, but nothing changed.

W32Time: BEGIN:InitAdjIncr
W32Time: Adj 156250 , Incr 156250 fAdjust 0
W32Time: END:Line 2503
W32Time: BEGIN:TsUpTheThread
W32Time: END Line 1407
W32Time: TimeMMInit()
W32Time: Kernel timer : using default maximum resolution
W32Time: MaximumTime = 156250
W32Time: CurrentTime = 156250
W32Time: Timer calibrated, looped 1 times
W32Time: BEGIN:InitTmCfg
W32Time: END:Line 807
W32Time: BEGIN:InitTmCli
W32Time: END:Line 2596
W32Time: BEGIN:InitTmData
W32Time: END:Line 2618
W32Time: AvoidTimeSyncOnWan 0
W32Time: BEGIN:CMOSSynchSet
W32Time: Setting adjustment 156250 - Bool 0
W32Time: BEGIN:SetTSTimeRes
W32Time: END:Line 1295
W32Time: END:Line 864
W32Time: BEGIN:InitializeDC
W32Time: BEGIN:GetRole
W32Time: Role is 'PDC'
W32Time: END Line 672
W32Time: BEGIN:FetchParentDomainName
W32Time: NetLogonGetTimeServiceParentDomain() returned 54b with
ptr 0
W32Time: END:Line 782
W32Time: END:Line 704
W32Time: Server: Binding to 1 NIC.
W32Time: bind failed: 0x80072740
W32Time: Logging event 0xC0000031. 15 min until this event is allowed
again.
W32Time: 0xC0000031 reported to System Log in Event Viewer
W32Time: BEGIN:FinishCleanup
W32Time: BEGIN:TsUpTheThread
W32Time: END Line 1407
W32Time: BEGIN:UnInitializeDC
W32Time: Ptrs 0 - 0
W32Time: END:Line 727
W32Time: Time service stopped.
W32Time: END:Line 407

sould this help for ya...

.

Relevant Pages

  • Re: domain time server
    ... No problem Julian, that's why we're here, to share the knowledge. ... agree that w32time is probably more ellegant that a "command-line hack", ... >> And I'm sorry to correct you Julian but NET TIME is not used only to set ... The NET TIME /SETSNTP command does have the same ...
    (microsoft.public.isaserver)
  • Re: time synch problem
    ... Type the following command and then press ENTER: ... net start w32time ... Should look similar like this,a the end you see the actual time server: ... the "reliable" time source instead of assuming its the PDC? ...
    (microsoft.public.windows.server.active_directory)
  • Re: time synch problem
    ... Type the following command and then press ENTER: ... net start w32time ... AD, and effectively the PDC. ... Should look similar like this,a the end you see the actual time server: ...
    (microsoft.public.windows.server.active_directory)
  • Re: time synch problem
    ... net start w32time ... You can also check the following registry key on each DC: ... Type the following command and then press ENTER: ... the "reliable" time source instead of assuming its the PDC? ...
    (microsoft.public.windows.server.active_directory)
  • Re: Domain time - clients not synching with DC
    ... Check out this command at the clients: ... net start w32time ... Also make sure that you only use domain internal DNS servers. ... Should the clients update their time automatically with the DC ...
    (microsoft.public.windows.server.general)