Jobos Posted March 30, 2017 Posted March 30, 2017 Came in school this morning to be told nothing was working. This problem I tracked down to the time on one of the DCs was 2 days out. Everything was ok yesterday so this was odd. The event log on the DC showed this The time service has detected that the system time needs to be changed by 176396 seconds. The time service will not change the system time by more than 172800 seconds. Verify that your time and time zone are correct, and that the time source uk.pool.ntp.org (ntp.m|0x0|0.0.0.0:123->129.250.35.250:123) is working properly. I changed the time and all was well again but just to be sure I changed the NTP pool address to pool.ntp.org is stated here pool.ntp.org: NTP Servers in United Kingdom, uk.pool.ntp.org Checking the DC again before I went home the time was an hour out so I restarted the time service on the DC but nothing changed so had to manually change it. This got me thinking so I restarted the time service again and within seconds the DCs time went an hour out. I've disabled the service for now but I need to get this fixed. All the VMs including the DCs are set to not sync with the host. Running w32tm /query /peers on the DC gives this: #Peers: 1 Peer: pool.ntp.org State: Active Time Remaining: 62.3096060s Mode: 1 (Symmetric Active) Stratum: 2 (secondary reference - syncd by (S)NTP) PeerPoll Interval: 15 (32768s) HostPoll Interval: 6 (64s) Looking at the logs again I see a number of event ID 1 from when I changed the time this morning to 16.22 when the time changed by an hour. The time zone is set to UTC +0 Dublin, Edinburgh, Lisbon, London
Bedders Posted March 30, 2017 Posted March 30, 2017 I always sync everything to "uk.pool.ntp.org". I'm not 100% sure if it requires the UK. at the start, otherwise it may be going off GMT rather than BST if it's an hour out?
Arthur Posted March 30, 2017 Posted March 30, 2017 (edited) Not had any issues syncing with time.google.com since the clocks went forward either. Edited March 30, 2017 by Arthur
Jobos Posted March 30, 2017 Author Posted March 30, 2017 I always sync everything to "uk.pool.ntp.org". I'm not 100% sure if it requires the UK. at the start, otherwise it may be going off GMT rather than BST if it's an hour out? Yes it was using uk.pool.ntp.org before I changed it to pool.ntp.org Think I'll try @Arthur suggestion of using Googles time service and see how it goes. Note. I found that disabling the time service on the DC means drives will not map.
MrEprise Posted March 30, 2017 Posted March 30, 2017 Maybe it doesn't apply in this case (since Google's time service seems to work for you) but for anyone else just note if your internet (and possibly filtering) is provided by RM, they actively block SNTP requests to any address bar their own ones (e.g. ntp.ifl.net.)
3s-gtech Posted March 30, 2017 Posted March 30, 2017 1 hour out would suggest that there is a timezone or BST issue with the source or your server.
Jobos Posted March 30, 2017 Author Posted March 30, 2017 1 hour out would suggest that there is a timezone or BST issue with the source or your server. Fool that I am I had removed the tick from the option to adjust for daylight saving time! I've changed the NTP server to google so I'll keep eye on it but it's puzzling why the time was 2 days out of sync.
Jobos Posted March 31, 2017 Author Posted March 31, 2017 Can you servers talk to external time servers? Yes the firewall allows that. I changed the NTP server to google last night and I've not had any phone calls today so I'm guessing all is well.
Bedders Posted March 31, 2017 Posted March 31, 2017 Yes the firewall allows that. I changed the NTP server to google last night and I've not had any phone calls today so I'm guessing all is well. Nicely done No news is good news!
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now