Published remote to local for years...new FP server blocks access

[Guest]

I have published for years, now with FP 2003, remote to local. I work off of
web server and back up (publish) to local. I changed host and now FP will
not publish. The new host (networksolutions) supports FP extensions and I
have enabled them for my account. I can FTP with FP but when I Publish FP or
SharePoint Services I get: "Unable to open "http://..." Server Error: FP
security violation. Possible causes:
blahblahblah. I think the issue not in the FP extension but the way my
local FP stores the password...it still thinks it is logging onto the old
host. The password dialogue box does only works for FTPing. How can I get
FP to wise up and let me give the local copy the new password and username?

 

[Guest]

Quit FrontPage, display My Network Places, delete any entries that point to
your live site, then start FrontPage and try opening the site again.

Jim Buyens
Microsoft MVP
http://www.interlacken.com
Author of:
*----------------------------------------------------
|\---------------------------------------------------
|| Microsoft Windows SharePoint Services Inside Out
|| Microsoft Office FrontPage 2003 Inside Out
||---------------------------------------------------
|| Web Database Development Step by Step .NET Edition
|| Microsoft FrontPage Version 2002 Inside Out
|| Faster Smarter Beginning Programming
|| (All from Microsoft Press)
|/---------------------------------------------------
*----------------------------------------------------

 

[Andrew Murray]

it is not frontpage blocking access -

One Solution: probably the Windows firewall is configured incorrectly (or
your firewall that you use if not the Windows one). So you need to list the
fpage.exe or something executable in your 'exceptions' list as a valid
program that requires internet access - one that you know is allowed to have
access.

 

[Guest]

Jim, thanks for the tip. I did not think to delete that reference. However,
I still get the i message: folder http://... isn't accessible...may be
located on an unavailable location, protected with a password, or the
filename contains...

I can access this site with FP FTP so I know the site is accessible. The
one thing that is not happening with the FP publish to FP server is that I
have yet to see a password dialogue box. FP FTP pops up a password and user
name dialogoue box and I simply supply it with the new data. Do you have any
other suggestions on how I might force FP publish to FP server to show me a
password and username box?

 

[Tom Pepper Willett]

The folder "http://Website" isn't accessible. The folder may be located on
an unavailable volume or protected with a password.

http://support.microsoft.com/support/kb/articles/Q260/7/55.ASP
http://support.microsoft.com/support/kb/articles/Q264/7/49.ASP
http://support.microsoft.com/support/kb/articles/Q266/6/65.ASP
http://support.microsoft.com/support/kb/articles/Q272/5/42.ASP
http://support.microsoft.com/support/kb/articles/Q287/3/99.ASP
http://support.microsoft.com/support/kb/articles/Q310/8/46.ASP

Alternatively, you may wish to download the FREE Jimco Open Web which
bypasses the possibly corrupted web folders: www.jimcoaddins.com
--
===
Tom "Pepper" Willett
Microsoft MVP - FrontPage
---
About FrontPage 2003:
http://office.microsoft.com/home/office.aspx?assetid=FX01085802
FrontPage 2003 Product Information:
http://www.microsoft.com/office/frontpage/prodinfo/default.mspx
Understanding FrontPage:
http://msdn.microsoft.com/office/understanding/frontpage/
FrontPage 2002 Server Extensions Support Center:
http://support.microsoft.com/default.aspx?scid=fh;en-us;fp10se
===
| Jim, thanks for the tip. I did not think to delete that reference.
However,
| I still get the i message: folder http://... isn't accessible...may be
| located on an unavailable location, protected with a password, or the
| filename contains...
|
| I can access this site with FP FTP so I know the site is accessible. The
| one thing that is not happening with the FP publish to FP server is that I
| have yet to see a password dialogue box. FP FTP pops up a password and
user
| name dialogoue box and I simply supply it with the new data. Do you have
any
| other suggestions on how I might force FP publish to FP server to show me
a
| password and username box?
|
| "Jim Buyens" wrote:
|
| > Quit FrontPage, display My Network Places, delete any entries that point
to
| > your live site, then start FrontPage and try opening the site again.
| >
| > Jim Buyens
| > Microsoft MVP
| > http://www.interlacken.com
| > Author of:
| > *----------------------------------------------------
| > |\---------------------------------------------------
| > || Microsoft Windows SharePoint Services Inside Out
| > || Microsoft Office FrontPage 2003 Inside Out
| > ||---------------------------------------------------
| > || Web Database Development Step by Step .NET Edition
| > || Microsoft FrontPage Version 2002 Inside Out
| > || Faster Smarter Beginning Programming
| > || (All from Microsoft Press)
| > |/---------------------------------------------------
| > *----------------------------------------------------
| >
| >
| > "Fact" wrote:
| >
| > > I have published for years, now with FP 2003, remote to local. I work
off of
| > > web server and back up (publish) to local. I changed host and now FP
will
| > > not publish. The new host (networksolutions) supports FP extensions
and I
| > > have enabled them for my account. I can FTP with FP but when I
Publish FP or
| > > SharePoint Services I get: "Unable to open "http://..." Server Error:
FP
| > > security violation. Possible causes:
| > > blahblahblah. I think the issue not in the FP extension but the way
my
| > > local FP stores the password...it still thinks it is logging onto the
old
| > > host. The password dialogue box does only works for FTPing. How can
I get
| > > FP to wise up and let me give the local copy the new password and
username?

 

