[isalist] Web Proxy client vs. Firewall client for web access
- From: Danny <nocmonkey@xxxxxxxxx>
- To: isalist@xxxxxxxxxxxxx
- Date: Wed, 23 Aug 2006 15:13:59 -0400
Server: SBS 2003 SP1 + ISA 2004
Policy: Allow All Outbound Protocols from Internal to External. Users: SBS
Internet Users (Yes, not our standard, but is for SBS 2003)
Client: Windows XP Pro SP2 + ISA Firewall Client
Issue: User unable to fully utilize (upload, edit, save) a web-based CMS
(Content Management System) that relies on an ActiveX add-in and Java
applet.
Scenario #1:
Web Proxy Enabled
Firewall Client Enabled
Symptoms: Uploading, editing, saving does not work. Just timesout. Anonymous
denies are recorded in the ISA logs.
Scenario #2:
Web Proxy Disabled
Firewall Client Enabled
Symptoms: Everything works.
Scenario #3:
Web Proxy Disabled
Firewall Client Disabled
Symptoms: Duh, no web access!
I understand why each scenario produced the results I experienced, but what
I am curious about is what the long term cons/side effects/issues with
leaving the computer configured with only the Firewall Client enabled; Web
Proxy disabled a.k.a Scenario #2.
Thanks,
...D
--
CPDE - Certified Petroleum Distribution Engineer
CCBC - Certified Canadian Beer Consumer
Other related posts:
- » [isalist] Web Proxy client vs. Firewall client for web access
