I ran the w32tm /once command and this is what I
received. Do you know what it means?
C:\>w32tm /once
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 2 NICs.
W32Time: Advertising that I'm a Time Service Provider
W32Time: BEGIN:TsUpTheThread
W32Time: BEGIN:TsUpTheThread
W32Time: timeBeginPeriod: setting resolution 9
W32Time: END Line 1407
W32Time: END Line 1407
W32Time: BEGIN:TimeSync
W32Time: NTP(S): waiting for datagram...
W32Time: NTP(S): waiting for datagram...
W32Time: BEGIN:FGetType
W32Time: END Line 254
W32Time: BEGIN:FDoTimeNTPType
W32Time: BEGIN:FDoNT5DSType
W32Time: BEGIN:FBuildDCList
W32Time: BEGIN:GetNT5DCAddress
W32Time: Member of an Win2K domain.
Looking for DCs.
W32Time: Accepting previously discoverd DC
W32Time: BEGIN:GetRole
W32Time: Role is 'PDC'
W32Time: END Line 672
W32Time: Calling DsGetDcNameA() for a DC
GTS in the same domain
W32Time: END Line 519
W32Time: BEGIN:GetNT5DCAddress
W32Time: Member of an Win2K domain.
Looking for DCs.
W32Time: Looking for any DC, not
necessarily a time source
W32Time: BEGIN:GetRole
W32Time: Role is 'PDC'
W32Time: END Line 672
W32Time: Calling DsGetDcNameA() for a DC
GTS in the same domain
W32Time: END Line 519
W32Time: END Line 639
W32Time: Logging event 0xC0000036. 15 min until
this event is allowed a
gain.
W32Time: 0xC0000036 reported to System Log in
Event Viewer
W32Time: DC lookup failed. 15 min until lookup
is allowed again.
W32Time: END Line 971
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
-----Original Message-----
To see what the time service is doing Stop the w32time service and run w32tm
/once and see what you are getting
--
Richard McCall [MSFT]
"This posting is provided "AS IS" with no warranties, and confers no
rights."
Thanks for the help. Port 123 is open to send/receive.
Not sure what you mean about the NAT between the DC and
the local loop though. How would I forward a port?
I checkd the registry, LocalNTP is set to Hex=0. Is
that 'yes'?
I did stop and restart w32time, but still have the same
incorrect time.
Perhaps I do have a NAT? How can I check that?
thanks,
Keith
-----Original Message-----
I assume you are doing a compare with an atomic clock?
If so, then something, somewhere, isn't working on your
NTP rig.
My rig:
a) Tell your firewall to be nice to TCP/UDP port 123
packets (I beleive you can get by on just UDP...never
tried).
b) Only use the external NTP source on a DC (as you have);
if there's any NAT between DC and your local loop, forward
the port.
c) On the DC, set the "LocalNTP=yes" in the registry.
d) You have correct syntax, so no worries there [I use
ntp2.usno.navy.mil].
4) Do "net stop w32time" and "net start w32time" to
immediately kick things off on your new internal NTP
server.
5) On Client boxes, do "net stop w32time", "net
time /setsntp:<your NTP server>", and finally "net start
w32time" for an immediate synch.
In the meantime, relax your Kerberos Policy for the extra
couple of minutes you are currently "out".
-----
David
-----Original Message-----
I have set the time service sync on a domain controller
using the 'net time /setsntp:sourcename' command, but it
has not updated to the coorect time on that external
source. We are still 6-7 minutes behind the time
that
is
coming from the external source. How can I get the
DC
to
refresh and start pulling the correct time from the
external source? (I am using time- a.timefreq.bldrdoc.gov
as the external source.)
.
