Greetings:
I'm troubleshooting an issue for a customer. We operate a web site that uses only secure pages and content. The application sends email to users when they have a task to complete. The link directs them to a secure page. Users behind a MS ISA 2000 server running in Proxy mode in a pure NT4.0 NTLM authentication environment experience 25-70 second load times for the page while users outside the ISA's sphere of influence see 5-12 second load times.
I've considered suggesting that they use SOCKS5 to obfuscate the whole proxy issue but I know they won't want to play that way. So, looking for ways to set particular URL's to bypass the proxy, or similar ways to tune the problem away.
We've determined that the server they're running ISA on is more than sufficient performance wise to handle the load, in case you were wondering.
I'm troubleshooting an issue for a customer. We operate a web site that uses only secure pages and content. The application sends email to users when they have a task to complete. The link directs them to a secure page. Users behind a MS ISA 2000 server running in Proxy mode in a pure NT4.0 NTLM authentication environment experience 25-70 second load times for the page while users outside the ISA's sphere of influence see 5-12 second load times.
I've considered suggesting that they use SOCKS5 to obfuscate the whole proxy issue but I know they won't want to play that way. So, looking for ways to set particular URL's to bypass the proxy, or similar ways to tune the problem away.
We've determined that the server they're running ISA on is more than sufficient performance wise to handle the load, in case you were wondering.