RE: ISA Server 2004 Standard Edition SP1
- From: "Ball, Dan" <DBall@xxxxxxxxxxx>
- To: "[ISAserver.org Discussion List]" <isalist@xxxxxxxxxxxxx>
- Date: Wed, 2 Mar 2005 15:29:19 -0500
Nope, didn't miss that. The whole thread evolved due to a question that
if you specify a server on the command-line while installing, is that
not the same as configuring the FWC statically?
I "don't want" it to be set statically, I "want" the FWC to autodetect,
and self-disable if necessary.
So, why does it self-disable for Tom if he statically configures a
server?
I understand what you're saying, but Tom says his experience tells a
different story.
I guess it's a moot point, I have mine setup for automatic detection, so
it won't affect me. Just curiosity I guess.
-----Original Message-----
From: Jim Harrison [mailto:Jim@xxxxxxxxxxxx]
Sent: Wednesday, March 02, 2005 15:18
To: [ISAserver.org Discussion List]
Subject: [isalist] RE: ISA Server 2004 Standard Edition SP1
http://www.ISAserver.org
Hi Dan,
Did you miss the "it depends" part?
If you configure the FWC statically, it will block.
If you have it configured "automatically", it will self-disable.
The same is true for IE - auto-detection is the on ly way you can
reliably move between ISA- and non-ISA-served networks.
Other related posts:
