On Tuesday 31. Julyta 2001 20:54, you wrote:
> All seems to be working now on the server, but my clients have this
> output from ntpq -p
>      remote           refid      st t when poll reach   delay   offset
> jitter
> ===========================================================================
>=== 192.168.0.1     0.0.0.0         16 u    -   64    0    0.000    0.000
> 4000.00
> *LOCAL(0)        LOCAL(0)        10 l   51   64  377    0.000    0.000
> 0.000
>
> any ideas?

They can't communicate with the local server. More firewalling? Try
"ntpdate -d -u 192.168.0.1" and see if you get any "receive" responses to the 
"transmit" lines.

>  i don't understand really how the server can have 123 socket
> connected to the internet to get time as well as serve time from that
> same socket to the clients?

The socket isn't "connected", ntp uses UDP. The socket is 
receiving packets that can be either responses from servers or requests from 
clients, and the contents of the packet tells which it is.

-- 
        Markku Kolkka
        [EMAIL PROTECTED]



_______________________________________________
Seawolf-list mailing list
[EMAIL PROTECTED]
https://listman.redhat.com/mailman/listinfo/seawolf-list

Reply via email to