Where I find OWA and RWW useful is from the outside world in the
oddball case where the cisco vpn client doesn't work and someone has
to use the cisco's web VPN. The web VPN isn't a full VPN, it's
basically a port-forwarding proxy that runs on the remote computer and
can only forward a finite number of ports, and in this case with just
SSL/443 forwarded, using OWA/RWW you can access both email and remote
desktop. I'm just a bit reluctant to open up OWA & RWW completely to
the outside world, having the extra layer of VPN security seems like a
reasonable restriction for things other than outlook RPC/HTTPS email.
I agree, normally, if you can VPN in or are on the local network
OWA and RWW don't make much sense.
I saw the IIS IP-based restriction & thought that might be the
way to go, will give it a shot. Just a quick question - would that
have to be done for all of the websites under Default Website? I'm
noticing quite a few SBS2003 & dell related things there -
ConnectComputer, dell ArrayManager, ClientHelp, & two of our local
intranet-only websites (internal test/staging area for our corporate
web page, and bugzilla)
Many thanks for all the help.
On Sep 3, 4:45 am, "Larry Struckmeyer [SBS-MVP]" <lstruckme...@mis-