Firewall client tool for isa server 2004

Symptoms If the Microsoft Internet Security and Acceleration (ISA) Server 2004 Firewall Client program is configured for auto-discovery, you may experience the following symptoms: If Microsoft Internet Explorer is not configured to use a proxy or to detect a proxy, you cannot access a Web pages when you use Internet Explorer. Additionally, you receive the following error message: Cannot find server or DNS Error A red "X" appears over the Firewall Client icon. You can find the Firewall Client icon in the notification area at the far right of the taskbar. If you pause the mouse pointer on the Firewall Client icon, you receive the following error message: Disabled: Cannot authenticate to ISA Server server_name If you try to configure the ISA Server 2004 Firewall Client program for auto-discovery, you may experience the following symptoms: If you try to configure the Firewall Client program to use auto-discovery by clicking Detect Now under Automatically detect ISA Server on the General tab, you receive the following error message: Failed to detect ISA Server A red "X" appears over the Firewall Client icon. You can find the Firewall Client icon in the notification area at the far right of the taskbar. If you pause the mouse pointer on the Firewall Client icon, you receive the following error message: Disabled: ISA Server could not be detected Cause This issue occurs if the IFPCEEWebProxy.SkipAuthenticationForRoutingInformation property is set to FALSE in ISA Server 2004. This problem occurs when the following conditions are true: The Firewall Client program is configured to use auto-discovery. The Require all users to authenticate Web Proxy setting is configured for the internal network object on the ISA Server 2004 computer.Note The Require all users to authenticate setting is available when you click Authentication on the Web Proxy tab when you view the properties of the internal network object. These conditions cause this problem because the Firewall Client program cannot perform HTTP authentication. When the Require all users to authenticate setting is enabled for the internal network object, the request to the Winsock Proxy Autodetect (WSPAD) port must be authenticated also. However, the Firewall Client program does not handle the "401 Authentication Required" response. Therefore, when the Firewall Client program tries to retrieve the Wspad.dat file from the Web Proxy Automatic Discovery (WPAD) server during the auto-discovery process, the auto-discovery process fails. Resolution To resolve this issue, set the IFPCEEWebProxy.SkipAuthenticationForRoutingInformation property to TRUE. To do this, follow the instructions in this section. ISA Server 2004, Standard Edition Service pack information To resolve this problem, obtain the latest service pack for ISA Server 2004. For more information, 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 Installation information Important This section, method, or task contains steps that tell you how to modify the registry. However, serious problems might occur if you modify the registry incorrectly. Therefore, make sure that you follow these steps carefully. For added protection, back

This article describes how to install the Microsoft Internet Security and Acceleration (ISA) Server 2004 Microsoft Firewall Client program on client computers by using a command-line or by using Group Policy.Modify the Microsoft Firewall Client installation shareBy default, when you install ISA Server 2004 the Firewall Client program installation files are stored in the following folder location: C:\Program Files\Microsoft ISA Server\clients Note In Microsoft Forefront Threat Management Gateway, Medium Business Edition, the Firewall Client program installation files are stored in the Microsoft Forefront Threat Management Gateway, Medium Business Edition installation CD.In some scenarios, you may want the Firewall Client program installation files to be located on another computer. To do so, you must perform a custom ISA Server installation. To perform a custom ISA Server installation, follow these steps. Note You cannot customize the Microsoft Forefront Threat Management Gateway, Medium Business Edition installation to modify the Microsoft Firewall Client installation share. However, you can copy the Firewall Client program installation files from Microsoft Forefront Threat Management Gateway, Medium Business Edition installation CD to another computer. Then, you can distribute the Firewall Client from that computer.On the computer where you want to store the Firewall Client program installation files, start ISA Server 2004 Setup.In the Microsoft ISA Server 2004 Installation Wizard, click Next.Click I accept the terms in the license agreement, and then click Next.Type your user name and organization in the corresponding boxes, type your product serial number in the Product Serial Number box if applicable, and then click Next.Click Custom, and then click Next.Click Firewall Services, click This feature will not be available, click ISA Server Management, click This feature will not be available, click Firewall Client Installation Share, click This feature will be installed on local hard drive, and then click Next.Click Install, and then click Finish when

Auto discovery" section.Configure auto discoveryTo configure the Firewall Client program to automatically detect the ISA Server computer or the Microsoft Forefront Threat Management Gateway, Medium Business Edition Server computer, you must configure Firewall client and Web Proxy client auto discovery in Windows. For additional information about how to configure Firewall Client and Web Proxy client auto discovery in Windows, click the following article numbers to view the articles in the Microsoft Knowledge Base: 309814� How to configure Firewall and Web Proxy client autodiscovery in Windows 2000252898� How to enable Proxy Autodiscovery in Windows 2000 296591� A description of the Automatic Discovery featureAdditionally, you must configure ISA Server 2004 or Microsoft Forefront Threat Management Gateway, Medium Business Edition to provide automatic discovery information to Firewall clients and to Web Proxy clients. To do this, follow these steps: Start the ISA Server Management tool.Expand ServerName, where ServerName is the name of your ISA Server computer.For ISA 2004 or for ISA 2006, expand Configuration, and then click Networks. For Microsoft Forefront Threat Management Gateway, Medium Business Edition, click Networking, and then click Networks in the middle pane.Right-click the network that you want ISA Server to publish auto discovery information about, and then click Properties. For example, right-click Internal, and then click Properties.Click the Auto Discovery tab, click to select the Publish automatic discovery information check box, and then click OK.Click Apply to update the firewall policy, and then click OK.TroubleshootingYou cannot assign a different ISA server or a different Microsoft Forefront Threat Management Gateway, Medium Business Edition server to each organizational unit.You cannot assign a different ISA server or a different Microsoft Forefront Threat Management Gateway, Medium Business Edition server to each organizational unit by using the Mspclnt.ini file. This was possible in Microsoft Internet Security and Acceleration Server 2000. If you want