Re: ISA 2004 Network Config

Tech-Archive recommends: Speed Up your PC by fixing your registry

From: Phillip Windell (_at_.)
Date: 11/30/04 

Date: Tue, 30 Nov 2004 10:28:45 -0600

Use private IP#s behind the ISA. Keep you extra public IP#s for something
more useful and only use additional ones on the external nic of the ISA when
there is no other convenient way. The most dependable and manageable ISA
config is one private IP# and one public IP#. Use additional ones sparingly. 

-- 
Phillip Windell [MCP, MVP, CCNA]
www.wandtv.com
"- Steve -" <sevans@foundation.sdsu.edu> wrote in message
news:%23y0WrMv1EHA.2824@TK2MSFTNGP09.phx.gbl...
> I'm getting ready to implment ISA 2004 to protect our Exchange
> infrastructure.
>
> One thing I'm confused about and can't find the information I need is how
to
> assign IP address.  I'm at a University so all of our machines have public
> address.
>
> Should I give the machines behind the ISA firewall private address and
> reassign the current public address to the ISA firewall and publish out
all
> the servers.
>
> or
>
> Should I just have the ISA firewall route between one network to another
and
> the ISA firewall only has one address.
>
> It seems like the first one is the way it should/has to be done.  Since
when
> I say publish OWA external clients should point to an address on the ISA
> firewall now.
>
>

Relevant Pages