Port 80 isn't open

tekmann33 · 02-13-2007, 06:54 PM

I just installed apache2 on a Fedora Core 6 machine. I have it running properly and I can get the "It Works" page to come up when I put in the local private address of the server "192.168.1.103"

However, I cannot access it remotely from within the same private network. I checked the firewall setting "System/Administration/Security level and firewall and made sure both http and https were checked.

I totally disabled the firewall and SELinux and I still had the same issue where I could not get to the web page remotely.

I ran an nmap on the apache server ip and came up with the following:

Code:

[root@BriansRH ~]# nmap 127.0.0.1

Starting Nmap 4.11 ( http://www.insecure.org/nmap/ ) at 2007-02-13 18:52 CST
Interesting ports on localhost (127.0.0.1):
Not shown: 1675 closed ports
PORT     STATE SERVICE
22/tcp   open  ssh
25/tcp   open  smtp
111/tcp  open  rpcbind
707/tcp  open  unknown
6000/tcp open  X11

Nmap finished: 1 IP address (1 host up) scanned in 0.135 seconds
[root@BriansRH ~]#

Shouldn't I see port 80 as being open? If so, how do I correct this?

Brian1 · 02-13-2007, 07:02 PM

nmap should show port 80 open if you are searching for it and the service is running. Firewall would not matter because you are access the loopback interface. The firewall can still be blocking so you would need to use the lan IP instead of the loopback interface IP.

Are you saying you cannot use the external IP of your network to get to the webserver?

Now if you are at a remote site can you see your webserver?

Is there a router between the machine and the internet?

If yes to all three and the router is a store bought router then this is normal for them. The store bought routers lack the ability to use the external IP from within the lan side.

Brian

tekmann33 · 02-13-2007, 07:18 PM

Quote:

Originally Posted by Brian1

nmap should show port 80 open if you are searching for it and the service is running. Firewall would not matter because you are access the loopback interface. The firewall can still be blocking so you would need to use the lan IP instead of the loopback interface IP.

Are you saying you cannot use the external IP of your network to get to the webserver?

Now if you are at a remote site can you see your webserver?

Is there a router between the machine and the internet?

If yes to all three and the router is a store bought router then this is normal for them. The store bought routers lack the ability to use the external IP from within the lan side.

Brian

I cannot use the external IP 192.168.1.103 of my web server from a machine within the same 192.168.1.X network to access apache. I can access the web page if I type in that address on the server itself, but I am unsuccessful from any other machine in my private network.

My network is basically 4 machines hooked into a linksys router. My machines all have private static IP's

Brian1 · 02-13-2007, 07:30 PM

Have you runned a port scan from one of the other machines on the webserver to see if the port is open?
Can you ping the webserver from another machine?

Brian

tekmann33 · 02-13-2007, 07:57 PM

It seems as if I cannot ping nor port scan my server from within my network.

Code:

C:\Program Files\Nmap>nmap 192.168.1.130

Starting Nmap 4.20 ( http://insecure.org ) at 2007-02-13 19:
Time
Note: Host seems down. If it is really up, but blocking our

Nmap finished: 1 IP address (0 hosts up) scanned in 0.291 se

C:\Program Files\Nmap>ping 192.168.1.130

Pinging 192.168.1.130 with 32 bytes of data:

Request timed out.
Request timed out.

I get the same results when I disable the firewall and SELINUX. Not sure what is going on.

My server is up and running. I can ping other machines from the server and I receive internet access as well.

Strange.

btmiller · 02-14-2007, 01:56 PM

Try doing a netstat -tan to make sure that Apache isn't just listening on the loopback interface, but actually waiting for connection on the external interface.

Also, just for fun, please post your iptables -L just to make sure that the firewall is completely disabled.

Brian1 · 02-14-2007, 03:26 PM

Are you sure the IP is correct? Do an ' /sbin/ifconfig -a ' and post the output.

Why you cannot ping it is really odd unless being blocked somewhere.
No iptables or selinux is running?
What is in your /etc/host.allow and /etc/host.deny files?
To flush the iptables run the command as root ' /sbin/iptables -F '.
Post the contents of /etc/sysconfig/network-scripts/ifcfg-eth0.

Brian