Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

External clients cannot access the published server when you use a server publishing rule in ISA Server 2006 to publish one or more services


View products that this article applies to.

Symptoms

Consider the following scenario:
  • You use a server publishing rule in Microsoft Internet Security and Acceleration (ISA) Server 2006 to publish one or more services.
  • There is a network address translation (NAT) relationship between the network of the published server that is behind ISA Server and the client-side network that accesses the server.
  • The network interface that is used for the Server Publishing listener is also used for site-to-site VPN connections.
In this scenario, external clients cannot access the published server. The incoming packets are displayed as "denied" by the default deny policy in ISA Server.

↑ Back to the top


Cause

When you create the listener that is used for the server publishing rule, ISA Server may incorrectly initialize the listener as a route listener instead of as an NAT listener.

↑ Back to the top


Resolution

To resolve this problem, follow these steps.

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. However, they will not modify these examples to provide added functionality or construct procedures to meet your specific requirements.
  1. Apply the hotfix package that is described in the following Microsoft Knowledge Base article:
    955151 Description of the ISA Server 2006 hotfix package: July 06, 2008
  2. Copy and then paste the following code into Notepad.
    Const SE_VPS_GUID = "{143F5698-103B-12D4-FF34-1F34767DEabc}"
    Const SE_VPS_NAME = "EnableHotfix955110"
    Const SE_VPS_VALUE = true
    
    Sub SetValue()
    
        ' Create the root object.
        Dim root  ' The FPCLib.FPC root object
        Set root = CreateObject("FPC.Root")
    
        'Declare the other objects that are needed.
        Dim array       ' An FPCArray object
        Dim VendorSets  ' An FPCVendorParametersSets collection
        Dim VendorSet   ' An FPCVendorParametersSet object
    
        ' Get references to the array object
        ' and to 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_NAME)
        End If
    
        if VendorSet.Value(SE_VPS_NAME) <> SE_VPS_VALUE Then
    
            Err.Clear
            VendorSet.Value(SE_VPS_NAME) = SE_VPS_VALUE
    
            If Err.Number <> 0 Then
                CheckError
            Else
                VendorSets.Save false, true
                CheckError
    
                If Err.Number = 0 Then
                    WScript.Echo "Done with " & SE_VPS_NAME & ", saved!"
                End If
            End If
        Else
            WScript.Echo "Done with " & SE_VPS_NAME & ", no change!"
        End If
    
    End Sub
    
    Sub CheckError()
    
        If Err.Number <> 0 Then
            WScript.Echo "An error occurred: 0x" & Hex(Err.Number) & " " & Err.Description
            Err.Clear
        End If
    
    End Sub
    
    SetValue
    
  3. Save the file as a Microsoft Visual Basic script file by using the .vbs file name extension. For example, use the following name to save the file:
    Enable_955110.vbs
  4. At a command prompt, change the location to the one in which you saved the Enable_955110.vbs file, and then run the following command:
    cscript Enable_955110.vbs
    Notes
    • Enable_955110.vbs is a placeholder for the file name.
    • To revert to the default setting, change Const SE_VPS_VALUE = true to Const SE_VPS_VALUE = false in the code that is mentioned in step 2, and then run the script again.

↑ Back to the top


Status

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

↑ Back to the top


Keywords: KB955110, kbqfe, kbexpertiseadvanced

↑ Back to the top

Article Info
Article ID : 955110
Revision : 2
Created on : 9/11/2008
Published on : 9/11/2008
Exists online : False
Views : 339