Open http://www through FP2k

Posted on 2003-12-03
Last Modified: 2013-12-04
Dear all,
Recently someone try to open my web page using Frontpage, , then FP prompt for username and password.
How can stop that at all.

More info:
Windows2000 Server
Norton FW.

Thanks in advance.
Question by:ethar1
  • 3
LVL 57

Expert Comment

by:Pete Long
ID: 9873164
on the server go to administration tools >IIS

Expand your server, right click it select properties, find the security menu unitick basic authentication, and everything else on that page

LVL 57

Assisted Solution

by:Pete Long
Pete Long earned 150 total points
ID: 9873172
HOW TO: Configure Web Server Permissions for Web Content in IIS;en-us;313075

HOW TO: Use the IIS Permissions Wizard;en-us;324070

HOW TO: Set IIS Permissions for Specific Objects;en-us;324068


Assisted Solution

Joseph_Moore earned 150 total points
ID: 9879568
Actually, I think this article would be helpful:
HOW TO: Install and Configure FrontPage 2000 Server Extensions on a Windows NT-Based Web Server (Windows NT or Windows 2000)

I suggest you remove the FP extensions if you don't use them for your site.
LVL 10

Accepted Solution

KingHollis earned 200 total points
ID: 9892329
This is a securtiy design. You don't want anyone opening your website with Frontpage unless they are specifically going to manipulate the website.

The Microsoft FrontPage server extensions may be installed automatically along with the Internet Information Server on a Windows Server. They are also used by other web management packages such as Visual InterDev. When they are installed automatically, the permissions are set to prevent outside access. However, if you are not careful you can
inadvertently change the access permissions and allow any outsider to change a website.

The site becomes vulnerable to attack when the users are given read execute (rx) access to the contents of the _vti_aut directory. This usually occurs when the site administrator sets the permissions on the webroot or _vti_bin directory and checks the check box "Replace permissions on subdirectories". This gives normal users execute access to the admin.dll and author.dll files.

There are three extensions in each root web of a website.

The extension shtml.dll handles user interactions with web forms and must be accessible to the users of your website. The extension admin.dll controls administration of a website and must be restricted to site administrators. The extension author.dll allows remote authoring of web pages on the site and access must be restricted to administrators and only those authors who are allowed to change the web pages. The directory and file permissions on these files and directories should be as follows:

_vti_bin   users (rx)(rx), authors (rx)(rx), administrators (rx)(rx)
_vti_adm   administrators (rx)(rx) no user or author access
_vti_aut   authors (rx)(rx), administrators (rx)(rx)

Here, users are the normal users of your web site including the web guest user IUSR_ if anonymous access is llowed. Authors are those people allowed to remotely change web pages and administrators are those users allowed to administer the web site.


Web site managers who are using FrontPage to administer their sites should check these permissions to insure that only those who are allowed to author or administer the site have access to the admin.dll and author.dll extensions. Web site managers who are using IIS servers but not FrontPage should check for the existence of the FrontPage extensions (check for the _vti_* directories and for _vti_inf.html in the web root directory) and, as Joseph_Moore suggested, remove them if FrontPage is not required.


1) Use care in tightening security through FrontPage Administrator. It’s easy to block access to everyone.
2) Test your permissions by attempting to edit your web page as a regular non-admin user. Put some character (like a dot) on the page and save it. If that character appears on the web page, you have a permission problem.  Apply this method remotely to see if an outsider can modify the web page. If this works, then you still have a permission problem.
3) Make sure you set permissions correctly on all copies of _vti_bin and its subdirectories.  There is one in each rootweb at a website.
4) Using scanners to identify this problem may not give you reliable results.  

LVL 57

Expert Comment

by:Pete Long
ID: 9921931

Featured Post

Comprehensive Backup Solutions for Microsoft

Acronis protects the complete Microsoft technology stack: Windows Server, Windows PC, laptop and Surface data; Microsoft business applications; Microsoft Hyper-V; Azure VMs; Microsoft Windows Server 2016; Microsoft Exchange 2016 and SQL Server 2016.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Recently, a new law in my state forced us to get a top-to-bottom analysis of all of our contract client's networks. While we have documentation, it was spotty at best for some - and in any event it needed to be checked against reality. That was m…
Article by: btan
The intent is not to repeat what many has know about Ransomware but more to join its dots of what is it, who are the victims, why it exists, when and how we respond on infection. Lastly, sum up in a glance to share such information with more to help…
This Micro Tutorial hows how you can integrate  Mac OSX to a Windows Active Directory Domain. Apple has made it easy to allow users to bind their macs to a windows domain with relative ease. The following video show how to bind OSX Mavericks to …
This video shows how to quickly and easily add an email signature for all users on Exchange 2016. The resulting signature is applied on a server level by Exchange Online. The email signature template has been downloaded from: www.mail-signatures…

809 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question