I notice that when my Web Proxy clients authenticate with the ISA Server using integrated authentication, that NTLM is used, and not Kerberos. I want to use Kerberos. How to I configure the Web Proxy clients to use Kerberos to authenticate with the Web Proxy service?
You can't use Kerberos to authenticate a Web Proxy client with the Web Proxy service. Internet Explorer doesn't support it. IE does not support Kerberos authentication and Microsoft says this is by design. Check out the details at http://support.microsoft.com/search/preview.aspx?scid=kb;en-us;Q321728 [This FAQ contributed by Tom Shinder]
Why do I see anonymous requests in the Web Proxy log? I'm forcing authentication and I don't have anonymous access rules.
This FAQ is by Thomas W Shinder: The reason for this is that all initial requests made by Web Proxy clients are sent anonymously. The ISA Server will send by a access denied message and a request for credentials. The Web Proxy client then sends the appropriate credentials or asks you to provide them, depending on the type of authentication you're using on the listener. Then the request is allowed or denied based on the sent credentials. No, you cannot eliminate these requests from the log -- that would violate ISA Server's policy of logging everything.
How does caching impact bandwidth requirements and information availability?
Caching reduces bandwidth requirements by moving Web content closer to the user. By caching frequently requested content, bandwidth usage can be decreased by as much as 40 percent. Caching also can provide content to users even when the source for the content is off-line or unavailable.
What is reverse caching and does ISA Server support it?
Reverse caching is another term for placing a cache in front of a Web server or e-commerce application. This is called "reverse" because it is implemented by the administrators of the Web servers, rather than by the clients, to cache or distribute content from the servers or to offload processing. ISA Server supports reverse caching, allowing Web managers to cache and distribute content, thereby improving user response time.
What are cache size recommendations for ISA Server 2000 (corporate and ISP setups)?
The processor load increases with more Ruled/ restrictions. So if you are planning to leave it open access, more RAM would be the way to go. You may want to use perform to determine bottlenecks. For small loads anything over 250MB will be good. For large loads, say > 1000 clients, 1GB will be more like it. You could also use the Proxy 2 algorithm of 100MB + .5mb per client of cache file.
Web page requests intermittently return 404 errors, doing a refresh serves up the page properly, is there a fix to this?
This problem is with both Beta 3 and RC1, currently, there is no fix.
When i installed ISA RC1 in cache mode i couldn't get my web pages and then i installed it in integrated mode and everything worked fine and i didn't any of my configuration! Why would this be so?