completely uninstall frontpage 2003

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

What's the best procedure to completely uninstall FP so that I can reinstall
it again without leftover files from the first install?
 
Uninstall, reboot, reinstall.

Why do you think you need to do this??

--
Steve Easton
Microsoft MVP FrontPage
95isalive
This site is best viewed..................
...............................with a computer
 
Because I tried the procedure you just told me, but when I reinstalled the
software, all of the settings were exactly as they were before the uninstall.
Some must be left behind.
Also, if you remember my past post about not being able to import or publish
to a remote server. The techs reinstalled FPE and says it works fine on their
end, so it must be on my side.
 
What settings were left behind.

I vaguely remember the post, but need you to refresh my memory please.
I visit about 40 different news groups every day.

;-)

--
Steve Easton
Microsoft MVP FrontPage
95isalive
This site is best viewed..................
...............................with a computer
 
Here's the run down on this problem.
I created a web site on FP 2003. It published fine up until recently.
Now, I can publish it from my work computer, but for some odd reason, it
won't publish from my home computer anymore. I deleted the web files on my
home computer and tried to import the site again, but no luck. It doesn't
even ask me for a logon to the server like it used to.
Now, I am working on a site which is located on another server and it
imports and publishes fine, both at home and at work.
I had tech support reinstall the FP extensions, but that didn't help either.
They said there are no problems on their end, so I figure it's my end.
I tried uninstalling and reinstalling FP, but that didn't work either.
Here's another wrench to throw into the works. I have two computers setup at
home. Each of them has their own copy of FP 2003 (legit copies). Neither one
of them can import the site.
Now, why will my work computer import and publish fine, but my home computer
won't? Are there certain permissions on there server which knows where I am
trying to access it from and won't allow it?
I am stumped. Please help.
 
Have you tried deleting the .web extensions cache files? A tool at
http://www.95isalive.com/fixes/fpclean.htm can be used to delete
these, and the FP temporary files as well.

If this fails, then:
Do the home computers have any network security in common (firewalls,
routers) that are not in use at your work?

It may be problem establishing an authentication dialogue, because the
server is using NTLM authentication and something in the network path
from your Home Computer->ISP->WebHost is blocking this. Changing
the server to use Basic authorisation may solve this problem, but
Basic (uses plain text) is not as secure as NTLM (uses encrypted text
for password).
 
Thanks for the tips.

I have been on the phone with tech support this morning, and this is what
seems to be the problem (they say anyway):

For some reason, the DNS "A" has to be repropagated. According to support,
there are four different types of DNS. One is the www, which everyone uses to
find a web site through their browser. Next, there is the "A" DNS, which
authoring software, such as Frontpage, use to log into the server to publish
files. I think he called it the Authoratative DNS. This DNS is the one that
allows entrance to a server. Without it, Frontpage cannot find the server, or
be allowed to publish to it.
So, they have to repropagate the "A" DNS to the world as he said. The two
other DNS we didn't talk about because it didn't concern me right now.

My question to him was, "how come I can publish to the server from my work
computer and not my home system?". He said because they also provide our ISP
services at work, and their servers are the first to be updated with my new
DNS. My home computer is on a different service, I have to wait for the DNS
to propagate to my ISP's DNS server.

Anyway, that's what's happening up to this point. I learned something new
about servers. I just hope tech support has it all squared away.

My final question to any MVP... Have you ever heard of this happening before?
 
If it's a new domain, then it takes up to 3 days (normally) for DNS
servers worldwide to be updated.
Some (very few) DNS servers are updated only once a week - these may
not "know" of the new domain until several days after the rest of the
world.
So, yes, what you describe can happen - your work's DNS servers may
have been updated immediately, but your ISP may be lagging behind.
 
It's not a new domain, so it's strange how one day I could publish to it at
home and work, then the next I could only publish to it at work. I suppose it
can happen. I'm too well versed in servers. I have enough to learn designing
web sites.

I'll just wait to see what happens and let you all know how it goes.

Thanks for your help!
 
By any chance did your web service provider move your web to a new server
with a different IP address??


--
Steve Easton
Microsoft MVP FrontPage
95isalive
This site is best viewed............
........................with a computer
 
That is a good question. They didn't tell me if they did or not. They just
said the "A" DNS records had to be repropagated.

I'm just going to have to wait and see how long it takes, if indeed that is
the problem. I can't understand why it worked one day and not the next. But
of course, I don't know much about servers either, so this is a learning
experience for me.
 
Back
Top