Well, I appear to be having problems getting my httpd server up and running on RH9. Here is what I know for sure.

------------------------------
1. The answer is looking right at me and I am just not able to see it.

2. httpd is started and running

3. http://127.0.0.1 does work and I see the pages just fine.

4. http://192.168.1.102 (my servers IP address) will not dispaly the pages even on the local machines browsers. All I get is "The connection was refused when attempting to connect to 192.168.1.102".

5. The network is working as I am using it now to surf the web and post this message.
---------------------------------

Eveything appears to be configured correctly and working, except for the fact that any attempt to connect beyound the 127.0.0.1 fails.


Anyone have any ideas? I am still surfing the web and trolling message boards is search of what must be a simple answer.

Could it be your firewall dropping outside connections to port 80?

Do not think it is that. I have 4 computers on my home network 2 workstations, one voicechat server (win98) and one webserver (rh9). When I am on any computer on my internal network and attempt to get to my webserver, entering the internal IP address of 192.168.1.102, I get "page not found error" and when I attempt to get to 192.168.1.102 from the webserver I get the error message. My hardware router (Linksys) is configured to route port 80 traffic to 192.168.1.102. My software firewall (on RH9) I turned off, thinking that it was indeed blocking me. I continued to get the same results. Starting and stopping httpd did not seem to make any difference.

I am still researching why this is, but no luck yet. I am also very sure that I am looking right at the answer but not abel to see it.

Follow up.

I just turned off my port 80 forwarding at my router (Linksys) and received a user id/password prompt for my router. I was able to get in to the router. So, not sure what that tells me but at least it gives me a palce to start.

Try running "nmap 127.0.0.1" and "nmap 192.168.1.102" from the webserver and see if it indicates that port 80 is open.

Ian

Well, that is sheding more light on the issue.

127.0.0.1 shows port 80 open

192.168.1.102 shows port 80 closed.

So, I must be looking in the wrong place as i have port 80 being monitored in httpd.conf.

Any ideas on what area I over looked in configuring?

Run , as root, "iptables -L" to see if there are any firewall rules still in place, if there are, "iptables -F" will flush those rules.

Also check thet there is no line anywhere in your httpd.conf thet says "Listen 127.0.0.0:80".

Ian

As far as I know:
127.0.0.1 is local to your pc, via the loopback interface(lo)
192.168.x.x is local to your private network, via your network card(eth0)
Your firewall may be allowing outbound port80/webpage connections from the server, and internal connections (127.0.0.1) but not allowing external connections to start chatting to things on your port80.
How are you configuring your firewall?
Try something like Guarddog maybe? (See in my first link below)

iptables gives me a "command not found" error.

httpd.cong has "Listen *:80"


I am still looking for the iptables (guess it is not mapped)

"/sbin/iptables" is where it is.

Ian

followup

iptables is in the /sbin directory as expected but even from the same directory I get the error that it cannot be found

[root@localhost sbin]# ls iptables
iptables
[root@localhost sbin]# iptables -L
bash: iptables: command not found

Just specify the full path: "/sbin/iptables -L"

If you are in the same directory, you need to use "./iptables"

Ian

Thanks, that did it. This is what was returned.


[root@localhost sbin]# /sbin/iptables -L
Chain INPUT (policy ACCEPT)
target prot opt source destination

Chain FORWARD (policy ACCEPT)
target prot opt source destination

Chain OUTPUT (policy ACCEPT)
target prot opt source destination

OK, so we know that the firewall is not the problem, so try putting a line in your httpd.conf thet reads "Listen 192.168.1.102:80", and restarting apache.

Ian

followup

I am guessing now that it has something to do with the DNS in RH9. The DNS entry there is 127.0.0.1.


OK, our post crossed each other. I will go tell it to listen to 192.168.1.102 and see what happens.