Matt Alexander wrote:
> On Wed, 28 Jul 2004, Steve wrote:
>
>
>>This is prolly a stupid question for you brainiacs, but here goes.
>>
>>I have a Redahat machine connected to my cable modem acting as a firewall and router using iptables. In my network behind it I have a WIN2000 Server running IIS5.0 which has 3 vitual websites running on it. I have 3 domain names which all have had the IP address of my static IP address of my cable modem (and the Linux box port forwards to the WIN2000 Server box) config'd with internic. Here's the question,,,,when friends use a browser and hit one of the domains, www.mydominname.com, they get the correct page, however, if I try to hit the same www.mydomainname.com from one of my boxes inside the network, I get "The Page Cannot Be Displayed" with
>>
>>Cannot find server or DNS Error
>>Internet Explorer
>>
>>at the bottom. I believe by setting up a DNS on the Linux box(which I don't currently have) I may be able to resolve this problem, or so that is my suspicion. But I'm wonder why if when my request packet goes out and hits the Name resolution address configured with the Linux box, why it can go out of my internal address for eth1 and hit the resolved addres, which is eth0, which should get port forwarded to the internal address and the response from the IIS go back.
>>
>>I may not be making any sense at this point, but I was wondering if my suspicion is correct, and if anyone could tell me or point me to an explanation?
>>Or, could this be an IIS issue?
>>
>>Total nOOb question to be sure
>
>
> I'm assuming you're using NAT on the firewall and your desktop machine
> is configured to use some external DNS servers? If so, then your
> problem most likely is this... When your browser requests
> www.mydomainname.com, it gets the WAN IP address and tries to connect
> to it. NAT was never designed, unfortunately, to redirect a
> connection back in once it goes out.
> Since you have a small network, the quickest fix would be to modify
> your hosts file on your desktop box and add each of your domains with
> the local IP address of the W2K box.
> If your network grows, then you could setup a DNS server on your
> network to handle your domains on the inside.
> ~M
>
>
> ---------------------------------------------------
> PLUG-discuss mailing list - PLUG-discuss@lists.plug.phoenix.az.us
> To subscribe, unsubscribe, or to change you mail settings:
> http://lists.PLUG.phoenix.az.us/mailman/listinfo/plug-discuss
>
I think I'd try adding a caching DNS server to your firewall box.
Not sure if that would fix your problem or not.
--
-Eric 'shubes'
"There is no such thing as the People;
it is a collectivist myth.
There are only individual citizens
with individual wills
and individual purposes."
-William E. Simon (1927-2000),
Secretary of the Treasury (1974-1977)
"A Time For Truth" (1978), pg. 237
---------------------------------------------------
PLUG-discuss mailing list -
PLUG-discuss@lists.plug.phoenix.az.us
To subscribe, unsubscribe, or to change you mail settings:
http://lists.PLUG.phoenix.az.us/mailman/listinfo/plug-discuss
(text/plain)