I need to bypass my ISA 2004 proxy server for a particular website. I have configured the direct access on the ISA server and all is well when I have the installed firewall client disabled. As soon as I enable the firewall client, the direct access stops working.
I found this article describing the issue with ISA 2004 SP2 and I have made the changes, but it still doesn't work.
What else can I do to force my clients to bypass the ISA server for a particular address?
Funny. I fought this tonight as well. I have a branch office that I was trying to get the PCs there which were loaded with the FWC to access an internal SSL website located at another office. With the FWC, it was not working, their local ISA server would NOT redirect them properly. Removing the FWC and relying soley on the IE Web Proxy worked. That wasn't a solution so I did some checking... On my ISA server, I found that for whatever reason entering in
under the Web Browser tab did NOT allow the PCs with the FWC to be properly redirected to the other branch location. However.... entering in
under the Web Browser tab DID allow the PCs with the FWC to be properly redirected to the other branch location ONCE the FWC received an updated wpad.dat file from the server (I forced this after each change during my testing by deleting the wpad.dat file, and starting IE wihch downloaded the updated wpad.dat).
I am running SP3 on both my ISA boxes.
WHY in the world would *.domain.com/* work, while, name.domain.com/* and name2.domain.com/* would NOT work?!