Re: Really screwy password problem

Tech-Archive recommends: Fix windows errors by optimizing your registry

Sorry about my previous answer! I was not assuming that the website in question can also be quite complex in structure. I will amend the solution by adding this advice:

Only delete the folders that begin with _vti* inside the website on your hard-disk and then open the cleaned out website in MS Frontpage. Now connect to remote website and publish again.

"Kickin' Ass & Takin' Names" <PopUlist349@xxxxxxxxxxx> wrote in message news:dc1e14f6-be99-4a11-82dc-8b5a87b687f2@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
I suspect the answer to this is to contact my ISP -- I sent emails
late last night and anticipate an answer today, meanwhile, is it
possible that FP is causing this problem?

I maintain five websites on two different host servers.

HOST A:
website 1, 2, 3

HOST B:
Website 4, 5

I purchased a new computer, installed it Tuesday.

I copied my websites from my old computer's hard drive to an external
HD, then, when the new computer was running, I installed FP 2003 from
the original CD and copied the websites from the external HD to the
new computer's HD.

I then made minor editorial changes to each website and tried to
publish.

In the case of each of the five websites, when I hit the Publish
button, I got the usual pop-up into which I entered the publishing
destination, http://website.com. FP then came back and asked for user
ID and password. I entered the user ID and password that I have
written down in my documentation.

In the case of websites 1 and 2, the changed pages published without a
hitch.

In the case of websites 3, 4, and 5, I cannot get past the user ID and
password because FP tells me the server is not accepting my password.

However, in the case of each website, I can access the control panel.
For websites 3, 4, and 5, I went to the control panels and changed the
passwords. Tried to publish again with new passwords, nothing doing.

As I said at the outset, I suspect a problem with the host server but
thought I'd ask if there's a possibility that FP is causing the
problem.


.

Quantcast