TIme is out on DC

[neonetman]

I've noticed that the time on our network is out be 2 minutes (well 100 seconds to be accurate).

 

I've tried setting the time on the DC using:-

 

* w32tm /config /manualpeerlist:time.windows.com /syncfromflags:manual /reliable:yes /update

* w32tm.exe /resync /rediscover /nowait

 

Despite the event log stating "The time provider NtpClient is currently receiving valid time data from time.windows.com (ntp.m|0x0|0.0.0.0:123->20.101.57.9:123).", the time is still 2 minutes ahead

 

I've also run "w32tm /stripchart /computer:time.windows.com /dataonly" which confirms I am 100s out.

 

I can't change the time manuallyu (the abvility to change time is greyed out), so am looking for support from you lot on how to resolve this

 

Frustrated!!!

 

Cheer

[Jawloms]

Is it a VM?

[neonetman]

Yes it's a hyper-v VM

[neonetman]

I've turned off time synchronisation on al DC's and run the sync commands again - still to no avail

[Jawloms]

My VM DC syncs it's time to it's host. I changed the hosts time and it corrected the DC after a few minutes.

[FN-GM]

My VM DC syncs it's time to it's host. I changed the hosts time and it corrected the DC after a few minutes.

 

Where does your host sync its time from? If it’s the domain controllers the time will drift again. You should turn off the host / vm time sync for domain controllers.

[FN-GM]

Yes it's a hyper-v VM

 

Similar to the above. Make sure you the DC virtual machine isn’t syncing with the host.

[neonetman]

Thanks all,

 

I've removed time sync and it's gradually corrected itself