Just for future reference, when you turned off the firewall you either stopped iptables (for good) or cleared out all of the rules. There was no need to issue a stop to iptables after disabling the firewall.

Josh Luthman Office: 937-552-2340 Direct: 937-552-2343 1100 Wayne St Suite 1337 Troy, OH 45373

Those who don't understand UNIX are condemned to reinvent it, poorly. --- Henry Spencer

On Tue, Dec 9, 2008 at 11:47 AM, <MFisher at hra.com> wrote:

I would probably agree that SELinux was the culprit. I was able to compile hobbit before when LIBPNG-DEVEL was not installed but it probably had errors i ddint see but wasnt extreme enough to halt the process. It is installed, and i couldnt have asked for more...Great app. Im sure I will be ehre again asking you gurus about some other stupid newbie crap.

Thanks for all your input!

On Tue, December 9, 2008 12:00, MFisher at hra.com wrote:

I thought so too, but after disabling the firewall i was still unable to access apache (80) from within my host windows machine...I was able to access apache locally from within the VM however. Upon stopping iptables, port 80 was now available to my host...I didnt dive into why but i know i was scratching my head for almost an hour....

You'll want to "chkconfig iptables off", or fix your iptables rules to trust port 80 inbound, or the problem will repeat when you reboot. Assuming you just did "service iptables stop" or the equivalent.

"iptables-save" will dump your iptables to stdout. You're probably missing a rule like: -A INPUT -p tcp -m state --state NEW -m tcp --dport 80 -j ACCEPT before the default REJECT. On Fedora 9 you can fix it with the system-config-firewall gui if you don't want to learn about the rule syntax, ordering, and flow.