C
Carla B.
My hub and I are striving to untangle the combined impact
of a) my upgrade to Front Page 02 and b) his upgrading our
home server from NT4 to XP. The net effect of both is
making many things work differently, and it's hard to know
if a given problem stems from (a) or (b) or a bit of each.
The Setup: A home network server downstairs, talking to two
desktops upstairs. All of them now on XP. The Front Page
IIS extensions and all our local copies of prior webs live
on a _network_ drive ("Drive I").
The Problem: Since he re-installed the server extensions to
work with XP, I can't get my Front Page to "see" my prior
webs *as* webs. It will open the pages and show the folders
fine, but if I display a page in the browser, it displays
as: "file:///I:/InetPub/wwwroot/domainBU/(filename)".
A local web opened that way will publish to its www cousin
OK. But I can't publish BACK the other way, from the web
copy to the local copy out on Drive I. Error says: "The
folder I:\{directory)\domain1BU is contained by a
server-based web. To access this web, you must use the
http:// URL for the web server." Just telling it to use the
same path and preface it with http doesn't cut it either.
Nor can I designate any local webs as Favorites or fire up
a web on Drive I in FP by clicking on it in Explorer
(clicking on the folder does not open the web; it just
opens the folder and if I then click on a page, it opens
the page in the browser instead). When I open the
application, the webs on Drive I show in the Recent menu as
"I:\(directory)\ domain1BU" not as http anything. Does this
suggest my FP now doesn't "see" them as webs?
So which clue are we missing? A bullet list of options to
check will be welcome if the answer isn't obvious.
Thanks!
of a) my upgrade to Front Page 02 and b) his upgrading our
home server from NT4 to XP. The net effect of both is
making many things work differently, and it's hard to know
if a given problem stems from (a) or (b) or a bit of each.
The Setup: A home network server downstairs, talking to two
desktops upstairs. All of them now on XP. The Front Page
IIS extensions and all our local copies of prior webs live
on a _network_ drive ("Drive I").
The Problem: Since he re-installed the server extensions to
work with XP, I can't get my Front Page to "see" my prior
webs *as* webs. It will open the pages and show the folders
fine, but if I display a page in the browser, it displays
as: "file:///I:/InetPub/wwwroot/domainBU/(filename)".
A local web opened that way will publish to its www cousin
OK. But I can't publish BACK the other way, from the web
copy to the local copy out on Drive I. Error says: "The
folder I:\{directory)\domain1BU is contained by a
server-based web. To access this web, you must use the
http:// URL for the web server." Just telling it to use the
same path and preface it with http doesn't cut it either.
Nor can I designate any local webs as Favorites or fire up
a web on Drive I in FP by clicking on it in Explorer
(clicking on the folder does not open the web; it just
opens the folder and if I then click on a page, it opens
the page in the browser instead). When I open the
application, the webs on Drive I show in the Recent menu as
"I:\(directory)\ domain1BU" not as http anything. Does this
suggest my FP now doesn't "see" them as webs?
So which clue are we missing? A bullet list of options to
check will be welcome if the answer isn't obvious.
Thanks!