Can't access server from LAN but WAN side works

I've RTFM and STFW but can't find a solution.

I've got several XP PCs and a Linux Apache server on the LAN side of an
Actiontec GT701 DSL modem/router.

When I enter the server domain name on the LAN side the PCs get the
main DSL modem/router page, while PCs on the WAN side get the correct
index.html server page.

I'm forwarding port 80 in the router to the server IP.

I think it's a common problem with a simple solution just can't figure
out what it is.

How to I get the router to forward local requests as well as external
requests to the server?

Do I need to setup a route for the server on each local PC?

Thanks for any assistance!

Arn wrote:

> When I enter the server domain name on the LAN side the PCs get the
> main DSL modem/router page, while PCs on the WAN side get the correct
> index.html server page.

I've had a problem that sounds similar. I assume that your, presumably on
the lan side, server is telling the outside world its server name
ServerName in httpd.conf. That's great for the outside world.
Unfortunately it is also telling your machines on your LAN this name and it
seems (to me at least with my router) that the browsers on the LAN then go
and look for subsequent pages at the ServerName given to them, which is a
network interface on the router, not your server. My router reacts by
displaying its pages. It does not portforward to where your server is on
the lan.

My solution was to spoof the DNS, assume that from the wan side your server
looks to be at www.foo.bar. If your server, on the LAN side is at
192.168.1.10 set www.foo.bar to be at 192.168.1.10 in your hosts file on
your various LAN machines.

Pete



--
http://www.petezilla.co.uk

Thanks!

I thought it might be something like that, but wanted to check with
others that had solved the problem.

Looks to be a rather clean solution; I don't need to mess with the
router or setup weird DNS records.

I'll give it a try tomorrow.