Hi

I've got a domain name pointed back to one of my machines at home, if I use a pc externally to view the domain it works fine.  Problem I 've got is if I type the domain name from a pc on the network, it goes to the router's configuration page, any ideas why its doing this?

Any pointers grateully received.  
 

It depends on the router, but I can make an educated guess.

OUTBOUND, "all" your systems go through the one router and have their addresses mapped down to a single address as far as your service provider is concerned.    For example, I'm writing from 192.168.200.77 internally, and Lisa's working from 192.168.200.189.  The machine in the library is at 192.168.200.103.   However, as far as the internet as a whole is concered all three of them are at 82.33.81.221.

So INBOUND connections are all to 82.33.81.221 (my router) and will be handled by that unless I have it configured otherwise.   The two things to look at in making changes here are the DMZ (demilitarized zone) which cuts firewalling from a local host, and the setting that may be labelled "virtual servers" to allow you to forward all inbound requests to your IP on a particular port to that server.


Thanks for your response.  Guess is right  

all internal machines run through 191.169.1.2 up to 5 if memory serves me right, but as far as incoming, only the 1 IP address assigned by the ISP is seen.

I've set up the virtual server, and I've tested it over dad's house by entering the domain name, and it works fine, goes straight through the router to the local machine running apache and the pages can be seen.

But if I try to enter the domain name from a machine on the home network, it only shows the router configuration page.  I've also (in the router config) put the local machine running apache in the dmz zone, but no difference.

The domain is pointed at my IP address by an external company, so the requests must be going out to the internet then back in, but I don't understand why internal machines only get the router config page



If it's a similar router to ours, then the DMZ / NATS forwarding configuration is for connections coming from outside.  And for a connection from an internal source, it doesn't apply, even if an external enquiry had to be made to resolve the DNS address back to you.

From a testing viewpoint, this behaviour is somewhat irritating, even if it is understandable when you give it some deep thought.

Yep, configuration must be similar.  Got around the problem by typing the local ip address directly, but it is a bit of a pain if you want to check its working from outside the network, nevermind.

Thanks again.

Chris.

---