![]() |
|
SPONSORED LINKS BY GOOGLE |
|
5
19th March 09:21
External User
Posts: 1
|
Is the ADSL modem also a NAT/firewall thingy? What are your two PCs'
addresses? Is there port forwarding (or whatever it's called) set-up on the NAT to forward HTTP traffic to the Linux box? What address appears in the DNS for your domain name? If you are using a NAT then your address will be something like: XP box 192.168.100.10, Linux box 192.168.100.11, NAT/firewall box: inside 192.168.100.1, outside 192.0.2.159 And when you do a DNS lookup for your domain name you'll get back 192.0.2.159. So when you try to connect to your webserver you'll get the outside address and not the inside address. And apparently your NAT box does not forward the packets back inwards. Try loading http://192.168.100.11, using whatever the Linux box's real address is. Traceroute (tracert.exe) might be useful to see where packets to the various addresses are going... This is another of the problems with NAT. One has to have two DNSs (sometimes called split DNS), one for use inside the NAT-ed network and another internet accessable one for outside. One simpler way to do this for you, is to put a corresponding entry in the "hosts" files on your box which will be used instead of doing the DNS lookup. My guess, as above, is that addressing alone is the issue. Once you can communicate using any protocol (e.g. ICMP Ping) all others will work too. -- Alan J. McFarlane http://homepage.ntlworld.com/alanjmcf/ Please follow-up in the newsgroup for the benefit of all. |
|
|
SPONSORED LINKS BY GOOGLE |
|
|