Administering an ISP Installation

Resetting Permissions in a Sub-Web

The easiest way to fix permissions problems in FrontPage is through the client. This section gives two sets of procedures for you to correct these problems. The first tells you what to do if a user, who has permission, cannot access a web. The second tells you how the Check Server Extensions command can fix authoring problems.

Cannot Access a Web Site

These steps will ensure that the user can access a web.

To give access

1. If you get errors relating to the Service.lck file, turn off anonymous browsing on the Web server.
2. Log on as an administrator, and open the web that is having the problem.
3. Remove the user account that is receiving the error, and click Apply.
4. If the IUSR_computername account is listed under the Users tab, remove it.
5. Click the Groups tab. If Network, Interactive, or Everyone is listed, remove them, and click Apply.
6. Under the Users tab, set browse access to Only registered users have browse access, and click Apply.
7. After the settings have been applied, reset browse access to Everyone has browse access.
8. Add the problem account back in with author access, and click Apply.
9. If you had to disable anonymous browsing, enable it.

If the user is not able to write to a Web site, try the next procedure.

Cannot Perform Authoring Tasks

Occasionally, an author of a web might not be able to upload web content, modify the web directly on the server computer, or perform other authoring functions supported by FrontPage Server Extensions. The cause of the problem can range from accidentally deleting or renaming essential files to corrupting the Windows 2000 DACLs. The Check Server Extensions command addresses many authoring problems by doing the following:

• Checks that files have Read access permission.
• Checks that the files Service.cnf and Service.lck have Read and Write access.
• Updates the files Postinfo.html and _vti_inf.htm.
• Verifies that the files _vti_pvt, _vti_log, and _vti_bin are installed and that _vti_bin is executable.
• Determines whether virtual server roots or metabase settings are correct and up-to-date.
• Verifies that the IUSR_computername account doesn’t have Write access.
• Warns you if you are running on a FAT file system. If you are, you won’t be able to supply any Web security whatsoever (provided you’re running IIS 5.0).

To check server extensions on a web

1. In the console tree, right-click the web that you want to check, and fix the server extensions.

   The selected web will be checked and fixed, as well as all sub-webs below it.

2. Click Tasks on the shortcut menu, and then click Check Server Extensions.

   The Check Web window displays a status log for each web that is checked.

3. Select Yes if you see the following prompt: Do you want to tighten security as much as possible?

© 1997-1999 Microsoft Corporation. All rights reserved.