Webserver/Router Help

[vadan]

I've searched every board I can find, and haven't found an answer to this seemingly simple problem. Please help!

I'm running a RH 7.2 webserver, with Apache, PHP, MySQL, et.al. I've got several Win98 clients on the network, held together with a Linksys BEFPV41 router.

Everything's apparently set up correctly. I can access the default page via 127.0.0.1, 192.168.1.20 (server IP) and can access it using the static WAN IP from anywhere inside the network. The problem is it cannot be seen from outside the network.

I've forwarded Port 80 to the server, and double checked with Earthlink DSL to ensure they weren't blocking port 80 (I've also tried ports 81, 8080 and 8800). Various port scanning utilities return 1 of 2 responses: Port 80 - Closed, unsecure (with no application using the port) or Port 80 - Open. In either event, the site is not accessible outside the network.

I've also tried updating the router's firmware, using 1.36, 1.37 and 1.42. None of these seem to make a difference, although running a port scan with v. 1.42 revealed ALL ports to be "stealthed".

Any ideas what I'm missing?

[Choozo]

How do you access the server from the outside?
Via dynamic IP assigned to the Linksys router?
(The 192.168.n.n range of IPs are not visible from the outside)

[SuperHornet]

If you can see it from the LAN on the correct port and can not see the site from outside the LAN then either NAT is not setup correctly or the router has a firewall bloking port 80.

[ 03 April 2002: Message edited by: SuperHornet ]

[vadan]

I connect via a static IP address from the ISP.

As to the router not being setup correctly, I would think if the port scan showed the port as open, or even closed, then the firewall was not blocking it. All non-forwarded ports show as stealthed.

Linksys' response was to enable Port Triggering for port 80, which I did. Still nothing.

Is it possible for Apache to time-out? Would this explain why the port is "open" during one scan, and "closed" later?

[SuperHornet]

That could be,
For a while my apache server would crash after X amount of time. Never could figure it out why, so I made a simple bash script to check to see if the server was running else restart it.
Check your error logs for httpd messages.

Since you tinkard with the port settings I would triple check the httpd.conf and make sure that all are on port 80.

Also make sure the server has a static IP and the router is correctly pointing to that IP.

[Football]

Look here in your httpd.conf


# ServerName allows you to set a host name which is sent back to clients for
# your server if it's different than the one the program would get (i.e., use
# "www" instead of the host's real name).
#
# Note: You cannot just invent host names and hope they work. The name you
# define here must be a valid DNS name for your host. If you don't understand
# this, ask your network administrator.
# If your host doesn't have a registered DNS name, enter its IP address here.
# You will have to access it by its address (e.g., http://123.45.67.89/)
# anyway, and this will make redirections work in a sensible way.
#
# 127.0.0.1 is the TCP/IP local loop-back address, often named localhost. Your
# machine always knows itself by this address. If you use Apache strictly for
# local testing and development, you may use 127.0.0.1 as the server name.
#
#February 11, 2002 ##########
#
# This is the External IP Address of my Router (WAN side)**********
#
ServerName 151.24.33.156

#February 11, 2002 ##########