Never mind... Apparently, even though I asked her if her firewall was really down, it wasn't.
I've shown her how to enable 123 in the firewall port. On Mon, 2007-10-15 at 16:47 -0500, Bryen wrote: > On Mon, 2007-10-15 at 14:25 -0700, Sloan wrote: > > Bryen wrote: > > > I'm forwarding this question from a colleague of mine... > > > > > > She's trying to set up an ntp server one one box and ntp client on the > > > other box. > > > > > > The client seems to work fine because when pointing it to a public ntp > > > server, everything works. But when pointing to the internal ntp server, > > > connection is failed. > > > > > > As a test, the firewall has been disabled on the server. > > > > > > What else must be done to make the server an ntp server and accept > > > connections? > > > > > > > It should just work. > > > > Please provide the output of the following command to be run on the ntp > > server: > > > > ntpq -pn > > > > > > Joe > > According to her results which she emailed me: > remote refid st t when poll reach delay offset > jitter > ============================================================================== > 127.127.1.0 LOCAL(0) 10 l 50 64 377 0.000 0.000 > 0.001 > *216.218.254.202 .CDMA. 1 u 51 64 373 83.299 -20.827 > 125.720 > +66.220.9.122 10.200.208.2 2 u 48 64 377 85.737 -12.030 > 156.947 > > She also verifies that the client machine and the server machine can > both get NTP from a public ntp server. It is just that client machines > cannot connect to the internal server machine. > > NTPDate, from the client machine, also says "no servers can be used, > exiting" > > > -- > ---Bryen--- > -- ---Bryen--- -- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
