Random access issue with webserver

Hi,


The basic problem I have is that I can access my website within the LAN and even from some machines in the outside world but not others (it times out at work). It definitely seems like a network config/apache issue, I'm just pulling hairs trying to figure out what it is. I mean, I would understand if nobody in the outside can see it, but this is making it very hard to debug.

Like I mentioned, it times out through a browser here @ work but using a tool @ samspade.org, it returns the proper source code:

URL
(I have a dynamic ip, so I'll edit this if it refreshes)

Has anyone heard or dealt with anything like this before? Any help would be appreciated, even if it's just pointing me to another board. I'll list all the info I can below.

Thanks in advance!

====================
My set up:

> Apache 1.3.19
> Redhat 7
> Linksys 4 port router
- Webserver has static ip where ports 80, 21, 22 are routed.
- Firmware 1.37.9
> Pacbell DSL service (dynamic ip)
====================
Details/Theories:

> On the same work machine where I can't see the webserver through a browser, I can ftp and ssh into it.
> I thought Pacbell might have been blocking port 80 (since I have dynamic ip service) in the beginning, but that wouldn't explain why people can access it.
> Network settings in linuxconf not configured correctly?
> I haven't tweaked anything with httpd.conf in Apache, in fact, I just reinstalled the whole webserver this weekend because it was driving me crazy.
> Settings in linksys router off?
====================
History:

> I had a static ip through Pacbell but had to switch to the dynamic service. Everybody could see it when it was static. When I went dynamic, I changed domain names too - those are the only two factors that are different in the before and after setup. (Of course now all of the network settings are tailored towards the new domain since I blew everything and started over again this weekend.)

You forgot to provide the most important info - your domain name.

>> On the same work machine where I can't see the webserver through a browser, I can ftp and ssh into it

FTP/SSH by IP or hostname?

It shouldn't matter that I connect via domain name (should it?). I would think that it's better for debugging purposes to hit the WAN IP (be it by the web browser, ftp, or ssh) instead of the domain name to skip the extra step of going through the DNS servers - it isolates the problem to being an internal one (router, network settings, etc) instead of adding an extra factor of the dynamic DNS service.

Thanks for the reply, I actually got it to work now. It turned out to be the firmware version of the router I had installed (unfortunately, I had upgraded it around the same time I switched to dyanmic IP and changed domain names so it made tricker to debug.)

So for anybody having the same problem with a Linksys router, if your firmware version is > 1.37 try downgrading it to 1.37.