asked on

Windows domain time issue

I am having an issue with time on my domain. The time is 10 minutes behind. I have attempted to use MS KB articles to resolve this issue and also added external NTP services but the time continually reverts to the 10 minute delay which is affecting all workstations.

The DC is virtualized and I have verified that the server is not synching to the hardware time that is hosting the the vm.

Below is the output of my w32tm query.

Anyone have any thoughts of on a resolution?

T.I.A

[Configuration]
EventLogFlags: 2 (Local)
AnnounceFlags: 10 (Local)
TimeJumpAuditOffset: 28800 (Local)
MinPollInterval: 6 (Local)
MaxPollInterval: 10 (Local)
MaxNegPhaseCorrection: 172800 (Local)
MaxPosPhaseCorrection: 172800 (Local)
MaxAllowedPhaseOffset: 300 (Local)

FrequencyCorrectRate: 4 (Local)
PollAdjustFactor: 5 (Local)
LargePhaseOffset: 50000000 (Local)
SpikeWatchPeriod: 900 (Local)
LocalClockDispersion: 10 (Local)
HoldPeriod: 5 (Local)
PhaseCorrectRate: 7 (Local)
UpdateInterval: 100 (Local)


[TimeProviders]
NtpClient (Local)
DllName: C:\Windows\system32\w32time.dll (Local)
Enabled: 1 (Local)
InputProvider: 1 (Local)
AllowNonstandardModeCombinations: 1 (Local)
ResolvePeerBackoffMinutes: 15 (Local)
ResolvePeerBackoffMaxTimes: 7 (Local)
CompatibilityFlags: 2147483648 (Local)
EventLogFlags: 1 (Local)
LargeSampleSkew: 3 (Local)
SpecialPollInterval: 3600 (Local)
Type: NTP (Local)
NtpServer: "1.ca.pool.ntp.org,0.ca.pool.ntp.org" (Local)

NtpServer (Local)
DllName: C:\Windows\system32\w32time.dll (Local)
Enabled: 1 (Local)
InputProvider: 0 (Local)
AllowNonstandardModeCombinations: 1 (Local)

VMICTimeProvider (Local)
DllName: C:\Windows\System32\vmictimeprovider.dll (Local)
Enabled: 1 (Local)
InputProvider: 1 (Local)

Open in new window

ASKER CERTIFIED SOLUTION

Frank Helk

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

Lionel MM

Please read the attached to see if that helps you--have used this for 10 plus years to fix any time issues--works 99% of the time. In one instance where time is an critical issue (and I cannot fix it) I use http://www.nist.gov/pml/div688/grp40/its.cfm -- it has worked for me on a bank's server for 10+ years (see download button on right side of page).
Timefix.Txt

Irwin W.

ASKER

@frankhelk...Thanks for this but it does not seem to run as a service. Is this right?

Frank Helk

Nope - your query sure runs in foreground, but W32time runs as service under all circumstances. And when running in NTP mode, it's a constant source of hassle (just last week I helped a coworker with w32time not syncing correct to the DC).

Still the same advice: Use the classic NTP client ...

The classic NTP ports run as service, too, and could be identified in task manager as ntpd.exe.

Seth Simmons

This question has been classified as abandoned and is closed as part of the Cleanup Program. See the recommendation for more details.