Re: Two local IP addresses, cannot see my own webserver!
From: Peter Hucker (hucker_at_clara.co.uk)
Date: 09/05/04
- Next message: Richard Urban: "Re: Downloads and Spyware"
- Previous message: Gian-Pa: "Re: DCOM/RPC problem after WinXP SP2 install"
- In reply to: Lanwench [MVP - Exchange]: "Re: Two local IP addresses, cannot see my own webserver!"
- Next in thread: Ron Lowe: "Re: Two local IP addresses, cannot see my own webserver!"
- Messages sorted by: [ date ] [ thread ]
Date: Sun, 05 Sep 2004 18:02:49 +0100
On Sun, 5 Sep 2004 12:00:34 -0400, Lanwench [MVP - Exchange] <lanwench@heybuddy.donotsendme.unsolicitedmail.atyahoo.com> wrote:
> Peter Hucker wrote:
>> On Sun, 5 Sep 2004 16:17:58 +0100, Ron Lowe
>> <ron-msng@{d.e.l.e.t.e.}lowe-family.me.uk> wrote:
>>
>>> I think this may ba a manifestation of a common issue.
>>>
>>> You may not be able to refer to another machine on your LAN using
>>> it's public IP address because the NAT doesn't do loopback.
>>>
>>> IOW, from within your LAN, the NAT ( sharing ) machine will only be
>>> contactable on the Internal IP ( 192.168.0.2 ) but not on it's
>>> external IP address.
>>>
>>> Normally, you need to use the hosts file internally to point to your
>>> external domain name to the internal IP address.
>>> Leave external DNS for your domain pointing at the external address.
>>>
>>> But then you won't be able to hit the home page at your ISP.
>>>
>>> How would I do it?
>>> Something like this:
>>>
>>> External DNS:
>>> www.yourdomain.com -> IP address of ISP's hosted page.
>>> www1.yourdomain.com -> External IP address of your server.
>>>
>>> In the home page, don't refer to the IP address of the home-hosted
>>> page, but refer to www1.yourdomain.com.
>>>
>>> Internally:
>>> Add this to your hosts file:
>>>
>>> 192.168.0.2 www1.yourdomain.com
>>>
>>> Now, name resolution for the www1 machine should resolve to the
>>> external IP address for everyone on the outside, but to 192.168.0.2
>>> for you on the inside.
>>>
>>> You still get the external IP address for the ISP-hosted page,
>>> becuase we didn't over-ride DNS with hosts for the www. homepage.
>>
>> But there is no domain for my external IP. Why can't I put:
>>
>> 127.0.0.1 80.229.155.158
>>
>> in the hosts file?
>
> Because that isn't what hosts does. It maps hostnames to IPs, doesn't
> redirect one IP address to another.
>
> I strongly suggest you buy a little gateway/router/firewall appliance, put
> it between your DSL modem and your network, and disable ICS. It works a lot
> better in general. Keep everyone on the same local (private) IP subnet. Use
> a static IP for your server, and DHCP if you like for your workstations.
>
> Windows makes a lousy router, if you ask me -and ICS is dreadful stuff.
It is sharing just fine. And I have an awful phone line - it's very difficult to get an ADSL modem/router to work on it - the one that works happenes to be USB.
Anyway even if I used a router (which I used to), I still have the same problem with a different IP being used for my server from here, than from externally.
-- *****TWO BABY CONURES***** 16 parrots and increasing http://www.petersparrots.com 93 silly video clips http://www.insanevideoclips.com 1259 digital photos http://www.petersphotos.com Served from a pentawatercooled dual silent Athlon 2.8 with terabyte raid Lysdexia: a peech imspediment we live to learn with...
- Next message: Richard Urban: "Re: Downloads and Spyware"
- Previous message: Gian-Pa: "Re: DCOM/RPC problem after WinXP SP2 install"
- In reply to: Lanwench [MVP - Exchange]: "Re: Two local IP addresses, cannot see my own webserver!"
- Next in thread: Ron Lowe: "Re: Two local IP addresses, cannot see my own webserver!"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
