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

  • Thread starter Thread starter kbotas
  • Start date Start date
K

kbotas

Hi!

A need a little help. A like to sync. the time of our clients, but i
can't.
We have SBS2000 server, and XP/2000 clients.

(A dont want to give admin priv. to our users.)

I hope u know a command, or anything else to force the client to get
new time from the server.

Tnx
 
If the clients are joined to the domain then they should already be
doing time sync with (one of) the domain controllers.
If you want to do a one-time sync to the defined time server use
w32tm /once
(do this inside a cmd window so you can read back through what
it did and whether it was doing DC locate to find time source)
You can use the net time command to see current config of ntp server
net help time
 
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...
 
Was that w32tm output from a run on the SBS DC ??
I ask as I am confused by its "PDC" response to doing GetRole
Usually one sees it saying it is an member and then going into
discovery of DC of its domain, etc. then the time sync.
Also, the failure to bind to NIC is not good.

Is your DNS zone for the domain healthy ??
One way to find out this (and more), is to, on the SBS DC,
do a start/run cmd and enter
netdiag
and look for failures.

Are the client machines configured to use ONLY the SBS DC
as their DNS server (in clients' Tcp/Ip config) ?
 
Roger!

The clients use 3 DNS but the first DNS name is the SBS DC.

I tried to run NETDIAG command, but > the system dont recognized
netdiag name as inside or outside command, program or batchfile....

Where can i find this netdiag.exe (com, etc..) ?
 
IIR netdiag is part of the "support tools" and you will find a folder
by the same name on the install CD - - - however, go to the
microsoft.com/downloads site and see if you can find a more
up-to-date version as it gets re-released when service packs
come out.

All machines that are within a domain should never, not ever,
use any DNS server that does not have ability to resolve names
in the DNS zone used for that AD. In the vast majority of AD
deployments this mean no machine should ever use a DNS
service that is not on a DC of the forest. Using an external
DNS in the Tcp/Ip settings WILL cause problems.

Roger
 
Back
Top