David Sexton wrote:

...

From: Sunny Date: 2004/12/02 Thu AM 10:54:29 EST> To: dasexton@cox.net CC: suse-linux-e@suse.com Subject: Re: [SLE] unable to acess apache web page I setup from outside of my lan> On Thu, 2 Dec 2004 10:40:30 -0500, David Sexton wrote:

...

I have setup apache and every thing seems to be working fine. I can access it from with in my LAN. How ever I am unable to access it from the outside. I have the router setup to forward port 80 to the computer with apache on it. But it dose not work. I have ssh setup setup in the same manner and it works fine. I wonder if there is some setting that deny outside ip's in apache.

Thanks

David

David, it is unlikely someone to respond. There is no enough data. What version of apache? What version of Suse? What exactly happens - unable to access is to wide as a meaning. Any error messages? Timeouts? Have you tries to telnet to port 80 from outside? Etc. To many things to guess.

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

Ok,

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

Are you sure the router does not have a firewall that also needs opening? I know some let you forward stuff, but dont open the port on the firewall, this has to be done seperately. telnet sexton.homelinux.org 80 times out for me, here is an nmap: nmap -P0 sexton.homelinux.org Starting nmap 3.50 ( http://www.insecure.org/nmap/ ) at 2004-12-02 16:44 GMT Interesting ports on ip24-252-34-77.om.om.cox.net (24.252.34.77): (The 1644 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 7009/tcp closed afs3-rmtsys 7010/tcp closed ups-onlinet 7070/tcp closed realserver 7100/tcp closed font-service So from that I would say that port 80 is definately being eaten by your router. Check that if you are running SuSEFirewall2 it allows 80 as well. Hope that helps