**UPDATE** This was solved. I looked at the traffic and wireshark and saw that the NTP responses were missing a lot of information. I went to the vendor site again and noticed that there was an option for a firmware update. The firmware running was released in December 2011. They JUST released a patch in January of this year. I'm guessing the recent NTP security patches broke whatever implementation they settled on back in 2011. Firmware saved me a lot of time and my systems appear to be happy again.
I'm trying to troubleshoot some NTP server devices(GPS appliance). These boxes report as being online and functional. They appear to be working, but I noticed that when I restart the ntpd client on one of my linux servers, it's not synchronizing with the time servers:
Code:
/etc/init.d/ntpd restart
Shutting down ntpd: [ OK ]
ntpd: Synchronizing with time server: [FAILED]
Starting ntpd: [ OK ]
I switched to my desktop and am having trouble connecting to the time servers as well. When I try to query the server in linux, I keep getting timeouts.
Code:
$ ntptrace 192.168.1.100
192.168.1.100: timed out, nothing received
***Request timed out
Code:
$ ntpdate -q 192.168.1.100
server 192.168.1.100 , stratum 16, offset -0.001145, delay 0.03400
7 Apr 14:34:29 ntpdate[29434]: no server suitable for synchronization found
I can replace those IPs with time.windows.com or 0.rhel.pool.ntp.org, etc...and I get a proper response using 'ntpdate -q'.
I can ping the ip address, firewall is open for 123 UDP in/out....and it responds in windows.
I can get a valid response via a Windows using this:
Code:
w32tm /stripchart /computer:192.168.1.100 /dataonly
Any ideas what I should try from here? I'd like to avoid breaking out wireshark if I can...