The information in this article applies to:
SYMPTOMSFrontPage authors may not be able to access Webs located within virtual servers on a multihomed computer running Microsoft Internet Information Server (IIS) versions 2.0 and 3.0. For example, a user who has author permissions, or who is a member of a Windows NT group that has author permissions for a Web, may not be able to access a Web within a virtual server. In this case, when trying to open the Web in FrontPage Explorer, access will not be granted if the author uses his/her own account information, but access will be granted if the author uses the administrator's account information. This may apply to both root Webs and subWebs within some or all virtual servers. CAUSE
The first time you install IIS, a home directory that does not have an IP
address associated with it is created. When you install FrontPage Server
Extensions, the FrontPage Server Administrator identifies this home
directory as "<Default Server>" (without the quotation marks). When you add
virtual servers to the IIS, each one is assigned an IP address using the
Directory Properties page in Internet Service Manager. The FrontPage Server
Administrator identifies each one by it's IP address. If The FrontPage
Server Extensions are installed into <Default Server> and any number of
virtual servers, the Server Extensions may not be able to identify whether
a particular user is a valid author of the Web.
RESOLUTIONTo resolve this behavior, remove the FrontPage Server Extensions from the IIS <Default Server>, assign a valid IP address to the <Default Server> making it a virtual server, and then reinstall the FrontPage Server Extensions. To do this, use the following steps:
STATUSMicrosoft has confirmed this to be a problem in the Microsoft products listed at the beginning of this article. Additional query words: front page
Keywords : fpiis |
Last Reviewed: August 2, 1999 © 2000 Microsoft Corporation. All rights reserved. Terms of Use. |