Webserver not accessible outside local network. 1

[urizen]

I have a small routing and web server running Redhat 6.2, and just installed Apache 1.3.22 (Or something like that).

This machine has to NICs, one going to my cable modem, and the other connected to my local network. (This machine allows connection sharing for the other peeps in my house.)

The server is up and running just fine, no errors or blips, and I can access it perfectly with any computer on the local network, but when anyone else tries to reach it from the outside, the get a not-responding error.

I have tried adding "Bindaddress 24.31.x.x" to the conf, and both "listen 24.31.x." and "listen 80" and it still will not work.

If anyone knows whats up with this, please let me know, any advice is appreciated.

 

[urizen]

Mehaps I should post the address so you guys can try it. My friends may just be having stupid problems.

http://fade.to/urizen

 

[ifincham]

Hi,

For that url, I get a page with redirection to

http://nic-118-c97-228.mn.mediaone.net

. Presumably the redirection page is served up by the fade.to domain.

I can ping this address successfully but it just times out on http . Assuming you are not using a firewall on port 80 yourself, it could be that your ISP is blocking port 80 - it has been known. You could always ask them and/or try running on a non-standard port and see if that works .

Hope this helps

 

[urizen]

Yeah, I tried port 8080 and 1234, and it didn't work. I'm wondering if ATT is activly watching for http requests the are coming in and denying them. (that link was a redirection). I'm gonna call and see if that may be the case.

 

[RhythmAce]

WAIT!!! DON'T DO THAT!!! Wanna get us all in trouble? :O) I have att broadband internet service which up until a few days ago was Excite @Home in the Bay Area. If you are running Windows, you can download a program called portdetective from

http://www.portdetective.com.

If you're running linux, you can search for "portscan" and it will list a few places that will scan your ports online and give you a report. Most ISPs frown on users running their own servers regardless of how little bandwidth they use. So if I wake up in the morning and att is wise to me, I'll know who to blame. )

 

[ifincham]

Hi,

If you don't have an external linux box to run nmap on you can run the grc.com test from you browser on the linux box. That causes a scan to be run against your IP address that should show open ports, etc.

https://grc.com/x/ne.dll?bh0bkyd2

.

Another obvious thing for you to do would be to (temporarily) run another server, e.g. telnet-server, wu-ftpd (ftp server), and see if you can remotely connect to that. This should establish whether your problem is limited to http.

Also, do you have the cable modem connected to a router or hub/switch ? If its a router, that itself may have some firewalling active.

Hope this helps

 

[urizen]

Hehe, all I call is my friend that works there, he usually knows what's going on. It seems that I should be able to do it, as prot 8080 is open (80 isn't), but it's probably just some freaky server problems.

I can use remote FTP and Telnet. I usually do this from work occasionaly to send something home. It's just the Apache server that doesn't want to work.

The box in question is connected directly to the modem on eth0, and eth1 is connected to my hub so everyone else in the house can mooch of the cable.

 

[RhythmAce]

I didn't know i had nmap - that's why you make the big bucks. )