Markku thanks ...

I uncommented those lines and you were right about the firewall config.
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?  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?  if someone had a bit of time to explain
this, i would sleep better tonight.

one of those guys who can't sleep if it don't workie,
chuck

This is my client ntp.conf file:

server  192.168.0.1     #ip of ntp server for network

server 127.127.1.0     # local clock
fudge  127.127.1.0 stratum 10

logfile /var/log/ntp.log        # me added for sanity sake

file /etc/ntp/drift
multicastclient                 # listen on default 224.0.1.1
broadcastdelay  0.008

authenticate no



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

Reply via email to