On Thu, 2002-03-28 at 13:43, Michael D. Schleif wrote: > > Tom Eastep wrote: > > > > You'll have to open up TCP 37 from your firewall to the net in order to use > > rdate. > > > > -Tom > > > > ----- Original Message ----- > > From: "Stephen Lee" <[EMAIL PROTECTED]> > > To: "Leaf-user" <[EMAIL PROTECTED]> > > Sent: Thursday, March 28, 2002 1:05 PM > > Subject: [Leaf-user] rdate, udp and Bering > > > > > 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? > > rdate works on my several DCD's without tcp/udp 37. All we have open > are: > > ntp 123/udp Network Time Protocol >
Adding port 37 to FW_TCP_OUT_PORTS in Bering got rdate working. Adding port 123 (either udp or tcp) did not work for me. Thanks for the help! Stephen _______________________________________________ Leaf-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-user
