Re: w32tm will not synch on SBS 2000 server

From: D Carroll (dec@gulloil.com)
Date: 04/02/03


From: "D Carroll" <dec@gulloil.com>
Date: Tue, 1 Apr 2003 15:34:24 -0800


Just did some experimenting. Got the same response as you when trying to
connect to nist1.datum.com
Used IP address instead, as in 'net time /setsntp:66.243.42.21'
This worked!
So there is probably a DNS issue here.
- Dave
"Gus CS" <anguscs@bigpond.com> wrote in message
news:eev#YTo9CHA.2520@TK2MSFTNGP11.phx.gbl...
> All
>
> I have set up my SBS server to synchronise with internet Time servers, and
> am using the server as an internal timeserver for my domain. however I
> cannot get it to actually synchronise. I believe it may have something to
> do with the ISA server, however, I have the NTP protocol allowed and
cannot
> understand why. I have pasted in below a copy of a command dpromt session
> where I test the configuration. Having stopped the service I check the
> server list, and then use w32tm to check the server can communicate with a
> server from the list. This all goes very well. It only falls apart when
I
> try to actually synchronise. having run w32tm -once in the verbose mode
it
> fails to synch and then stops. The line that concerns me is the
>
> W32Time: Time Out occured in sockets
>
> I cannot get it to work, and it is annoying me. Can anyone help?
>
> Yours Angus CS
>
>
>
>
> C:\>net stop w32time
> The Windows Time service is stopping.
> The Windows Time service was stopped successfully.
>
>
> C:\>net time /querysntp
> The current SNTP value is:
>
nist1.datum.com,time.datum.com,augean.eleceng.adelaide.edu.au,time.nist.gov,
> ntp
> .pipex.net,swisstime.ethz.ch
>
> The command completed successfully.
>
>
> C:\>w32tm -source -v
> W32Time: BEGIN:InitAdjIncr
> W32Time: Adj 100144 , Incr 100144 fAdjust 0
> W32Time: END:Line 2503
> W32Time: BEGIN:TsUpTheThread
> W32Time: END Line 1407
> W32Time: TimeMMInit()
> W32Time: Kernel timer : using default maximum resolution
> W32Time: MaximumTime = 100144
> W32Time: CurrentTime = 100144
> 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: ntpserver -
>
nist1.datum.com,time.datum.com,augean.eleceng.adelaide.edu.au,time.nist.gov,
> ntp0.pipex.net,swisstime.ethz.ch
> W32Time: BEGIN:CMOSSynchSet
> W32Time: Setting adjustment 100144 - 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 2 NICs.
> W32Time: Advertising that I'm a Time Service Provider
>
> C:\>w32tm -once -v
> W32Time: BEGIN:InitAdjIncr
> W32Time: Adj 100144 , Incr 100144 fAdjust 0
> W32Time: END:Line 2503
> W32Time: BEGIN:TsUpTheThread
> W32Time: END Line 1407
> W32Time: TimeMMInit()
> W32Time: Kernel timer : using default maximum resolution
> W32Time: MaximumTime = 100144
> W32Time: CurrentTime = 100144
> 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: ntpserver -
>
nist1.datum.com,time.datum.com,augean.eleceng.adelaide.edu.au,time.nist.gov,
> ntp0.pipex.net,swisstime.ethz.ch
> W32Time: BEGIN:CMOSSynchSet
> W32Time: Setting adjustment 100144 - 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 2 NICs.
> W32Time: Advertising that I'm a Time Service Provider
> W32Time: timeBeginPeriod: setting resolution 9
> W32Time: BEGIN:TimeSync
> W32Time: BEGIN:FGetType
> W32Time: END Line 254
> W32Time: BEGIN:FDoTimeNTPType
> W32Time: BEGIN:ChooseNTPServer
> W32Time: END Line 2178
> W32Time: BEGIN:GetSocketForSynch
> W32Time: NTP: ntpptrs[0] - NIST1.DATUM.COM
> W32Time: rgbNTPServer NIST1.DATUM.COM
> W32Time: Port Pinging to - 123
> W32Time: Connecting to "NIST1.DATUM.COM" (66.243.43.21)
> W32Time: END:Line 1170
> W32Time: BEGIN:GetDefaultRid
> W32Time: END Line 2359
> W32Time: BEGIN:ComputeDelay
> W32Time: BEGIN:NTPTry -- init
> W32Time: END Line 1683
> W32Time: BEGIN:NTPTry -- try
> W32Time: BEGIN:ComputeInterval
> W32Time: END Line 2479
> W32Time: Sending to server 48 bytes...
> W32Time: BEGIN:TsUpTheThread
> W32Time: END Line 1407
> W32Time: NTP(S): waiting for datagram...
> W32Time: BEGIN:TsUpTheThread
> W32Time: END Line 1407
> W32Time: NTP(S): waiting for datagram...
> W32Time: NTP: didn't receive datagram
> W32Time: Logging event 0x8000000B. 15 min until this event is
> allowed again.
> W32Time: 0x8000000B reported to System Log in Event Viewer
> W32Time: END Line 1951
> W32Time: Time source failed to produce usable timestamp.
> W32Time: BEGIN:NTPTry -- fail
> W32Time: END Line 1683
> W32Time: Time Out occured in sockets
> W32Time: BEGIN:NTPTry -- try
> W32Time: BEGIN:ComputeInterval
> W32Time: END Line 2479
> W32Time: Sending to server 48 bytes...
> W32Time: NTP: didn't receive datagram
> W32Time: Rejecting logging event 0x8000000B. 894 sec until
this
> event is allowed.
> W32Time: END Line 1951
> W32Time: Time source failed to produce usable timestamp.
> W32Time: BEGIN:NTPTry -- fail
> W32Time: END Line 1683
> W32Time: Time Out occured in sockets
> W32Time: BEGIN:NTPTry -- try
> W32Time: BEGIN:ComputeInterval
> W32Time: END Line 2479
> W32Time: Sending to server 48 bytes...
> W32Time: NTP: didn't receive datagram
> W32Time: Rejecting logging event 0x8000000B. 889 sec until
this
> event is allowed.
> W32Time: END Line 1949
> W32Time: Time source failed to produce usable timestamp.
> W32Time: BEGIN:NTPTry -- fail
> W32Time: END Line 1683
> W32Time: END Line 1496
> W32Time: END Line 368
> W32Time: BEGIN:ComputePostTimeData
> W32Time: BEGIN:ComputeInterval
> W32Time: END Line 2479
> W32Time: BEGIN:ComputeSleepStuff
> W32Time: Computed stagger is 0ms, bias is 0ms
> W32Time: Time until next sync - 2699.960s
> W32Time: END:Line 816
> W32Time: END:Line 221
> W32Time: END:Line 196
> W32Time: BEGIN:TermTime
> W32Time: NTP(S): received shutdown notification.
> W32Time: NTP(S): received shutdown notification.
> W32Time: TimeMMCleanup()
> W32Time: BEGIN:FinishCleanup
> W32Time: BEGIN:TsUpTheThread
> W32Time: END Line 1407
> W32Time: Inform NetLogon That you are not a TS Provider
> W32Time: BEGIN:UnInitializeDC
> W32Time: Ptrs 0 - 0
> W32Time: END:Line 727
> W32Time: Time service stopped.
> W32Time: END:Line 407
>
> C:\>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>



