ISA questions

Hi,
I have 2 questions concerning ISA.

1) I set up the SSL for OWA directions as posted on the
sbs2000.info site. We also publish a different website
located on a seperate server via site publishing rules.
That being said I can't close port 80 on ISA. Is there
anything else I can do to block port 80 traffic on the SBS
machine?

2) Is it true that, Site and Content along with Protocol
rules only control how INTERNAL clients access the
internet. Opening these rules up (i.e. all IP
traffic/applies to any request) do not expose our network
to external born attacks.

Chad
Wed Aug 20 13:39:49 CDT 2003

Hi nic - see inline.

--

Chad A. Gross

Lerman's Law of Technology: Any technical problem can be overcome
given enough time and money. Corollary: You are never given enough
time or money.


In news:009f01c36732$1d31e220$a301280a@phx.gbl,
nic <nic@noway.com> posted:
> Hi,
> I have 2 questions concerning ISA.
>
> 1) I set up the SSL for OWA directions as posted on the
> sbs2000.info site. We also publish a different website
> located on a seperate server via site publishing rules.
> That being said I can't close port 80 on ISA. Is there
> anything else I can do to block port 80 traffic on the SBS
> machine?

Is your webserver joined to your domain? If so, does it have to be? If it
were me, I'd put a router between the 2nd nic on your SBS & internet
connection, and attach both your webserver & WAN side of your SBS to the
router. Have the router forward port 80 to the webserver and forward port
443 (and any others necessary) to your SBS. This way you can close port 80
in ISA . . .

>
> 2) Is it true that, Site and Content along with Protocol
> rules only control how INTERNAL clients access the
> internet. Opening these rules up (i.e. all IP
> traffic/applies to any request) do not expose our network
> to external born attacks.

Correct. Inbound packet filters control what external traffic your server
is accepting. Site & Content rules control outbound access - not inbound.