Web sites do not open in Microsoft FrontPage after you configure FrontPage Server Extensions 2002 on an Apache 1.3.19 or later Web site

After you configure the Microsoft FrontPage Server Extensions 2002 on an Apache 1.3.19 or later Web site, the Web site does not open in Microsoft FrontPage.

This problem occurs if you use your _default_ Web site while you are specifying both a unique Fully-Qualified Domain Name (FDN) and any port other than port 80.

This problem occurs because of the way that FrontPage names the CNF files that are used when you open FrontPage-enabled Web sites. For example, virtual hosts may be defined in your Httpd.conf file similar to the way that they are defined in the following example:

<VirtualHost _default_:8080>
DocumentRoot /webdocs/public_html
ServerName www.example.com
</VirtualHost>
				

If you use this example, FrontPage Server Extensions 2002 creates a file in your /usr/local/frontpage/ folder that is named We8080.cnf. However, FrontPage Server Extensions 2002 creates a file that is named www.example.com:8080.cnf instead. Because FrontPage has to find a CNF file with the correct naming format, an error occurs when you try to open the Web site with the FrontPage client.

Use one of the following methods to work around this problem:

�	Use the correct naming format to rename the incorrectly named CNF file so that FrontPage can locate the file that it needs when you open the Web site. For example, if you use the example that is mentioned in the "Cause" section of this article, you would rename the www.example.com:8080.cnf file to We8080.cnf.
�	Create a symbolic link to the CNF file that FrontPage created. If you use the example that is mentioned in the "Cause" section of this article, use the following syntax to create a symbolic link: ln -s www.example.com:8080.cnf we8080.cnf

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