Click to See Complete Forum and Search --> : Accessing APache Server


Jeffie
09-03-2002, 01:24 AM
I have installed Redhat 7.2 and APache Server 1.3.20. I managed to get the Apache server running so I can see the default index.html page on the Linux system by going to http://localhost.
When I try to get to the Linux system from my W2K system running IE, it can't find the page. I can ping the Linux machine from the Win system.
The Linux box is set to 192.168.1.100, the W2K is .103. I have them connected via a 10/100 hub that has a Linksys router connecting to the DSL bridge for the outside world and all of the computers here connect fine outside.
I have tried setting the server name to www.system.com and also with the IP address, but can't get to the server from the other machine.
HELP ME BEFORE I REBOOT AGAIN!!!!!!!!

:confused:

peeps_59
09-03-2002, 10:55 AM
I'm pretty new to this, too. But this is what I have learned so far (any of you ancient grasshoppers feel free to correct me).

If the router is set up for port forwarding of port 80, then all of the machines on the sub-net will need to access the web page via your IP address not your FDN (fully qualified domain name), i.e. they cannot access via http://www.my_domain.com they must use http://192.168.1.100

That being said, I know you said you tried it both ways. Did you edit the ~/conf/httpd.conf file? There are a couple of places you need to look at as far as access (Search for '<Directory' and read the comments very closely and alter as applicable), and one place where you need to enter your FDN

Hope this helps.

flav2000
09-03-2002, 11:42 AM
Redhat by default sets up the system's firewall to block all incoming requests.

You have to reconfigure the firewall rules (through ipchains or iptables - iptables is newer and better) to open up your port 80. Unless you do that the apache server can only be seen on the linux box.

That's the reason you can ping the box but cannot reach the server from local machines.

Another quick way you could test this is to drop your security (for a short little while only) and see if you can see the web server. If dropping security levels to low allows you to see the web server then it's definitely a firewall configuration problem.