Linux - NetworkingThis forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
What does your /etc/hosts.deny file look like? I may be on the wrong track here with these tcpwrappers but its worth a shot. Just to make sure that its not your tcpwrappers add:
ALL:ALL
to your /etc/hosts.allow file and then restart xinetd by doing:
I have a Ultra10 with Solaris 9, a NT 2002 Advanced Server and two Redhat 8.0 machines. All access a cable modem through an 8 port Linksys cable router.
All browsers on all machines can get outside the firewall, all browsers on all machines can acces web servers on the NT and Sparc machines. Apache is available locally on the Redhat machines, I can ping the interfaces on both Redhat machines, but I get access denied from Apache from inside the firewall.
This was a configuration issue. When Redhat 8.0 is first installed a firewall setting is established through lokkit. In this case it was the firewall setting that caused the connection refused messages when attempting to access apache remotely.
I had this problem as well, and just now figured a way around it. I, too, am using Red Hat 8.0 and am a new apache user (though I've fiddled with Linux for a little while). The lokkit application can be run by typing /usr/sbin/lokkit at a command line (as root). Strangely, once I made changes and selected OK, the changes were lost. I finally just stopped the iptables service and that fixed the problem. [ Red Hat button --> Server settings --> Services --> iptables, then click stop. You may wish to remove the check mark to prevent iptables from running at startup. ]
Um, certainly stopping iptables will solve the problem but only because you no longer have a firewall. If that computer is connected to the internet, it is toast.
A better approach would be to configure your firewall to allow traffic to port 80. iptables -L will display your firewall rules. If you have trouble, post 'em in a new thread and ask for help.
Yes, I'm very aware that that stopping iptables leaves no firewall. I posted quite literally moments after discovering that it was indeed a firewall issue. Perhaps I should have been more clear when I said "fix." It was really the first stage of a fix, the second being allowing only http traffic on port 80. Thanks for pointing that out.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.