Hello Stephen, Michael > > Stephen Lee wrote: > > > > On Thu, 2002-03-28 at 12:56, Michael D. Schleif wrote: > > > > > > > > > Thanks. I installed xntpd.lrp and pointed it to one of the public ntp > > > > servers. The problem is that my hardware clock is so far off that it's > > > > going to take ntpd a long time to synchronize the local time to the > > > > remote ntp server time. I would normally use rdate to do a quick fix but > > > > in this case rdate doesn't work with tock.usno.navy.mil. It, like all of > > > > the other rdate servers tried, only accepts udp queries. I suppose if > > > > all else fails I could manually set the time with 'date' and 'hwclock'. > > > > > > Try this: > > > > > > rdate -s ntp0.cornell.edu > > > > > > > I get "rdate: ntp0.cornell.edu: Connection refused" on Bering boxes but > > it works on Eigerstein2b boxes. Could there be some firewall setting > > causing this problem? as Tom allready stated it is. rdate uses port 37 and this is denied by default change shorewall settings 1 ) params
FW_TCP_OUT_PORTS=53,37 and restart shorewall (don't forget to backup ) > I do not know which `rdate' is in Bering. Dachstein, &c. uses busybox > rdate. Bering uses also Busybox v0.60.2 rdate > Regarding firewalled ports, have you checked these? > > ntp 123/tcp Network Time Protocol > ntp 123/udp Network Time Protocol > With me rdate ntp0.cornell.edu functions after the modification i indicated above. The connection refused comes from your own router not from the timeserver. PS you are talking about using rdate from the router not from a linux machine in the internal network ? The parameter I talked about before is firewall ---> timeserver. otherwise the firewall should not be blocking. Regards Eric Wolzak member of the "bering crew" ;) _______________________________________________ Leaf-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-user
