Access | control each FrontPage web (including each subweb) contains three ISAPI DLL copies that make up the FrontPage Server Extensions, which are generated in a directory in the FrontPage Web top-level directory.
▲_vti_bin/_vti_adm/admin.dll is to complete the task of managing the Web
▲_vti_bin/_vti_aut/author.dll is to write the FrontPage Web
▲_vti_bin/shtml.dll perform the browsing period behavior
FrontPage Server Extensions are stored in separate directories in the root directory of user files by sending HTTP Post requirements to these DLLs for all authoring and administration.
HTTP is a stateless protocol, and IIS handles each HTTP request independently of each other, for example, when an HTTP request accesses the Admin.dll of a Web site from FrontPage Explorer, IIS attempts to execute the request in an anonymous user iuser_hostname way. There are a number of reasons why IIS can perform Admin.dll processing requests:
(1), IIS may not allow anonymous browsing to be enabled
(2), the directory containing Admin.dll is not set to not be executable by IIS
(3), the Iusr_hostname user may not exist in Windows NT (created by IIS at installation time), or the user is disabled when IIS is installed
(4), Admin.dll ACL may not give Iusr_hostname permission to execute the file
If an anonymous user cannot perform the Admin.dll,web server returns error 401 (no access), then FrontPage Explorer prompts the viewer for a username and password and uses Windows NT to authenticate the user, who may not be able to see the prompt. Just as the viewer simply provides the security ID of the logged-on user, after the user is authenticated, IIS attempts to use the user-supplied account again, and if the authenticated user has permission to execute Admin.dll, then the user can become the FrontPage Administrator and do the appropriate action.
In practical applications, because FrontPage Explorer caches the user name and password at the time of the initial prompt, the user is not required to provide the user name and password at each HTTP request, but the user is prompted for a new username and password if the cached user name and password do not perform an operational license.
Even if the settings for FrontPage and IIS are correct, users may be prevented from accessing the FrontPage site, depending on the state of the user account, or if the Windows NT user no longer exists, is already disabled, or is in a state that cannot execute these ISAPI DLLs. All of these users will be denied access.
This article by the Beach Boy finishing production, you can reprint, but please specify its origin, thank you!
