I have a linksys WRT54GS.  For most people my websites works.  I have
noticed that several people are unable to reach my website that I host
from my home: http://www.javaclimber.com  but they can access my
remote route configuration http://www.javaclimber.com:8123  They can
also access my DMZ machine http://www.javaclimber.com:8088/

I have never seen anyone who can not ping my javaclimber.com
successfully.  I have a dynamic IP.

I have suspicion that this is a MTU issue.

Why can't some people access my site and what can I do to fix the problem.

I tried changing the webserver MTU to 1200 and that did not seem to help:
ip link set dev eth0 mtu 1200

I have 2 webservers running on different machines running linux.

The first machine is Fedora core 3 and is DMZ.  http://www.javaclimber.com:8088

The second machine is RedHat 8.  WRT54GS port forwards port 80 and
8082 to the RedHat 8 machine.  The webserver is actually running on
port 8082.

In summary:

http://www.javaclimber.com:8123
router web config
seems to work for all

http://www.javaclimber.com:8088
DMZ
seems to work for at least some of those who can't see port 80

http://www.javaclimber.com
Port forwarded from router
Many can not access, but can access 8123 or 8088.


http://www.javaclimber.com:8082
Port forwarded from router
Many can not access, but can access 8123 or 8088.


You can see more details at:
https://answers.google.com/answers/search?q=javaclimber&qtype=all&btnG=Google+Search&catid=1205

---

Clarification of Question by kevinnilson-ga on 10 Mar 2006 10:49 PST

Client gets a 404 for port 80.

---

Clarification of Question by kevinnilson-ga on 11 Mar 2006 13:22 PST

The client get Server not found.  They do not get a 404.

I think you said in your old question/thread, that the machines that
cannot access your website, are not able to access with the domain
name nor with the IP, so this cant be a domain propagation problem.
It seems that the problem is with the packets that the router has to
forward. Maybe you could try to upgrade the firmware to see if it
helps....

You said that everybody can ping www.javaclimber.com. Check you router
configuration and check if you can forward ICMP packets.. in that
case, forward the ICMP packets to one of your servers and try to ping
www.javaclimber.com from a PC that cant access your website. (Just to
check if it's a problem with the port forwarding).

I think the only way to know exactly what's going on, is to capture
the packets and analyze them... but I think it wont be easy to capture
packets on the DSL interface of your router ;)... if you have a
separate dsl modem with ethernet between the modem and the router,
maybe you could connect a PC with 2 NICs, configured as a bridge and
capture packets... but that's not that easy to do I guess ;) ... The
other option (but not as helpful as the former) is to capture packets
at the client's end.. maybe there's something interesting there...
BTW is there any error message on the browser?

Client gets a 404 for port 80.

404? that's weird... The 404 errors are sent by web servers.. in this
case it would mean that the port forwarding is working and that your
web server is sending 404 errors to some clients.. what is really
weird.. Maybe you could check your webserver logs and search for
requests that are replied with 404's...if you find identical requests
from different hosts with different response codes (404, 200 or maybe
others) then the problem is obviously the webserver configuration.

The client get Server not found.  They do not get a 404.