From: Amazon, Brazil
is your rule configured to allow only authenticated users? Maybe thats the "problem", because some websites, like bank sites, donīt work well when the proxy server is configured to ask for authentication. These type of applications are being processed by the webproxy but are not passing all the info webproxy expects from an IE or other compliant web browser.
It explains why works when you remove the proxy setting from the browser and access the website as secureNAT (assuming the ISA is the default gateway).
The 1.1 is allowed through proxy connections, looking at the ISA server.
The HTTP Proxy Connection keeps initiating and closing.
The log shows: Open HTTP Proxy at 172.20.0.103:1282 Http traffic allowed Close HTTP Proxy Http Denied traffic (the timeout i suspect) Open HTTP Proxy at 172.20.0.103:1283 and so on.
There seems to be gaps in the proxy connection where http traffic is denied. ISA BPA is fine, the hotfix is being downloaded now.
As far as forced authentication, it is not set in the network section to connect to proxy, it is set in the rule allowing http out (authenticated users only).
Have an AD domain with proxy set as a domain policy, so all: Internet Explorer - connection to proxy set, login information sent Safari - connection to proxy is IE's so set, login is requested Firefox - Ignores group policy, manually set to use proxy, login is requested.
All three do authenticate though.
< Message edited by CSDAdmin -- 9.Jun.2008 10:10:36 AM >