[Okta Webinar] Learn how to a build a cloud-first strategyRegister Now

x
?
Solved

Another w32time Issue

Posted on 2009-02-10
5
Medium Priority
?
1,867 Views
Last Modified: 2012-05-06
I have searched here and Google'd in general, and I can't find an answer to yet another time issue.

I have an issue where a PDCe is configured to sync from an external time source.  This system, DC1, is a virtual machine.  When I do a "w32tm /resync", the correct time is read from the external source (we use north-america.pool.ntp.org), and you can watch the time reset to that which is accurate.  However, within 10 seconds later it reverts back to a bad time a couple minutes in the past, the same time it was set to before the manual sync.  

Orginally I had thought the physical server the VM was running on was the problem.  I disabled the w32time service on the physical machine and it appeared the problem was taken care of.  However, a few days later it was called to my attention that the member servers, which sync to DC1, had bad time.  DC1 has eventlog entries like:

Event Type:      Warning
Event Source:      W32Time
Event Category:      None
Event ID:      50
Date:            2/10/2009
Time:            10:18:44 AM
User:            N/A
Computer:      GW-DC1
Description:
The time service detected a time difference of greater than 5000 milliseconds  for 900 seconds. The time difference might be caused by synchronization with  low-accuracy time sources or by suboptimal network conditions. The time service is no longer synchronized and cannot provide the time to other clients or update  the system clock. When a valid time stamp is received from a time service  provider, the time service will correct itself.  

I turned NTP debug logging on, and those results are below.  Note that there is a hole opened in the firewall for queries to get through, and again a manual sync works fine.

Any help would be appreciated!

Toni


