cannot see web page, but can see ftp and telnet

logos · 01-16-2002, 01:23 PM

so here is the thing...I can ftp and telnet to my machine, but I cant see the web page. Inside the LAN, I can see the page, but the router has been configure to let port 80 in. Apache goes up without any errors, so I don't really know if its linux, apache, or the router...someone please narrow my options..thanks...

Redhat 7.2 box

jrocha · 01-16-2002, 02:07 PM

i don't know how newbie you are, but you can type on your server:

ps -e|grep httpd

if you obtain a response, there is an httpd server runing and the problem now trully turns a problem, else, yo should start up your web server using:

/etc/rc.d/etc.d/httpd start

or some script for start up your http daemon

i hope this helps.

logos · 01-16-2002, 02:23 PM

well..i'm no hardcore admin...but I know my way around the box pretty well...

apache has been reinstalled with the latest ver...so its on /usr/local/apache and I am starting it up manually...
I have killed all the processes (httpd) and restarted it..and it starts clean, no errors in the log. So it does appear to be another issue, cause like I said, I can see the web page from inside the LAN, but not from the outside. Thanks all...

logos · 01-16-2002, 04:52 PM

so here's my thing now..i discovered that if i move it to any other priviliged port (like 81) I can see the page externally..that means that its not the router, or apache...it must be good ole linux...somewhere in there the port 80 is disabled...now can anyone tell me where? thanks...

Scotty2435 · 01-16-2002, 11:18 PM

actually i had the same problem. As it turns out port 80 is filtered on a lot of cable modem isps. A BSD guru I knew used nmap to figure that out. That's probably it so I don't think theres anything you can do about it. On my isp's contract you're not even supposed to run web and maby even ftp servers

finegan · 01-17-2002, 04:10 AM

You might want to download nmap from www.insecure.org and see if this is the case. I have the same problem with my Cable ISP, but as I'm sponging my connection off of a neighbor via a wireless LAN, I really can't complain. We found that almost all of the service ports below 1024 were blocked off, so we just set up a number of sshd's listening on high ports. This won't help you read public, but at least I can corroborate that you're not alone.

So to be certain, you set your webserver to listen to port 81 and it loaded externally? If that's it, yeah, its probably blocked from the outside.

Cheers,

Finegan