When you try to use the FrontPage client to connect to a Web
site or to publish a Web site, you receive the following error message, and the
Web site is not opened:
The Web server at
http://address does not appear to have the FrontPage
server extensions installed.
is a server having the following
- The server is running Microsoft Internet Information
- The FrontPage Server Extensions are installed on the
- The URLScan utility is installed.
When you install the URLScan utility, the Urlscan.ini file
that lists default settings is installed. The default settings deny requests
from FrontPage to access the server.
You can use the FrontPage Server Extensions if you edit the
settings in the Urlscan.ini file. To do this, follow these steps:
- Locate the Urlscan.ini file in Windows Explorer. By
default, this file is created in the following folder:
where Drive represents the drive
letter of your hard disk.
- Create a copy of the file and name it
- In Notepad, open the original copy of the Urlscan.ini
- Locate the [Options] section. Change the AllowDotInPath=0
setting to AllowDotInPath=1.
- Locate the [AllowVerbs] section. Change the ;OPTIONS verb
to OPTIONS. (Removing the semicolon uncomments the line.)
NOTE: If URLScan 2.1 is installed, you do not need to make this
change. This was corrected in URLScan 2.1. URLScan 2.1 is available at the
following Microsoft web site: If you have URLScan 2.0, you need to make this change. Version
2.0 is included on the compact disc.
- Save the file to replace the original.
- Stop and restart IIS services.
Using NET STOP and NET START Commands to Force IIS Services to Re-Read the Registry
Internet Information Services 5.0 Command-Line Syntax for Iisreset.exe
- Test the ability to connect with FrontPage.
If you encounter further difficulties with other IIS
functionality while URLScan is running, set EnableLogging=1 in the [Options]
section of Urlscan.ini and then restart IIS. If any errors occur, check the
last entries in the Urlscan.log file for information about what requests are
URLScan protects your server from attacks by turning off
functionality that is not being used by the server. The default settings in the
Urlscan.ini file, included in the downloadable file, assume that the server is
serving only Active Server Pages (ASP) and static content, such as Hypertext
Markup Language (HTML) pages and images. It also assumes that you are not using
the following technologies:
- CGI (.exe) executables
- Index Server
- Internet or HTTP-based printing
- Server Side Includes (SSI)
If you need to use any of these technologies, you will need to
change the Urlscan.ini file accordingly.
For additional information about installing and configuring URLScan, click the
following article number to view the article in the Microsoft Knowledge Base:
Using URLScan on IIS
How To Use URLScan with FrontPage 2000
Other Settings That May Affect FrontPage
- Specifying an AlternateServerName prevents FrontPage from
connecting or publishing, even if it is configured to return the actual Web
- Setting RemoveServerHeader=1 also prevents FrontPage from
connecting or publishing.
- For the CGI-based FrontPage Hit Counter Web component to
function, you need to enable the use of files with the .exe extension in the
Urlscan.ini file. Because this allows other CGI applications to execute as
well, the administrator should consider using an ISAPI or ASP-based hit
For additional information about using an ASP-based hit counter
with FrontPage, click the article number below to view the article in the
Microsoft Knowledge Base:
309008 To allow requests for files with the .exe
extension, set one of the following configurations:
HOW TO: Use the ASP PageCounter Component in FrontPage 2000
- If you set UseAllowExtensions=0, then comment out or
remove .exe from the [DenyExtensions] section of the Urlscan.ini
- If you set UseAllowExtensions=1, then add .exe to the
[AllowExtensions] section of the Urlscan.ini file.
- Setting AllowLateScanning=1 loads URLScan as a low priority
filter. This allows URLScan to be loaded below the FrontPage down-level
compatability filter, Fpexedll.dll. For
additional information about the Fpexedll.dll filter and URLScan, click the
following article numbers to view the articles in the Microsoft Knowledge Base:
Frequently asked questions about Fpexedll.dll
How To Use URLScan with FrontPage 2000
Article ID: 307976 - Last Review: February 27, 2014 - Revision: 2.3
- Microsoft FrontPage 2002 Standard Edition
- Microsoft FrontPage 2002 Server Extensions
- Microsoft FrontPage 2000 Standard Edition
- Microsoft FrontPage 2000 Server Extensions
- Microsoft Visual InterDev 1.0 Standard Edition
- Microsoft Visual InterDev 6.0 Standard Edition
|kbnosurvey kbarchive kbwebpublishing kbwebserver kbopenfile kberrmsg kbprb KB307976|