[Guest]

Andrew, "blocking" was a poor choice of words on my part. I did as you
adviced and allowed FP.exe to have free reign with Norton. I even shut down
Norton with better result. The problem I am having now was not an issue with
my firewall or anti hacking tools before. Prior to moving my FP web site to
another FP server, everything was well in administering my site remotely and
publishing back locally for a backup. What did you think of Jim's tack? Is
it possible that FP publish is going to my old server? Or going to the new
server with my old password and username?

 

[Guest]

My tack is that FrontPage is going to the new server with your old password
and username. Because (I presume) you're using the same DNS name as before,
FrontPage doesn't "know" that the server has changed.

If the new site has its own IP address, you can test this by trying to open
http://<IP address>, as in http://192.168.1.1

Have you tried the suggestions in the articles Tom suggested?

Jim Buyens
Microsoft MVP
http://www.interlacken.com
Author of:
*----------------------------------------------------
|\---------------------------------------------------
|| Microsoft Windows SharePoint Services Inside Out
|| Microsoft Office FrontPage 2003 Inside Out
||---------------------------------------------------
|| Web Database Development Step by Step .NET Edition
|| Microsoft FrontPage Version 2002 Inside Out
|| Faster Smarter Beginning Programming
|| (All from Microsoft Press)
|/---------------------------------------------------
*----------------------------------------------------

 

[Guest]

Tom, thanks. You gave me enough to keep me busy for the weekend. I want to
research this more and get it right the first time because it sounds like I
could really screw things up if I just start poking around. I will get back
to you on this endeavor.

 

[Guest]

Yup, Jim...same DNS. I think I did the number addy once early on with no
luck but it is worth trying it again before I go for the headier stuff Tom
supplied me. You all are great. thanks again.

 

[Guest]

Tom, would a FP uninstall work for wiping out any vesture of the old IP?

 

[Guest]

Tom, I have went through the list of asp finds with these results:
1) most of them apply to FP2000 so no inKfile node in the registry
2) it was helpful to use the command line with frontpg
3) I still have not been able to open the sith with FP

I did find out that NetworkSolutions sets up a third level IP on there FP
server.
This means that whether I give FP Open Site, http://www.[DNS] or http://[3rd
level].netsolhost.com, FP returns an error message stated it cannot locate
the site. When I run "frontpg http://[3rd level].netsolhost.com" from the
command line FP opens the index.htm page locally for editing but is not
logged onto the site.

I can ping both the netsolhost server, 205.175.148.65 and my 3rd level site.

I can log onto my 3rd level site with FP ftp...transfer files to and fro in
the FP Remote and Local windows.

Is there a FP startup switch...like, "frontpg /p..." that I can run from the
command line or a shortcut to somehow control FP's password and username
settings for DNS?

Why does FP make following a DNS relocation of IP so tough?

 

[Guest]

Jim, I getting desparate here. I have called my IP help desk and they think
it is FP. Would you read the post 4/11 I put up today for Tom Pepper W. and
let me know if there is anything I missed?

 

[Guest]

Have you tried the same operation from a different computer? Preferably one
that never opened the old site? This would help localize the problem.

Is it possible an Internet firewall of some kind is getting in the way?

Otherwise, try the procedure described at:

FrontPage Publish Command Fails
http://www.interlacken.com/winnt/tips/tipshow.aspx?tip=24

Jim Buyens
Microsoft MVP
http://www.interlacken.com
Author of:
*----------------------------------------------------
|\---------------------------------------------------
|| Microsoft Windows SharePoint Services Inside Out
|| Microsoft Office FrontPage 2003 Inside Out
||---------------------------------------------------
|| Web Database Development Step by Step .NET Edition
|| Microsoft FrontPage Version 2002 Inside Out
|| Faster Smarter Beginning Programming
|| (All from Microsoft Press)
|/---------------------------------------------------
*----------------------------------------------------

 

[Guest]

Jim, we (ya'll) "cracked the nut"! I have now sucessfully Open my site with
FP and Published local to remote. Here is how it worked: File=>Open
Site...=>Site name:[http://[3rd level pointer supplied by new IP Network
Solutions].netsolhost.com]. I know I attempted this procedure before with no
luck but for some reason it worked this morning. Perhaps the new IP needed
to simmer a bit longer, eh. Anyways, thank you all for the fantastic
support. I think FP's poor functioning with IP changes and my lack of
understanding of third level IP's both contributed to the problem.