Windows Server 2008 R2 Thread, Time jumping issue (no access to ntp server) in Technical; The problem: My only domain controller time keeps jumping either forwards or backwards a amount between 2 hours and 24 ...
The problem: My only domain controller time keeps jumping either forwards or backwards a amount between 2 hours and 24 hours.
I run 4 virtual 2008r2 servers and one physical, all connected to the domain.
The virtual servers run on VMware across two machines.
The setup has been pretty static for the last 6 months.
The time across the domain started jumping a few days ago.
Currently I have no access to a ntp server (a separate issue with over zealous county blocking, that is taking them months to fix)
Played around with w32tm, all domain machines were resyncing to domain. Domain had no w32tm host/ source listed to resync from.
Disabled w32tm on the domain server- this caused all the network machines other than 2008r2 to retain the correct time. Now though each of 2008r2 servers will be running at different times. Over night one server gained 7 hours another gained 2 days while the antivirus server lost a month. At first I thought this might be to do with only the virtualised machines but the lone physical server had the same issue.
Any ideas what is setting the time for the 2008r2 machines?
Can anyone suggest a tool to pinpoint whats setting the time seemingly randomly. I tried a tool called ntplookup but it could not identify any rogue ntp servers.
Am I missing something obvious?
Domain had no w32tm host / source listed to resync from.
All you should need to do is configure the time on the server which holds the PDC emulator role so that it syncs with an external source. The other servers in your domain will automatically find the authoritative time server and sync with that.
In VSphere client - right click server edit settings, Options, VMware Tools, on the bottom left does it have Syncronise Guest time with host ticked?
I will have to check when back on site (just been kicked out). I believe they are not set to Synchronize guest time.
Originally Posted by kmount
If the hypervisor time is jumping too, is it pointing to something else for time? (and that it may be is the one jumping).
Would be useful to know what the hypervisors are doing for their time configuration, it could be the root of the problem.
Also worth checking timezone configured on your server builds just incase, that can account for 'big hour' jumps.
The VMware hosts and both joined to the domain and were taking their time from the domain controller. They are no longer set to pick up time the ntp client is stopped, yet they still change at the same rate as the 2008r2 servers. All the servers and hosts are set to London time zones (was one of my early thoughts too).
I checked the BIOS of one of our VMware hosts and the time was spot on.
I can confirm that time sync between the virtual servers and the ESX server is presently unticked.
In noted behavior since I left yesterday..
All virtual servers and hosts had changed to 17.12.2005
The physical server had the right time.
1 hour later
Both hosts were using 23.02.2022
2/4 servers were using 23.02.2022 including the domain server
The other two servers were displaying the correct time.
Physical server had the correct date/ time
To set the time server on 2008 R2, run the following command on a physical DC (recommended):
net stop w32time
w32tm /config /syncfromflags:manual /manualpeerlist:ntp.bgfl.org
w32tm /config /reliable:yes
net start w32time
w32tm /query /peers
Just change the name of the NTP server to your time server of choice.
If your LA are unable to provide a suitable NTP server, you should request port UDP 123 is unblocked or at least forwarded to a nominated time server. Without this I bet your local network is creating a whole range of errors disrupting users.