T
TAV
Hello,
We are using FrontPage 2003 for our intranet. Your support is requested and
very much appreciated.
History: On occasion I (working on a development site) and the others
(working on a live page) would get prompted for user name and password to
"Connect to Inprov.pcu.hq" when trying to open a page to edit or publish a
page. We had never used passwords for FrontPage before. The work around was
to either enter our network logon (as sometimes this would work) or have
someone else publish or update. Or if we tried the next day everything was
fine. We did not get prompted to logon.
We recently relocated our intranet to a new server (2003 w/ SP2) and now
that we have gone live, with actually subwebs on development for the other
people, they are either:
1. Continually getting prompted for user name and password. They attempted
to use their network logon info but this was not acceptable.
2. Do not get prompted for user logon info. However when they save page
changes and then publish to live, the changed page does not appear.
At the server level, rights to the folders have been reviewed for the subweb
people and they all appear to be the same. I have full control and can open
the subwebs update and publish for them.
I located information on the web about Setting Permissions (Tools\Server)
when the live site is opened in FP. However I am getting approximately this
error message, "The FP Server Extensions 2002 is not compatible and too old
to use with this server" message. I have sent this to my server admin for
review and I hope updating.
So, I guess my question is, am I on the right track to get my subweb people
entry and publish rights?
Thanks again.
TAV
We are using FrontPage 2003 for our intranet. Your support is requested and
very much appreciated.
History: On occasion I (working on a development site) and the others
(working on a live page) would get prompted for user name and password to
"Connect to Inprov.pcu.hq" when trying to open a page to edit or publish a
page. We had never used passwords for FrontPage before. The work around was
to either enter our network logon (as sometimes this would work) or have
someone else publish or update. Or if we tried the next day everything was
fine. We did not get prompted to logon.
We recently relocated our intranet to a new server (2003 w/ SP2) and now
that we have gone live, with actually subwebs on development for the other
people, they are either:
1. Continually getting prompted for user name and password. They attempted
to use their network logon info but this was not acceptable.
2. Do not get prompted for user logon info. However when they save page
changes and then publish to live, the changed page does not appear.
At the server level, rights to the folders have been reviewed for the subweb
people and they all appear to be the same. I have full control and can open
the subwebs update and publish for them.
I located information on the web about Setting Permissions (Tools\Server)
when the live site is opened in FP. However I am getting approximately this
error message, "The FP Server Extensions 2002 is not compatible and too old
to use with this server" message. I have sent this to my server admin for
review and I hope updating.
So, I guess my question is, am I on the right track to get my subweb people
entry and publish rights?
Thanks again.
TAV