tech_guy Posted June 3, 2013 Posted June 3, 2013 We have a HP DC that will gain four minutes over a term. It's set to sync with pool.ntp.org so I'm baffled. Any ideas?
Davit2005 Posted June 3, 2013 Posted June 3, 2013 These are the ntp addresses I normally use. 0.uk.pool.ntp.org 1.uk.pool.ntp.org 2.uk.pool.ntp.org 3.uk.pool.ntp.org 1
tech_guy Posted June 3, 2013 Author Posted June 3, 2013 Physical and we're using: 0.uk.pool.ntp.org 1.uk.pool.ntp.org 2.uk.pool.ntp.org 3.uk.pool.ntp.org
Michael Posted June 3, 2013 Posted June 3, 2013 You could always change the watch battery on the motherboard, although normally you lose time rather than gain it.
MrEprise Posted June 3, 2013 Posted June 3, 2013 Does your ISP allow you to connect to those ntp addresses? The SWGfL for example blocks access to any ntp servers except their own so it may be worth finding this out.
chazzy2501 Posted June 3, 2013 Posted June 3, 2013 (edited) yeap, I have swgfl so I just used their timeserver ntp.swgfl.org.uk that way you also don't have to worry about proxy settings. Edited June 3, 2013 by chazzy2501
AngryTechnician Posted June 3, 2013 Posted June 3, 2013 Curious. Anything in the System event log for the Time-Service source that might suggest what the problem is?
sted Posted June 3, 2013 Posted June 3, 2013 dont you have to alter a dc's settings to get it to use an ntp server anyway? If you have other dcs is it just updating to "correct" then finding other dcs are different then recorrecting to the same as other dcs?
ConradJones Posted June 7, 2013 Posted June 7, 2013 w32tm /query /configuration w32tm /query /status might help shed some light? also i concur checking ports are not blocked.
timbo343 Posted June 7, 2013 Posted June 7, 2013 To the OP, funny you should say that, mine do that too. I have had to change mine back as they too had speeded up so to speak.
timzim Posted June 7, 2013 Posted June 7, 2013 If it's gaining 4 minutes then it not synching with the external clock. More likely you have some sort of synching loop in your domain where 1 machine synchs with another then that one synchs with the first. The only time I've seen this is before is when I had a a virtual DC set to synch from the virtual host and vice versa. The miniscule delay between synching and changing the time increases the time difference between the two very very slowly but it builds to minutes over a few months. Check which machines on your network are time servers - I bet you have more than one.
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