I have started playing around with linux and apache and tried setting up a network. I have one computer running apache 2.0 server with a free domain name on a mandrake linux 9 and a phoneline 2wire gateway. However my other computer on the network cant see this site when i type in external domain name but can see it when i put in the internal ip 192.168.0.33. How do i make all computer realise that the url i type is actually hosted by this other computer. Can you give me the solution and also a brief explanation/ theory.
Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations Westi on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
computer cant see the domain hosted by server on the network
- Thread starter kaio123
- Start date
sleipnir214
Programmer
The problem is you are in a non-routable network and internet access is being provided by NAT.
When a machine on your browser attempts to go to your server, it gets an internet address, so instead of talking directly to the server on its own network, it sends the packets to the default gateway. Unless that default gateway (or some other router) has been specifically instructed otherwise, it will not send a packet back out through the interface from which the packet came (which it would have to do to get the packet back to the server) because not doing so prevents network looping.
One workaround is to put an entry into your workstation's hosts file which specifically states that has the non-routable address actually configured on the web server. Under normal network configuration, entries in the hosts file supercede DNS lookup, so your workstation's browser will resolve as a local address and fetch content from the server on the local network. Want the best answers? Ask the best questions: TANSTAAFL!
When a machine on your browser attempts to go to your server, it gets an internet address, so instead of talking directly to the server on its own network, it sends the packets to the default gateway. Unless that default gateway (or some other router) has been specifically instructed otherwise, it will not send a packet back out through the interface from which the packet came (which it would have to do to get the packet back to the server) because not doing so prevents network looping.
One workaround is to put an entry into your workstation's hosts file which specifically states that has the non-routable address actually configured on the web server. Under normal network configuration, entries in the hosts file supercede DNS lookup, so your workstation's browser will resolve as a local address and fetch content from the server on the local network. Want the best answers? Ask the best questions: TANSTAAFL!
- Thread starter
- #3
I did try that soln without success. Here's what my hosts file looks like but i still couldnt view the site internally.Also my gateway does NAT and knows tht one computer acts as server.
127.0.0.1 localhost.localdomain localhost
192.168.0.33 kaio.sytes.net
12.249.31.165 kaio.sytes.net
127.0.0.1 localhost.localdomain localhost
192.168.0.33 kaio.sytes.net
12.249.31.165 kaio.sytes.net
- Status