A client computer takes longer than expected to connect to a Web site through an ISA Server 2006 or an ISA Server 2004 Web proxy server

This article has been archived. It is offered "as is" and will no longer be updated.
SYMPTOMS
Consider the following scenario:
  • A client computer tries to connect to a Web site through a Microsoft Internet Security and Acceleration (ISA) Server 2006 or a Microsoft Internet Security and Acceleration (ISA) Server 2004 Web proxy server.
  • ISA Server is configured to request user authentication from client computers.
  • The client computer uses the HTTP 1.0 protocol to send connection requests to ISA Server.
In this scenario, the client computer takes longer than expected to connect to the Web site.
CAUSE
This problem occurs because the client computer does not support connection requests that contain a "Proxy-Connection: Keep-Alive" header. By default, ISA Server keeps the connection alive by assuming that the client computer supports connection requests that contain the "Proxy-Connection: Keep-Alive" header.

If the client computer does not support connection requests that contain a "Proxy-Connection: Keep-Alive" header, ISA Server will close the connection after the connection times out. By default, the time-out is two minutes. Therefore, each connection request will take two extra minutes.
RESOLUTION
To resolve this problem, follow these steps:
  1. Install the latest ISA Server service pack:

    For more information about how to obtain the latest service pack for ISA Server 2006, click the following article number to view the article in the Microsoft Knowledge Base:
    954258 How to obtain the latest Internet Security and Acceleration (ISA) Server 2006 Service Pack
    For more information about how to obtain the latest service pack for ISA Server 2004, click the following article number to view the article in the Microsoft Knowledge Base:
    891024 How to obtain the latest ISA Server 2004 Service Pack
  2. Run the following Microsoft Visual Basic script on the ISA Server computer. To run this script, follow these steps:
    1. Copy the script to a text editor such as Notepad, and then save it by using a file name that has a .vbs file name extension.
    2. Double-click the Visual Basic script file that you created in step 2a to run the script.

    Microsoft provides programming examples for illustration only, without warranty either expressed or implied. This includes, but is not limited to, the implied warranties of merchantability or fitness for a particular purpose. This article assumes that you are familiar with the programming language that is being demonstrated and with the tools that are used to create and to debug procedures. Microsoft support engineers can help explain the functionality of a particular procedure, but they will not modify these examples to provide added functionality or construct procedures to meet your specific requirements.
    '----Script beginConst SE_VPS_GUID = "{143F5698-103B-12D4-FF34-1F34767DEabc}"Const SE_VPS_VALUE = "DontKeepAliveAuthenticatedSession"Sub SetValue()    ' Create the root obect.    Dim root  ' The FPCLib.FPC root object    Set root = CreateObject("FPC.Root")    'Declare the other objects needed.    Dim array       ' An FPCArray object    Dim VendorSets  ' An FPCVendorParametersSets collection    Dim VendorSet   ' An FPCVendorParametersSet object    ' Get references to the array object    ' and the network rules collection.    Set array = root.GetContainingArray    Set VendorSets = array.VendorParametersSets    On Error Resume Next    Set VendorSet = VendorSets.Item( SE_VPS_GUID )    If Err.Number <> 0 Then        Err.Clear        ' Add the item        Set VendorSet = VendorSets.Add( SE_VPS_GUID )        CheckError        WScript.Echo "New VendorSet added... " & VendorSet.Name    Else        WScript.Echo "Existing VendorSet found... value- " &  VendorSet.Value(SE_VPS_VALUE)    End If    if VendorSet.Value(SE_VPS_VALUE) <> true Then        Err.Clear        VendorSet.Value(SE_VPS_VALUE) = true        If Err.Number <> 0 Then            CheckError        Else            VendorSets.Save false, true            CheckError            If Err.Number = 0 Then                WScript.Echo "Done with " & SE_VPS_VALUE & ", saved!"            End If        End If    Else        WScript.Echo "Done with " & SE_VPS_VALUE & ", no change!"    End IfEnd SubSub CheckError()    If Err.Number <> 0 Then        WScript.Echo "An error occurred: 0x" & Hex(Err.Number) & " " & Err.Description        Err.Clear    End IfEnd SubSetValue'----Script end
Properties

Article ID: 921944 - Last Review: 01/16/2015 01:58:09 - Revision: 2.0

  • Microsoft Internet Security and Acceleration Server 2006 Enterprise Edition
  • Microsoft Internet Security and Acceleration Server 2006 Standard Edition
  • Microsoft Internet Security and Acceleration Server 2004 Enterprise Edition
  • Microsoft Internet Security and Acceleration Server 2004 Standard Edition
  • kbnosurvey kbarchive kbtshoot KB921944
Feedback