Microsoft KB Archive Search

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.

  1. Home
  2. You cannot use an IP address for AutoDiscovery in ISA Server 2004 Web Proxy Client

You cannot use an IP address for AutoDiscovery in ISA Server 2004 Web Proxy Client

View products that this article applies to.

Symptoms

Assume the following scenario: You try to configure AutoDiscovery for Microsoft ISA Server 2004 Web Proxy Client by changing the value of the
msFPCFQDN
registry value to an IP address. In this scenario, ISA Server 2004 replaces the IP address in the registry value with a fully qualified domain name (FQDN) after you restart your ISA Server 2004 computer.

For example, assume that your organization includes a load-balancing environment that uses an IP address instead of an FQDN. In this scenario, the ISA client computers in your organization may experience DNS and connectivity issues after you configure AutoDiscovery for ISA Server 2004 to use an IP address.

↑ Back to the top

Resolution

The fix for this problem is scheduled to be included in Service Pack 1 (SP1) for ISA Server 2004. For information about ISA Server updates, utilities, and service packs, visit the following Microsoft Web site:
http://www.microsoft.com/technet/isa/downloads/2004/default.mspx
After you apply SP1 for ISA Server 2004, you can prevent ISA Server 2004 from using the FQDN to replace the IP address after you restart your computer. To do this, create the following registry DWORD value:
AllowAlternativeFQDN=1
Then, follow these steps:
  1. Click Start, click Run, type regedit, and then click OK.
  2. Locate and then right-click the following registry subkey:
    HKEY_LOCAL_MACHINE\Software\Microsoft\FPC
  3. Point to New, and then click DWORD Value.
  4. Type AllowAlternativeFQDN, and then press ENTER.
  5. Right-click AllowAlternativeFQDN, and then click Modify.
  6. In the Value Data box, type 1, and then click OK

↑ 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: KB891066, kbbug, kbfix, kbqfe

↑ Back to the top

Article Info
Article ID : 891066
Revision : 6
Created on : 12/4/2007
Published on : 12/4/2007
Exists online : False
Views : 382