Re: options - Re: ntp server
On Fri, 2004-06-25 at 06:36, Greg Folkert wrote:
> [greg@prt:greg]$ dpkg -l | grep ntp
> ii ntp 4.2.0a-8 Network Time Protocol: network utilities
> ii ntp-doc 4.2.0a-8 Network Time Protocol: documentation
> ii ntp-server 4.2.0a-8 Network Time Protocol: common server tools
> ii ntp-simple 4.2.0a-8 Network Time Protocol: daemon for simple sys
> ii ntpdate 4.2.0a-8 The ntpdate client for setting system time f
I have the same package set installed.
> Gives me this (I use IP addys so I don;t have to worry about DNS
> failing)
>
> [greg@knight:greg]$ ntpq -cpe
> remote refid st t when poll reach delay offset jitter
> ==============================================================================
> LOCAL(0) LOCAL(0) 12 l 837 1024 377 0.000 0.000 0.001
> *192.168.1.200 132.163.4.101 2 u 47 1024 377 0.218 -31.756 7.610
>From my laptop I get the following:
zen8100a:~# ntpq -cpe
remote refid st t when poll reach delay offset jitter
===================================================================
whiskas .INIT. 16 u - 1024 0 0.000 0.000 4000.00
*LOCAL(0) LOCAL(0) 13 l 207 1024 377 0.000 0.000 0.001
Which, when I read the man page
(file:///usr/share/doc/ntp-doc/html/ntpq.html) for ntpq, seems to say
that the space at the start of the "whiskas" lines means that server is
not available. Given its delay and offset of zero, this also makes
sense.
The port is accessible:
---
zen8100a:~# nmap -sU -p 122-124 -vv whiskas
Starting nmap 3.50 ( http://www.insecure.org/nmap/ ) at 2004-06-25 17:03
EST
Host whiskas (192.168.0.4) appears to be up ... good.
Initiating UDP Scan against whiskas (192.168.0.4) at 17:03
The UDP Scan took 2 seconds to scan 3 ports.
Adding open port 123/udp
Interesting ports on whiskas (192.168.0.4):
PORT STATE SERVICE
122/udp closed smakynet
123/udp open ntp
124/udp closed ansatrader
Nmap run completed -- 1 IP address (1 host up) scanned in 2.350 seconds
---
So why oh why can't my ntp programs reach my server?
tia
zen
Reply to: