We are currently using an Apache 2. server with FP 2003 extensions - when
tryiong to access any site thru FP we get the following error:
The folder http://develop.villanova.edu is n't accessible. The folder may be
located in an unavailable location, protected with a password, or the
filename conatins a a / or \.
The directory/folder was working but we renamed the host name.
Since the rename, we cannot open the folder/directory using the EDIT with MS
FFP, thru the IE browser which we can do with most of the other sites or
diretcly thru FrontPage as we had previously been able to do. Any suggestion
s
on what we have done wrong? HELP

[ Post a follow-up to this message ]

Are the FP extensions installed?
If yes, have you re-install them since renaming the host?

Normally, FP has problems opening subdomains, so it is best use subwebs and 
point the subdomain to
the FP subweb, then you would open the root web, then open the subweb in FP.

--
 ========================================
======
Thomas A. Rowe (Microsoft MVP - FrontPage)
 ========================================
======
If you feel your current issue is a results of installing
a Service Pack or security update, please contact
Microsoft Product Support Services:
http://support.microsoft.com
If the problem can be shown to have been caused by a
security update, then there is usually no charge for the call.
 ========================================
======

"Marybeth" <Marybeth@discussions.microsoft.com> wrote in message
news:E894EFC0-B3F2-4822-8E0A-9FCD769595BB@microsoft.com...
> We are currently using an Apache 2. server with FP 2003 extensions - when
> tryiong to access any site thru FP we get the following error:
> The folder http://develop.villanova.edu is n't accessible. The folder may 
be
> located in an unavailable location, protected with a password, or the
> filename conatins a a / or \.
> The directory/folder was working but we renamed the host name.
> Since the rename, we cannot open the folder/directory using the EDIT with 
MS
> FFP, thru the IE browser which we can do with most of the other sites or
> diretcly thru FrontPage as we had previously been able to do. Any suggesti
ons
> on what we have done wrong? HELP

[ Post a follow-up to this message ]