1
I'm trying to sync my PC time with an internal server but I'm not sure if it's working.
I've added the internal server to NTP.conf as below:
colin@colin:~$ sudo geany /etc/ntp.conf
server 193.61.148.167 prefer
server 0.debian.pool.ntp.org iburst
server 1.debian.pool.ntp.org iburst
server 2.debian.pool.ntp.org iburst
server 3.debian.pool.ntp.org iburst
This is the results of ntpdc -c peers
remote local st poll reach delay offset disp
=======================================================================
=mca167.scm.ulst 193.61.148.73 1 64 1 0.00122 -298.2700 2.81874
=ns1.nexellent.n 193.61.148.73 16 64 0 0.00000 0.000000 3.99217
=1.ntp.tld.sk 193.61.148.73 16 64 0 0.00000 0.000000 3.99217
=time.ostseehaie 193.61.148.73 16 64 0 0.00000 0.000000 3.99217
=ns393034.ovh.ne 193.61.148.73 16 64 0 0.00000 0.000000 3.99217
And the result of ntpdc -c sysinfo
system peer: 0.0.0.0
system peer mode: unspec
leap indicator: 11
stratum: 16
precision: -20
root distance: 0.00000 s
root dispersion: 0.00021 s
reference ID: [73.78.73.84]
reference time: 00000000.00000000 Mon, Jan 1 1900 0:00:00.000
system flags: auth monitor ntp kernel stats
jitter: 0.000000 s
stability: 0.000 ppm
broadcastdelay: 0.000000 s
authdelay: 0.000000 s
To me it doesn't look like it's working as 193.61.148.73 is my PC IP and the IP of the server is 193.61.148.167
EDIT: apologies of the formatting I'm on my phone and can't figure out the code tags.
Are you sure your firewall is permitting NTP? Most of your peers appear to be unreachable. If you are not going to permit them, then you really should comment out the pool.ntp.org lines. It does seem to be able to access 193.61.148.167 (ie mca167.scm.ulster.ac.uk) server. – Zoredache – 2015-03-07T17:27:29.880
I'm not sure about the firewall, I'm on a managed environment so it wouldn't surprise me if it was locked down. Also may I ask how you know that the other hosts are unreachable? Is it the fact that delay and offset are all 0's? – Colin747 – 2015-03-09T09:30:23.200