[isalist] Re: [Book/2004] Quick followup question about FWC & Proxy

  • From: "Jim Harrison" <Jim@xxxxxxxxxxxx>
  • To: <isalist@xxxxxxxxxxxxx>
  • Date: Mon, 3 Jul 2006 16:23:04 -0700

http://www.ISAserver.org
-------------------------------------------------------

No - and this is easily the hardest part of ISA client troubleshooting.

With the exception of the FWC, there are no "ISA clients" as such - it's just 
easier to think in terms "the machine' than 
"every stinkin' connection or request possibly made by any thread of any 
process that thinks it needs to resolve names, connect to remote hosts or 
simply spew packets via Winsock, TCP/IP or other means.", which is really how 
it works.

As such, there is no "always" or "never" with regard to "client type 
performance", as each request type has its own set of dependencies.

..but to answer your question; you should use either "automatically detect.." 
or, if you have no wpad support in your network, "configuration URL" in the 
browser settings.  This way, the "local vs. remote" configuration is obtained 
from the master of all knowings; ISA.

-------------------------------------------------------
   Jim Harrison
   MCP(NT4, W2K), A+, Network+, PCG
   http://isaserver.org/Jim_Harrison/
   http://isatools.org
   Read the help / books / articles!
-------------------------------------------------------
 

-----Original Message-----
From: isalist-bounce@xxxxxxxxxxxxx [mailto:isalist-bounce@xxxxxxxxxxxxx] On 
Behalf Of Jonathon J. Howey
Sent: Monday, July 03, 2006 15:34
To: isalist@xxxxxxxxxxxxx
Subject: [isalist] [Book/2004] Quick followup question about FWC & Proxy

Just started resuming reading the book, and I came across this paragraph in 
Configuring ISA 2004, page 442 / 443:
 
-The picture shows the 'Use a web proxy server" checkbox is checked -Paragraph 
states: "The Use a Web Proxy server option allows you to configure the Web 
browser to use the ISA 2004 as its Web Proxy, but without the benefits of the 
autoconfig. script information. This setting provides higher performance than 
the SecureNAT (now SecureNET i suppose) client configuration but you do not 
benefit from the settings contained in the autoconfig. script.  The most 
important configuration settings in the autoconfig. script includes site names 
and addresses that should be used for Direct Access. For this reason, you 
should avoid this option unless you do not wish to use Direct Access to bypass 
the Web Proxy service to access selected Web Sites."
 
So this means that if the checkbox is checked, the Direct Access list will be 
ignored in an environment where all three client types are used? Furthermore, 
if the client's browser for example has a proxy filled in, will this FWC client 
setting step in, or does the proxy itself still have high precidence?  When 
will i see this setting start to affects Direct Access in a three-client 
enviroment if the proxy always handles Web Traffic (according to p.415).
 
 
Thanks,
 
PS: Where do you talk about the IP Routing setting again in the book? I can't 
find it in the index, and it's starting to bug me as i read about it, but i 
can't find the page it's on... I thought it was Chapter 6 or prior, but i must 
be skimming over it. Cheers.
Jonathon J. Howey
MENSE Inc.
P 780.409.5620
F 780.409.5621
D 780.409.5628
C 780.965.8363
Jonathon@xxxxxxxx <mailto:Jonathon@xxxxxxxx> 
 
Defining the Future of Transportation
www.MENSE.ca <http://www.MENSE.ca/> 

All mail to and from this domain is GFI-scanned.

------------------------------------------------------
List Archives: //www.freelists.org/archives/isalist/
ISA Server Newsletter: http://www.isaserver.org/pages/newsletter.asp
ISA Server Articles and Tutorials: http://www.isaserver.org/articles_tutorials/
ISA Server Blogs: http://blogs.isaserver.org/
------------------------------------------------------
Visit TechGenix.com for more information about our other sites:
http://www.techgenix.com
------------------------------------------------------
To unsubscribe visit http://www.isaserver.org/pages/isalist.asp
Report abuse to listadmin@xxxxxxxxxxxxx

Other related posts: