Kent Borg <[EMAIL PROTECTED]> writes: >> > [root@mail etc]# ntptrace >> > localhost.localdomain: stratum 16, offset 0.000033, synch distance >> > 0.00005 >> > 0.0.0.0: *Not Synchronized* >> > >> > Does it work? or not work? >> > How do I know it? > > Recently I have fired up a new RH 7.3 machine and I would like to have > it sync to the basement machine--but it won't. > > [root@tb rpm]# ntpq -p > remote refid st t when poll reach delay offset jitter > ============================================================================== > borg.org 0.0.0.0 16 u - 1024 0 0.000 0.000 4000.00 > [root@tb rpm]# >
Looking at what is happening on the network tcpdump -i eth0 -s 1600 -vv port ntp helps me a lot in those cases. (Substitute appropriate interface for eth0.) Look at what happens when you restart ntpd, or while doing ntptrace. I do not know what RH's default firewall rules do with ntp - might be worth a look. Also, maybe they have some kind of "reject all" acl entry in ntpd's config file. So long, Joe -- "I use emacs, which might be thought of as a thermonuclear word processor." -- Neal Stephenson, "In the beginning... was the command line" _______________________________________________ Redhat-list mailing list [EMAIL PROTECTED] https://listman.redhat.com/mailman/listinfo/redhat-list
