NTP problem

[darth]

Hi I started this question under "Can access Webmin, Can't SSH in however", but it seems inappropriate as this is an entirely different subject.

Problem is, from the first time I set up my pogoplug v3 I have not been able to get the time to automatically set. I tried everything I could think of. In frustration I removed openntp and replaced it with ntp and didn't do any better. I am using a static ip, I have set my /etc/resolv.conf to use the Google DNS servers as:

nameserver 8.8.8.8
nameserver 8.8.4.4

My /etc/ntp.conf is as follows:

# Associate to public NTP pool servers; see http://www.pool.ntp.org/
#server 0.pool.ntp.org iburst
server 64.73.32.134 iburst
server 1.pool.ntp.org iburst
server 2.pool.ntp.org iburst
server 3.pool.ntp.org iburst

# Location of drift and log files
driftfile /var/lib/ntp/ntp.drift
logfile /var/log/ntp.log

I replaced 0.pool.ntp.org with its IP address below, just in case I was having a DNS problem.
I removed all restrictions.

I can ping 0.pool.ntp.org or it's IP without problem.

I killed ntp and ran ntpdate as follows:

# ntpdate -dv 0.pool.ntp.org

and got the following:

5 Apr 15:37:12 ntpdate[1560]: ntpdate 4.2.6p5@1.2349-o Fri Mar 2 19:05:31 UTC 2012 (1)
host found : bindcat.fhsu.edu

Looking for host pool.ntp.org and service ntp
transmit(209.114.111.1)
transmit(206.197.161.242)
transmit(96.44.157.90)
transmit(209.114.111.1)
transmit(206.197.161.242)
transmit(96.44.157.90)
transmit(209.114.111.1)
transmit(206.197.161.242)
transmit(96.44.157.90)
transmit(209.114.111.1)
transmit(206.197.161.242)
transmit(96.44.157.90)
transmit(209.114.111.1)
transmit(206.197.161.242)
transmit(96.44.157.90)
209.114.111.1: Server dropped: no data
206.197.161.242: Server dropped: no data
96.44.157.90: Server dropped: no data
server 209.114.111.1, port 123
stratum 0, precision 0, leap 00, trust 000
refid [209.114.111.1], delay 0.00000, dispersion 64.00000
transmitted 4, in filter 4
reference time: 00000000.00000000 Wed, Feb 6 2036 23:28:16.000
originate timestamp: 00000000.00000000 Wed, Feb 6 2036 23:28:16.000
transmit timestamp: d3289d1f.232cce6e Thu, Apr 5 2012 15:37:19.137
filter delay: 0.00000 0.00000 0.00000 0.00000
0.00000 0.00000 0.00000 0.00000
filter offset: 0.000000 0.000000 0.000000 0.000000
0.000000 0.000000 0.000000 0.000000
delay 0.00000, dispersion 64.00000
offset 0.000000

server 206.197.161.242, port 123
stratum 0, precision 0, leap 00, trust 000
refid [206.197.161.242], delay 0.00000, dispersion 64.00000
transmitted 4, in filter 4
reference time: 00000000.00000000 Wed, Feb 6 2036 23:28:16.000
originate timestamp: 00000000.00000000 Wed, Feb 6 2036 23:28:16.000
transmit timestamp: d3289d1f.56604fee Thu, Apr 5 2012 15:37:19.337
filter delay: 0.00000 0.00000 0.00000 0.00000
0.00000 0.00000 0.00000 0.00000
filter offset: 0.000000 0.000000 0.000000 0.000000
0.000000 0.000000 0.000000 0.000000
delay 0.00000, dispersion 64.00000
offset 0.000000

server 96.44.157.90, port 123
stratum 0, precision 0, leap 00, trust 000
refid [96.44.157.90], delay 0.00000, dispersion 64.00000
transmitted 4, in filter 4
reference time: 00000000.00000000 Wed, Feb 6 2036 23:28:16.000
originate timestamp: 00000000.00000000 Wed, Feb 6 2036 23:28:16.000
transmit timestamp: d3289d1f.8991f8fb Thu, Apr 5 2012 15:37:19.537
filter delay: 0.00000 0.00000 0.00000 0.00000
0.00000 0.00000 0.00000 0.00000
filter offset: 0.000000 0.000000 0.000000 0.000000
0.000000 0.000000 0.000000 0.000000
delay 0.00000, dispersion 64.00000
offset 0.000000

5 Apr 15:38:54 ntpdate[1562]: no server suitable for synchronization

I have 3 windoze and 1 Ubuntu computers that have no NTP problems. However, 1 Windoze unit needs its connection constantly repaired for DNS problem. I have tried turning that computer off in case it was screwing with DNS, but it is not.

I have another pogo with exactly the same problem (I cloned the rootfs, so I am not surprised). I have the problem on one even when the other is unplugged, so they are not interfering with each other. Even though they are clones, I geve them different IP's and updated mac_addr in /usr/locals.

I am out of ideas. Sigh. Any help would be appreciated.

Thanx to Warheads and Geoff for their help so far on this,

EDIT: "I have 3 windoze and 1 Ubuntu computers that have no NTP problems."

Actually, I did have ntp problems on all of those computers. 3 were synced to one master that was, in turn, running on its hardware clock and not being synchronized at all. Life is soooooo complicated. Leaving my router open to the world solved my time problems, but promises some sort of security nightmare in the future. I synched all my systems and plugged the hole in my router. Not much better than just setting Date and Time manually, but probably not a problem with my computers... I must budget for another router....

[WarheadsSE]

Is there possibly something out there causing the NTP protocol to be shat upon? A firewall or something that for some reason magically borks NTP?

[Geoff]

Is there another computer connected to the same router (or any router bridged to it) configured to use the same static IP address? Is your chosen static IP address within the address range of the DHCP pool of the router (better if not)?

$this->bbcode_second_pass_quote('WarheadsSE', 'I')s there possibly something out there causing the NTP protocol to be shat upon? A firewall or something that for some reason magically borks NTP?

[pepedog]

I have seen mention of fakeclock on arch, brought up before network and ntp
http://www.raspberrypi.org/forum/distributions/fedora-arm-on-raspberry-pi/page-15
Post 214
Seems a good thing, can't find an arch package though

[darth]

Thanks pepe, I found the posting very interesting. Being a complete Noob to all things Linux, I barely fathom the significance, but I did read elsewhere that having a clock that is horribly out of synch with reality can do bad things to hapless pogos. Then again... perhaps its me that is out of synch. Reality and I have had a troubled relationship and currently aren't speaking to each other.

[pepedog]

Most plugs don't have a hardware clock, they forget the time and ends up in year 1970.
When you login, it wants to force you to change password. A lot of things fail.
What that daemon does is look at dates in logs, and sets date to something reasonable.
Then you get the network, then ntp sets clock, if either fails things are not too bad.
I haven't tested that script.