Redhat NTPD Clock

[Bob McClure Jr]

On Fri, May 26, 2006 at 08:27:16AM -0400, John Wirt wrote:
> 
> 
> John Wirt wrote:
> 
> >Bob McClure Jr wrote:
> >
> >>On Thu, May 25, 2006 at 09:26:57PM -0400, John Wirt wrote:
> >> 
> >>
> >>>Hmm..can you  tell me how to set the security level?
> >>>
> >>>Thank you, Rick.
> >>>
> >>>John Wirt
> >>>  
> >>
> >>
> >>We prefer bottom posting here.  See
> >>
> >>http://en.wikipedia.org/wiki/Top-posting
> >>
> >>Try "firewall-config".
> >>
> >> 
> >>
> >When I enter "firewall-config" as a command, the response is "command 
> >not found"
> >
> >When I enter "iptables -h" as a command. the response is "command not 
> >found"
> >
> >What should I do?
> >
> >John Wirt
> 
> 
> PS, also I have no Internet access the desktop.

Not sure what you mean by that.  Post the results of "netstat -rn".
You can do that as your mere mortal self.

> No errors other than the 
> clock.redhat.com error is reported on boot up.
> 
> - - - - - - - - - - - - - - - - - -
> 
> >
> >>>Rick Stevens wrote:
> >>>
> >>>  
> >>>
> >>>>On Thu, 2006-05-25 at 00:58 -0400, John Wirt wrote:
> >>>>
> >>>>
> >>>>    
> >>>>
> >>>>>Thanks you several of you, I have RedHat booting to completion 
> >>>>>just fine except for one problem.
> >>>>>
> >>>>>Near the end of the boot sequence, RedHat apparently tries to 
> >>>>>connect to some time standard at 66.187.224.4. The sequence is:
> >>>>>
> >>>>>
> >>>>>ntpd: Opening firewall for input from 66.187.224.4 port 123
> >>>>>ntpd: Opening firewall for input from clock.redhat.com port 123
> >>>>>iptables v 1.2.8: host/network clock.redhat.com not found [FAILED]
> >>>>>
> >>>>>  use iptables -h for assistance.
> >>>>>
> >>>>>However, iptables -h doesn't provide any help.
> >>>>>
> >>>>>What is the problem? How can I fix it?
> >>>>> 
> >>>>>
> >>>>>      
> >>>>
> >>>>You must have the firewall open ports for TCP and UDP port 53 (DNS).
> >>>>What's probably happening is that the system is trying to resolve
> >>>>clock.redhat.com (66.187.224.4 and 66.187.233.4) and can't because the
> >>>>firewall is blocking DNS issues.  This happens if you used the 
> >>>>"maximum"
> >>>>setting on system-config-securitylevel as that blocks EVERYTHING
> >>>>(including DNS).  Use the "medium" security setting.
> >>>>
> >>>>----------------------------------------------------------------------
> >>>>- Rick Stevens, Senior Systems Engineer     rstevens at vitalstream.com -
> >>>>- VitalStream, Inc.                       http://www.vitalstream.com -
> >>>>-                                                                    -
> >>>>-        Change is inevitable, except from a vending machine.        -
> >>>>----------------------------------------------------------------------
> >>>
> >>
> >>Cheers,
> >> 
> >>

Cheers,
-- 
Bob McClure, Jr.             Bobcat Open Systems, Inc.
bob at bobcatos.com             http://www.bobcatos.com
Jesus wasn't (and isn't) politically correct.
Send complaints to root at universe.gov.