149059 08:57:14.3014904s - ClockDispln:149059 08:57:14.3014904s -   PhCRA:0 phcT:100 KPhO:0
149059 08:57:15.3054304s - ClockDispln:149059 08:57:15.3054304s -   PhCRA:0 phcT:100 KPhO:0
149059 08:57:15.7572034s - W32TmServiceMain: timeout
149059 08:57:15.7572034s - TimeProvCommand([NtpClient], TPC_GetSamples) called.
149059 08:57:15.7572034s - NtpClient returned 0 samples.
149059 08:57:15.7572034s - W32TmServiceMain: waiting 64.000s
149059 08:57:15.7772822s - ListeningThread -- DataAvailEvent set for socket 0 (192.168.200.62:123)
149059 08:57:15.7772822s - ListeningThread -- response heard from 192.168.31.100:123
149059 08:57:15.7772822s - /-- NTP Packet:
149059 08:57:15.7772822s - | LeapIndicator: 3 - not synchronized;  VersionNumber: 3;  Mode: 1 - SymmetricActive;  LiVnMode: 0xD9
149059 08:57:15.7772822s - | Stratum: 0 - unspecified or unavailable
149059 08:57:15.7772822s - | Poll Interval: 7 - 128s;  Precision: -6 - 15.625ms per tick
149059 08:57:15.7772822s - | RootDelay: 0x0000.0000s - unspecified;  RootDispersion: 0x0001.0400s - 1.01563s
149059 08:57:15.7772822s - | ReferenceClockIdentifier: 0x00000000 - unspecified
149059 08:57:15.7772822s - | ReferenceTimestamp:   0x0000000000000000 - unspecified
149059 08:57:15.7772822s - | OriginateTimestamp:   0x0000000000000000 - unspecified
149059 08:57:15.7772822s - | ReceiveTimestamp:     0x0000000000000000 - unspecified
149059 08:57:15.7772822s - | TransmitTimestamp:    0xCD3BBFF154000000149059 08:57:15.7772822s -  - 12878729841328125000ns - 149059 08:57:21.3281250s
149059 08:57:15.7772822s - >-- Non-packet info:
149059 08:57:15.7772822s - | DestinationTimestamp: 149059 08:57:15.7772822s - 0xCD3BBFEBC6FBF75C149059 08:57:15.7772822s -  - 12878729835777282200ns149059 08:57:15.7772822s -  - 149059 08:57:15.7772822s
149059 08:57:15.7772822s - | RoundtripDelay: -5550842800ns (-5s)
149059 08:57:15.7772822s - | LocalClockOffset: 2775421400ns - 0:02.775421400s
149059 08:57:15.7772822s - \--
149059 08:57:15.7772822s - Computing server digest: OLD:FALSE, RID:00001FF5
149059 08:57:15.7772822s - TransmitResponse: sent 192.168.200.62:123->192.168.31.100:123
149059 08:57:16.3093704s - ClockDispln:149059 08:57:16.3093704s -   PhCRA:0 phcT:100 KPhO:0
149059 08:57:17.3133104s - ClockDispln:149059 08:57:17.3133104s -   PhCRA:0 phcT:100 KPhO:0
149059 08:57:18.3272898s - ClockDispln:149059 08:57:18.3272898s -   PhCRA:0 phcT:101 KPhO:0
149059 08:57:19.3312298s - ClockDispln:149059 08:57:19.3312298s -   PhCRA:0 phcT:100 KPhO:0
149059 08:57:20.3351698s - ClockDispln:149059 08:57:20.3351698s -   PhCRA:0 phcT:100 KPhO:0
149059 08:57:21.3391098s - ClockDispln:149059 08:57:21.3391098s -   PhCRA:0 phcT:100 KPhO:0
149059 08:57:22.3430498s - ClockDispln:149059 08:57:22.3430498s -   PhCRA:0 phcT:100 KPhO:0
149059 08:57:23.3469898s - ClockDispln:149059 08:57:23.3469898s -   PhCRA:0 phcT:100 KPhO:0
149059 08:57:23.8891174s - ListeningThread -- DataAvailEvent set for socket 0 (192.168.200.62:123)
149059 08:57:23.8891174s - ListeningThread -- response heard from 192.168.200.113:123
149059 08:57:23.8891174s - /-- NTP Packet:
149059 08:57:23.8891174s - | LeapIndicator: 3 - not synchronized;  VersionNumber: 3;  Mode: 1 - SymmetricActive;  LiVnMode: 0xD9
149059 08:57:23.8891174s - | Stratum: 0 - unspecified or unavailable
149059 08:57:23.8891174s - | Poll Interval: 7 - 128s;  Precision: -6 - 15.625ms per tick
149059 08:57:23.8891174s - | RootDelay: 0x0000.147Fs - 0.0800629s;  RootDispersion: 0x0010.0000s - 16s
149059 08:57:23.8891174s - | ReferenceClockIdentifier: 0x00000000 - unspecified
149059 08:57:23.8891174s - | ReferenceTimestamp:   0xCD3ACC9EDC000000149059 08:57:23.8891174s -  - 12878667550859375000ns - 149058 15:39:10.8593750s
149059 08:57:23.8891174s - | OriginateTimestamp:   0x0000000000000000 - unspecified
149059 08:57:23.8891174s - | ReceiveTimestamp:     0x0000000000000000 - unspecified
149059 08:57:23.8891174s - | TransmitTimestamp:    0xCD3BC06AD0E7D714149059 08:57:23.8891174s -  - 12878729962816037600ns - 149059 08:59:22.8160376s
149059 08:57:23.8891174s - >-- Non-packet info:
149059 08:57:23.8891174s - | DestinationTimestamp: 149059 08:57:23.8891174s - 0xCD3BBFF3E39D32AB149059 08:57:23.8891174s -  - 12878729843889117400ns149059 08:57:23.8891174s -  - 149059 08:57:23.8891174s
149059 08:57:23.8891174s - | RoundtripDelay: -118926920200ns (-118s)
149059 08:57:23.8891174s - | LocalClockOffset: 59463460100ns - 0:59.463460100s
149059 08:57:23.8891174s - \--
149059 08:57:23.8891174s - Computing server digest: OLD:FALSE, RID:00000460
149059 08:57:23.8891174s - TransmitResponse: sent 192.168.200.62:123->192.168.200.113:123
149059 08:57:24.3509298s - ClockDispln:149059 08:57:24.3509298s -   PhCRA:0 phcT:100 KPhO:0
149059 08:57:25.3548698s - ClockDispln:149059 08:57:25.3548698s -   PhCRA:0 phcT:100 KPhO:0
149059 08:57:26.3588098s - ClockDispln:149059 08:57:26.3588098s -   PhCRA:0 phcT:100 KPhO:0
149059 08:57:27.3627498s - ClockDispln:149059 08:57:27.3627498s -   PhCRA:0 phcT:100 KPhO:0
149059 08:57:28.3666898s - ClockDispln:149059 08:57:28.3666898s -   PhCRA:0 phcT:100 KPhO:0
149059 08:57:29.3706298s - ClockDispln:149059 08:57:29.3706298s -   PhCRA:0 phcT:100 KPhO:0
149059 08:57:30.3745698s - ClockDispln:149059 08:57:30.3745698s -   PhCRA:0 phcT:100 KPhO:0
149059 08:57:31.3785098s - ClockDispln:149059 08:57:31.3785098s -   PhCRA:0 phcT:100 KPhO:0
149059 08:57:32.3824498s - ClockDispln:149059 08:57:32.3824498s -   PhCRA:0 phcT:100 KPhO:0
149059 08:57:33.3863898s - ClockDispln:149059 08:57:33.3863898s -   PhCRA:0 phcT:100 KPhO:0
149059 08:57:34.3903298s - ClockDispln:149059 08:57:34.3903298s -   PhCRA:0 phcT:100 KPhO:0
149059 08:57:34.5509602s - ListeningThread -- DataAvailEvent set for socket 0 (192.168.200.62:123)
149059 08:57:34.5509602s - ListeningThread -- response heard from 192.168.200.153:123
149059 08:57:34.5509602s - /-- NTP Packet:
149059 08:57:34.5509602s - | LeapIndicator: 3 - not synchronized;  VersionNumber: 3;  Mode: 1 - SymmetricActive;  LiVnMode: 0xD9
149059 08:57:34.5509602s - | Stratum: 0 - unspecified or unavailable
149059 08:57:34.5509602s - | Poll Interval: 5 - 32s;  Precision: -6 - 15.625ms per tick
149059 08:57:34.5509602s - | RootDelay: 0x0000.147Fs - 0.0800629s;  RootDispersion: 0x0010.0000s - 16s
149059 08:57:34.5509602s - | ReferenceClockIdentifier: 0x00000000 - unspecified
149059 08:57:34.5509602s - | ReferenceTimestamp:   0xCD3ACEDD5F7AFEA3149059 08:57:34.5509602s -  - 12878668125372970500ns - 149058 15:48:45.3729705s
149059 08:57:34.5509602s - | OriginateTimestamp:   0x0000000000000000 - unspecified
149059 08:57:34.5509602s - | ReceiveTimestamp:     0x0000000000000000 - unspecified
149059 08:57:34.5509602s - | TransmitTimestamp:    0xCD3BC02744ED9168149059 08:57:34.5509602s -  - 12878729895269250000ns - 149059 08:58:15.2692500s
149059 08:57:34.5509602s - >-- Non-packet info:
149059 08:57:34.5509602s - | DestinationTimestamp: 149059 08:57:34.5509602s - 0xCD3BBFFE8D0BBA48149059 08:57:34.5509602s -  - 12878729854550960200ns149059 08:57:34.5509602s -  - 149059 08:57:34.5509602s
149059 08:57:34.5509602s - | RoundtripDelay: -40718289800ns (-40s)
149059 08:57:34.5509602s - | LocalClockOffset: 20359144900ns - 0:20.359144900s
149059 08:57:34.5509602s - \--
149059 08:57:34.5509602s - Computing server digest: OLD:FALSE, RID:000021B9
149059 08:57:34.5509602s - TransmitResponse: sent 192.168.200.62:123->192.168.200.153:123
149059 08:57:35.3942698s - ClockDispln:149059 08:57:35.3942698s -   PhCRA:0 phcT:100 KPhO:0
149059 08:57:36.3982098s - ClockDispln:149059 08:57:36.3982098s -   PhCRA:0 phcT:100 KPhO:0
0
Comment
Question by:SafetyNet-TC
  • 2
