Context: When we deployed the firewall client, the ISA server Internal Network Domains tab included all our internal domains, and within the Internal Network Web Browser tab we've accounted for our Internal Domains and Internal Addressing as well as additional domains and addresses that are supplied in the routing script so that we furnish a comprehensive "bypass ISA Server list" to our web proxy clients utilizing the routing script. However we're running into a deficiency in how Internet Explorer is being configured by the firewall client (via the firewall client web browser settings | Enable web browser automatic configuration), where the browser is not being supplied any "exceptions" for the Proxy Server "bypass proxy server for local addresses" area.
Problem: Web proxy clients that inherit the Proxy Server settings (from Internet Explorer) do not inherit a "bypass list" and send all requests to ISA, even the requests for local (domain or addresses) resources. Is there a way to resolve this with ISA 2004 or ISA 2006?
In other words: Is there a way for ISA Server or the firewall client to supply a bypass proxy server for local addresses list within Internet Explorerís Proxy Server settings?
< Message edited by abqtech -- 15.Oct.2007 12:22:33 PM >
Tarek, You're correct I don't see the bypass list supplied in IE. And web requests that make us of the proxy server are all directed to the proxy server, even for local sites and extranet sites. The desire is to have a bypass list provided to IE's proxy server setting.
Hi hmilito We have a Group Policy that specified the necessary bypass list & proxy server, however the firewall client settings override what's being set by Group Policy.
The only thing I can think of that will resolve this problem is to Use a Group Policy that, sets the browser settings (use automatic configuration script & Proxy Server including bypass list) and then configure the firewall client so that it does not enable web browser automatic configuration.
Tarek, Thanks for you reply and I have re-read that MS Article, however the issue that I'm trying to address, does not apply to that article, because the web proxy clients that are impacted by this are not WPAD or Routing.Script clients. They are IE clients that have the Use Proxy Server for you LAN configured to point to ISA. And some HTTP (web) requests generated by the client (could be an ActiveX, Java or Multimedia Plugin) are utilizing the ISA Server specified in Use Proxy Server for you LAN. And when Use Proxy Server for you LAN is configured via the MS Firewall Client no bypass proxy server for local addresses is supplied.