If Comcast doesn't not support _underscored folders they don't support or understand the FP SE (even though they may be claiming to)
FP uses _hidden folders to manage a FP SE site and will fail w/o them
--
| Done, and many thanks for your help. No change--but in the meantime I checked
| on the community forum at Comcast. Surprise! Although the "online chat" rep I
| talked to this morning said that there was no problem on Comcast's end, in
| fact it seems that quite a few people are having this very problem.
|
| (1) Here's the Comcast message:
|
| "Some of you use Frontpage to develop and upload files to your Comcast
| webspace and have been experiencing some problems. After some initial
| investigation, the problem seems to be related to foldernames that Frontpage
| creates that start with a "_" (underscore) character.
|
| "Thus, this message is to let you know that we are aware of this issue and
| are working to resolve it. As more information becomes available, we will
| keep you updated. In the meantime, if you are experiencing errors with
| uploading files, please consider using FTP to upload files until this issue
| is resolved."
|
| (2) Here's a user-submitted workaround for those who need the full
| functionality of FP extensions (I don't, so I can't vouch for it):
|
| "Here's a work-around that I found on an online Front Page Discussion Group.
| I tried it and it worked for me.
|
| "It's a two-part problem having to do with the FP extensions.
|
| "First part: Any time a site created by FP is published using FTP it
| corrupts the FP extensions. In order to "fix" the extensions the host
| (Comcast) has to fix them on their end.
|
| "Second part: In order to use the "fixed" extensions, the user (you and me
| and anyone else using FP) has to go into their account profile, unsubscribe
| the FP extensions, sign out of Comcast, sign back in, subscribe to the FP
| extensions.
|
| "Cumbersome, I know, but it is a valid work-around until Comcast can do a
| permanent "fix"."
|
|
|
| "Thomas A. Rowe" wrote:
|
| > Ok, add it but make sure the https is unchecked when you add it.
| >
| > --
| > ==============================================
| > Thomas A. Rowe (Microsoft MVP - FrontPage)
| > WEBMASTER Resources(tm)
| >
| > FrontPage Resources, WebCircle, MS KB Quick Links, etc.
| > ==============================================
| > To assist you in getting the best answers for FrontPage support see:
| >
http://www.net-sites.com/sitebuilder/newsgroups.asp
| >
| > | > > There are no sites in "Trusted Sites," but I unchecked the https box anyway.
| > > No change. Sigh.
| > >
| > > "Thomas A. Rowe" wrote:
| > >
| > >> Check your IE Trusted Site settings and make sure the https is not check for your domain. You may
| > >> have to delete it and re-enter it.
| > >>
| > >> --
| > >> ==============================================
| > >> Thomas A. Rowe (Microsoft MVP - FrontPage)
| > >> WEBMASTER Resources(tm)
| > >>
| > >> FrontPage Resources, WebCircle, MS KB Quick Links, etc.
| > >> ==============================================
| > >> To assist you in getting the best answers for FrontPage support see:
| > >>
http://www.net-sites.com/sitebuilder/newsgroups.asp
| > >>
| > >> | > >> > Thanks for the info. According to Comcast, the FrontPage server extensions
| > >> > ARE enabled for my account. I disable and reenabled them, but his had no
| > >> > effect. Is there any way to determine the source of the "port 443" error?
| > >> > That is, is there any simple way to find out whether it is a problem with the
| > >> > server, or with my firewall, or my Windows settings somewhere? Thanks again!
| > >> >
| > >> > "Thomas A. Rowe" wrote:
| > >> >
| > >> >> Ok, since the server doesn't have the extensions, means that you can not use any of the FP
| > >> >> features
| > >> >> that require the run-time extensions, such as Hit Counter, Guest Book, Discussion Web, the
| > >> >> Feedback
| > >> >> Form via the FP Form Handler, Custom Linkbars, nor will you ever be able to retrieve your site
| > >> >> structure, navigation and custom theme, if you loose your local copy.
| > >> >>
| > >> >> --
| > >> >> ==============================================
| > >> >> Thomas A. Rowe (Microsoft MVP - FrontPage)
| > >> >> WEBMASTER Resources(tm)
| > >> >>
| > >> >> FrontPage Resources, WebCircle, MS KB Quick Links, etc.
| > >> >> ==============================================
| > >> >> To assist you in getting the best answers for FrontPage support see:
| > >> >>
http://www.net-sites.com/sitebuilder/newsgroups.asp
| > >> >>
| > >> >> | > >> >> > Fascinating. Here was the result: "The server you are publishing to does not
| > >> >> > have the FrontPage Server Extensions installed, and therefore does not
| > >> >> > support publishing via HTTP." So FP directed me to use an FTP address
| > >> >> > instead, which I did, and it worked. I guess that's all that matters! Thanks
| > >> >> > for your help!
| > >> >> >
| > >> >> > "Thomas A. Rowe" wrote:
| > >> >> >
| > >> >> >> Try publishing to http:// instead of https:// and uncheck the SSL box. If this works, then
| > >> >> >> check
| > >> >> >> with the host to make sure that the FP extensions are configured on the server to support
| > >> >> >> SSL
| > >> >> >> (port
| > >> >> >> 443)
| > >> >> >>
| > >> >> >> --
| > >> >> >> ==============================================
| > >> >> >> Thomas A. Rowe (Microsoft MVP - FrontPage)
| > >> >> >> WEBMASTER Resources(tm)
| > >> >> >>
| > >> >> >> FrontPage Resources, WebCircle, MS KB Quick Links, etc.
| > >> >> >> ==============================================
| > >> >> >> To assist you in getting the best answers for FrontPage support see:
| > >> >> >>
http://www.net-sites.com/sitebuilder/newsgroups.asp
| > >> >> >>
| > >> >> >> | > >> >> >> > It's an "https" address, so I assume 443--the SSL box is checked in the
| > >> >> >> > FrontPage publishing box. RD
| > >> >> >> >
| > >> >> >> > "Tom Pepper Willett" wrote:
| > >> >> >> >
| > >> >> >> >> Are you supposed to be publishing to port 443 (SSL) or port 80?
| > >> >> >> >> --
| > >> >> >> >> ===
| > >> >> >> >> 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
| > >> >> >> >> ===
| > >> >> >> >> | > >> >> >> >> |I use FrontPage 2000-SP1 with Windows XP Pro SP2. Yesterday, I updated my
| > >> >> >> >> web
| > >> >> >> >> | site several times using FrontPage with no problem. This morning, I began
| > >> >> >> >> | receiving the following error message when I clicked "publish": "Could not
| > >> >> >> >> | find a web server at 'home.comcast.net' on port 443. Please check to make
| > >> >> >> >> | sure that the web server name is valid and your proxy settings are set
| > >> >> >> >> | correctly."
| > >> >> >> >> |
| > >> >> >> >> | (1) The web server is up and running. After receiving this message, I was
| > >> >> >> >> | able to upload files using Comcast's built-in HTTP upload system.
| > >> >> >> >> |
| > >> >> >> >> | (2) The address in the "publish" box is correct.
| > >> >> >> >> |
| > >> >> >> >> | (3) I have no proxy settings in Internet Explorer.
| > >> >> >> >> |
| > >> >> >> >> | (4) I turned off my firewall (Norton Internet Security) but that didn't
| > >> >> >> >> make
| > >> >> >> >> | any difference.
| > >> >> >> >> |
| > >> >> >> >> | (5) The only program I installed between yesterday and today was the
| > >> >> >> >> | Microsoft .NET framework and its associated security updates.
| > >> >> >> >> |
| > >> >> >> >> | Any idea what might be causing this problem? Thanks!
| > >> >> >> >>
| > >> >> >> >>
| > >> >> >> >>
| > >> >> >>
| > >> >> >>
| > >> >> >>
| > >> >>
| > >> >>
| > >> >>
| > >>
| > >>
| > >>
| >
| >
| >
