accessing my webserver from behind the router

[ArmchairAthlete]

So my roommate with a nice Linksys router left. Now I'm left with two dumb old routers that seem to have the same problem with my webserver.

They'll forward WAN http port 80 requests to the webserver just fine. But LAN requests from behind the router for the WAN IP (resolved /w DNS or otherwise) result in bringing up the LAN config page. If it's for a resource on my site, the router won't be able to find it of course. The previous router was smart enough to send these requests to my webserver.

Port 80 is set up to go to my webserver... there really aren't many options to configure on the Netgear RP114 or the Dlink DI-604 that's the other option now unless I buy something.

Do I just need to buy a router that doesn't suck?

 

[RebateMonger]

Many SOHO routers can't access an external port from inside your LAN. They are "smart" and know that the internal router address is the "same" as the external router IP, so they go to the internal IP. I don't know of any router fix but trying a different router.

Internally, just browse directly to your web host, rather than trying to access it via the Internet.

 

[ArmchairAthlete]

Yea... my webserver is also my desktop so of course loopback works.

Problem is, things on my site like stylesheets are set up to use the DNS name. The site also publishes feeds that it in turn consumes to generate a little box for each one I configure, so I've had to fix those too to use loopback but publish their link with the actual URL for internet users.

 

[RebateMonger]

You could use a HOSTS file on the accessing PC, that sends it to the internal IP address instead of the external (public DNS) address.

 

[ArmchairAthlete]

Ah thanks! I should've thought of that earlier considering I've done it before at work. That is the easiest solution.