Relevant Pages

  • Re: w32tm will not synch on SBS 2000 server
    ... The main thing is that you need to create a filter in ISA. ... > am using the server as an internal timeserver for my domain. ... > The Windows Time service was stopped successfully. ... > W32Time: Advertising that I'm a Time Service Provider ...
    (microsoft.public.win2000.security)
  • Re: number of critical errors occurred on SBS 2003
    ... W32Time with ID: 4 ... The time service is configured to use one or more input providers however ... for SQL Server code: 18452 occur 1 time... ...
    (microsoft.public.windows.server.sbs)
  • Re: I cant sync to any time server
    ... Try reseting the time service ... net start w32time ... Microsoft MVP - Windows XP Shell/User ... server is unavailable. ...
    (microsoft.public.windows.mediacenter)
  • Re: W32Time
    ... I would like them to sync w/ ... If your workstations are not updating to the server, ... net start w32time ... The time service has not synchronized the system time for 86400 seconds ...
    (microsoft.public.windows.server.sbs)
  • RE: Microsoft Windows SBS 2003 Communication Issues
    ... > I. Make sure that the Time service on the SBS 2003 server is enabled. ... > For the SBS server, the time server may be disabled by some software. ... > Microsoft CSS Online Newsgroup Support ... > This newsgroup only focuses on SBS technical issues. ...
    (microsoft.public.windows.server.sbs)