3 Comments
 
LVL 85

Assisted Solution

by:oBdA
oBdA earned 2000 total points
ID: 23604234
Virtualization hosts usually provide a mechanism to sync their time with the guest machines. If your DC is configured to sync with an external time source, then you have to disable the sync with the host (usually somewhere in the properties of the virtual machine). The other possibility would be to disable the time service on the guest machines and instead make sure that the host's time is precise, and sync the guests with the host only.
But simply disabling the time service on the host won't achieve anything - the host/guest sync will continue.
0
 

Accepted Solution

by:
SafetyNet-TC earned 0 total points
ID: 23606430
Talk about a "dooh" moment.  Yes, http://support.microsoft.com/kb/867585 covers the issue.  Thank you for the tip!

Toni
0
 
LVL 85

Expert Comment

by:oBdA
ID: 23697152
Sorry, but I object to the "20pt" split. "dooh" moment or not, I provided the correct solution (and I would have given detailed instructions on how to disable the time sync, but you didn't mention which virtualization solution you're using).
Asking Questions > Step 4: Assign Points
http://www.experts-exchange.com/help.jsp
"Points are your advertising; the more points you assign, the more likely you are to get a quick response. Points are not the reward you give for your answer. For example, if you ask how to do something, and an Expert tells you that you can't, that's the answer, and all of the points should be awarded, even if you don't like the answer."
0

Featured Post

Free Tool: IP Lookup

Get more info about an IP address or domain name, such as organization, abuse contacts and geolocation.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

In a hurry?.. scroll down to "HERE's HOW TO DO IT" Section. Greetings All, I was going to post this as question/solution, but its seems more appropriate as an article considering its length.  I felt it important to illucidate all the details c…
This is a little timesaver I have been using for setting up Microsoft Small Business Server (SBS) in the simplest possible way. It may not be appropriate for every customer. However, when you get a situation where the person who owns the server is i…
In this video, we discuss why the need for additional vertical screen space has become more important in recent years, namely, due to the transition in the marketplace of 4x3 computer screens to 16x9 and 16x10 screens (so-called widescreen format). …
Windows 8 came with a dramatically different user interface known as Metro. Notably missing from that interface was a Start button and Start Menu. Microsoft responded to negative user feedback of the Metro interface, bringing back the Start button a…

872 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question