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

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) ?



<kbotas@xxxxxxxxxxx> wrote in message
news:1137743854.494190.266310@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
> 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: Pain in the butt w32time error
    ... The windows time service is started on the SBS, ... >> net start w32time ... >>> Time Provider NtpClient: No valid response has been received from ...
    (microsoft.public.windows.server.sbs)
  • Re: SBS 2003 Time sync problem
    ... Domain Controllers and members have a well defined time sync algorithm and ... PDCe's should be the only servers getting external time sync. ... what Les posted works excatly the same for other PDCe's (Like SBS ... net start w32time ...
    (microsoft.public.windows.server.sbs)
  • Re: SBS 2003 Time sync problem
    ... PDCe's should be the only servers getting external time sync. ... net start w32time ... Run the batch file on your SBS. ...
    (microsoft.public.windows.server.sbs)
  • Re: SBS 2003 Time sync problem
    ... PDCe's should be the only servers getting external time sync. ... net start w32time ... Run the batch file on your SBS. ... You can replace the time server ...
    (microsoft.public.windows.server.sbs)
  • Re: Time Server Question
    ... net start w32time ... What I want is for the SBS box to go out and get time from an external ... from the external source as it is trying to get time from itself. ... I'm sure I'm messing up a GPO somewhere but I can't narrow it down. ...
    (microsoft.public.windows.server.sbs)