virtual (PDC) DC on VMware host cannot synch time with external ntp host

Virtual W2K12 (PDC) DC running on VMware ESX 5.5 host is not synchronizing time with external source.  The time source shows "Local CMOS Clock" not matter what I try.

We have disabled time synch for the VM with VMware  according to https://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1189.

I've tried following the steps to question #6 in https://blogs.msdn.microsoft.com/virtual_pc_guy/2010/11/19/time-synchronization-in-hyper-v/, which included setting to "0", then setting the external ntp server list according to  https://docs.microsoft.com/en-us/previous-versions/windows/it-pro/windows-server-2003/cc784553(v=ws.10).

No matter what I try, I see this on the PDC:

C:\Windows\system32>w32tm /query /source
Local CMOS Clock

Windows time synch b/t the other DC's, member servers, and workstations are all working - synchronizing with our PDC just fine. It's just that we can't get synch'd with an external time server.  We currently point to an internal switch that's running an ntp service.

Below is my current configuration:

      C:\Windows\system32>w32tm /query /configuration
      [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)
      
      FileLogName: C:\Windows\Temp\w32time.log (Local)
      FileLogEntries: 0-116 (Local)
      FileLogSize: 10000000 (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: 10.1.1.254 (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: 0 (Local)
      InputProvider: 1 (Local)
LVL 1
RhoSysAdminAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

MaheshArchitectCommented:
read complete thread below and act on that
https://www.experts-exchange.com/questions/29018610/ntp-server.html
it should resolve your issue
VMware steps you taken are correct
somehow your server is unable to connect to external time source, u ned to ensure that your server is able to communicate over udp 123 to internet time server
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
RhoSysAdminAuthor Commented:
Pointing to the NIST ntp servers worked once. My ntp source was one of the NIST servers, and the time on the DC had updated to the correct time (we were 90 seconds off).

Thinking I was done, I removed the registry keys for the debut log file I had added earlier today. I repeated the steps as you listed, and now I'm back to "Local CMOS clock" for the time source:

C:\Windows\system32>w32tm /config /manualpeerlist:"time-a-b.nist.gov,0x1 time-a-g.nist.gov,0x1"
 /syncfromflags:MANUAL /reliable:yes /update
The command completed successfully.

C:\Windows\system32>w32tm /config /update
The command completed successfully.

C:\Windows\system32>net stop w32time && net start w32time
The Windows Time service is stopping.
The Windows Time service was stopped successfully.

The Windows Time service is starting.
The Windows Time service was started successfully.


C:\Windows\system32>w32tm /resync
Sending resync command to local computer
The computer did not resync because no time data was available.

C:\Windows\system32>w32tm /query /source
Local CMOS Clock

C:\Windows\system32>w32tm /query /status
Leap Indicator: 0(no warning)
Stratum: 1 (primary reference - syncd by radio clock)
Precision: -6 (15.625ms per tick)
Root Delay: 0.0000000s
Root Dispersion: 10.0000000s
ReferenceId: 0x4C4F434C (source name:  "LOCL")
Last Successful Sync Time: 3/21/2018 3:53:38 PM
Source: Local CMOS Clock
Poll Interval: 6 (64s)
0
MaheshArchitectCommented:
find out pool.ntp.org servers nearby your region and check if they works

Somehow you are unable to reach internet time servers over UDP 123, for that your Dc should reach out to internet with internet name resolution and SNMP protocol (UDP 123) to designated time servers
0
Powerful Yet Easy-to-Use Network Monitoring

Identify excessive bandwidth utilization or unexpected application traffic with SolarWinds Bandwidth Analyzer Pack.

RhoSysAdminAuthor Commented:
Our PDC (DC) is on our internal network, and there are no firewall restrictions on where it can go OUT.

Our network engineer sees queries going out to the ntp servers on his firewall log.   My debug log shows what looks to be communication with the external ntp server as well.

Why does my "/query /source" still show "Local CMOS Clock" when it may actually be working?

C:\Windows\system32>w32tm /query /source
Local CMOS Clock

C:\Windows\system32>w32tm /query /status
Leap Indicator: 0(no warning)
Stratum: 1 (primary reference - syncd by radio clock)
Precision: -6 (15.625ms per tick)
Root Delay: 0.0000000s
Root Dispersion: 10.0000000s
ReferenceId: 0x4C4F434C (source name:  "LOCL")
Last Successful Sync Time: 3/21/2018 3:53:38 PM
Source: Local CMOS Clock
Poll Interval: 6 (64s)
0
RhoSysAdminAuthor Commented:
We appear to be having better luck pointing directly at two NIST servers. Although I still see event ID 47 warnings. But it appears a warning is logged for one and the ntp client switches to the other NIST server. At this moment, time is synch'd and our time source is a NIST server.

C:\Windows\system32>w32tm /query /status
Leap Indicator: 0(no warning)
Stratum: 2 (secondary reference - syncd by (S)NTP)
Precision: -6 (15.625ms per tick)
Root Delay: 0.0783591s
Root Dispersion: 0.8082004s
ReferenceId: 0x84A36001 (source IP:  132.163.96.1)
Last Successful Sync Time: 3/23/2018 8:18:41 AM
Source: time-a-b.nist.gov,0x1
Poll Interval: 9 (512s)


C:\Windows\system32>w32tm /query /source
time-a-b.nist.gov,0x1

I think all I can do at this point is monitor it and hope we stay synch'd.

Should I have more than two servers in my list in case both become unreachable at the same time?
0
MaheshArchitectCommented:
Normally two servers are enough
But you can add 3rd one if wanted to
0
RhoSysAdminAuthor Commented:
After monitoring ntp for past several days, it appears to be working as expected.
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Virtualization

From novice to tech pro — start learning today.