FrontPage access to local sites on server 2003

  • Thread starter Thread starter Allan
  • Start date Start date
A

Allan

I had this issue before and found a solution now the problem has returned and
I cannot now find that solution.

I have dozens of sites I manage on a local Windows 2003 server. This server
has been running for years with no issues.

Last week I did some MS updates and now I cannot use FrontPage on the lcal
server to access the local sites. I can edit them just frin from a remote PC
but I connot edit them from the local server.

It is often MUCH faster for me to do some database work on the local server
rather than have FrontPage temp cache MSAcess files that are in the 10s of
megs of size to a workstation.

When I Attempt to login in I am continuously prompted for my login
credentials and eventually have to simply cancel to end the issue.

I fixed this once with what I thought was a permissions setting.

Anyone remember how to overcome this?
 
Thanks for the response, but alas no, I have not updated to IE8.

I remember this being a permissions issue os some kind and I think I had to
modify perseion levels for the LocalService prcess but I cannot remember.

I had thought I save the darn article but I save so many tips it hard to
keep track of them all.

I can edit the sites from a remote computer but when you have a 10 or 20 meg
Access database, editing is much faster locally.
 
Thanks again Karen.

This issue is very hard to explain because it seems to make no sense. Using
the words "local server" gives the wrong impression of my issue.


I have a web server where I host many websites. Let's say for example the
website is http://www.visionquestit.com/

If I use that address to open the site in FrontPage from a remote PC I can
open it and edit it just fine in FrontPage.

If, however, I open FrontPage on the web server itself and attempt to do
that same thing, I only get the sign in dialog over and over even if I use
Adaministrative Level credentials.

I can open the site using local paths I.E. \\localhost\visionquestit\html\

The issue here is that if you use parenting paths, this can wreak havoc on
the site when FrontPage starts moving files around and tracking them for you
which is one of the great things I like about FrontPage.

I just don't know why this is such a problem and I wish I could remember how
to resolve it. I know it is a permission setting in the Windows\System32\root
folders. I just don't remember what they were and I am not willing to
arbitrarily play with them to work it out.

This came back because Microsoft was kind enough to put back the permissions
during the last update. Unfortunatly rolling back the update does not resolve
the permission issue since it does not reverse the setting to what they were.

This is definaltely not an Internet Explorer issue.
 
Back
Top