Re: Re: [SLE] unable to acess apache web page I setup from outside of my lan
From: Sunny
Date: 2004/12/02 Thu AM 11:56:30 EST To: dasexton@cox.net CC: suse-linux-e@suse.com Subject: Re: Re: [SLE] unable to acess apache web page I setup from outside of my lan I am running Suse 9.1, I am not sure what version of apache I am using I think it's verson 2.0. And when I try to access my domain it times out. The domain name is sexton.homelinux.org IP 24.252.34.77. And like I said port 80 is setup to forward from the wlan to the lan then to my computer on the lan side .
Here is how my network configuration is setup. I have a dynamic ip address on wlan side. So I use dydns.org to keep the ip address up dated. The router is setup to forward port 80 from the wlan to my computer on the lan then to my suse box that has apache on it.
Hope this helps explain what i have going on more.
thanks for your help.
David
David, I allowed myself to nmap your machine. The only open port shown is 22 (ssh). So it seems that your router config is not ok. Port 80 is not open as far as I can see.
Here is the output:
sunny@linux:~> nmap -P0 24.252.34.77
Starting nmap 3.75 ( http://www.insecure.org/nmap/ ) at 2004-12-02 10:51 CST Interesting ports on ip24-252-34-77.om.om.cox.net (24.252.34.77): (The 1650 ports scanned but not shown below are in state: filtered) PORT STATE SERVICE 22/tcp open ssh 113/tcp closed auth 7000/tcp closed afs3-fileserver 7001/tcp closed afs3-callback 7002/tcp closed afs3-prserver 7003/tcp closed afs3-vlserver 7004/tcp closed afs3-kaserver 7005/tcp closed afs3-volser 7006/tcp closed afs3-errors 7007/tcp closed afs3-bos 7008/tcp closed afs3-update 7070/tcp closed realserver 7100/tcp closed font-service
Nmap run completed -- 1 IP address (1 host up) scanned in 51.767 seconds
Cheers Sunny
-- Get Firefox http://www.spreadfirefox.com/?q=affiliates&id=10745&t=85
-- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com
I did a nmap on my linux box from the lan side and I got the following. I don't see port 80 open. I am pretty sure the Suse firewall is off. How do know for sure that my suse box is not eating port 80?
nmap -P0 sexton.homelinux.org Starting nmap 3.50 ( http://www.insecure.org/nmap/ ) at 2004-12-02 11:10 CST Interesting ports on 127.0.0.1 (127.0.0.1): (The 1652 ports scanned but not shown below are in state: closed) PORT STATE SERVICE 22/tcp open ssh 111/tcp open rpcbind 139/tcp open netbios-ssn 445/tcp open microsoft-ds 887/tcp open unknown 2049/tcp open nfs 5801/tcp open vnc-http-1 Nmap run completed -- 1 IP address (1 host up) scanned in 0.081 seconds
I did a nmap on my linux box from the lan side and I got the following. I don't see port 80 open. I am pretty sure the Suse firewall is off. How do know for sure that my suse box is not eating port 80?
nmap -P0 sexton.homelinux.org
Starting nmap 3.50 ( http://www.insecure.org/nmap/ ) at 2004-12-02 11:10 CST Interesting ports on 127.0.0.1 (127.0.0.1):
You are testing localhost ... Try nmap 192.168.x.x or whatever your internal ip for that box is. Try both with and without -P0 and see the results. Also, on the affected machine, try: netstat -apn | grep 'tcp.*:80.*LISTEN' This will show you if a process is listening on port 80. -- Get Firefox http://www.spreadfirefox.com/?q=affiliates&id=10745&t=85
participants (2)
-
David Sexton
-
Sunny