frontpage port 21 issues..

[Guest]

I have been adding content to my website the same way for the past 6 months
with no problems, but all of the sudden, I can't get my pages published.

The error message that comes up is "could not find a Web Server at
'www.domain.com' on port 21. Please check to make sure that the web server
name is valid and you proxy settings are set correctly."

If I publish the page individually, it will publish, but WITHOUT any
graphics. When I do a FULL publish of the entire site, the above error
message appears..

This is really frustrating, and I would appreciate any help..

 

[Rob Giordano \(Crash\)]

How are you "publish the page individually" ?


--
~~~~~~~~~~~~~~~~~~
Rob Giordano
Microsoft MVP Expression





|I have been adding content to my website the same way for the past 6 months
| with no problems, but all of the sudden, I can't get my pages published.
|
| The error message that comes up is "could not find a Web Server at
| 'www.domain.com' on port 21. Please check to make sure that the web
server
| name is valid and you proxy settings are set correctly."
|
| If I publish the page individually, it will publish, but WITHOUT any
| graphics. When I do a FULL publish of the entire site, the above error
| message appears..
|
| This is really frustrating, and I would appreciate any help..

 

[lurker]

I'm with you.
I have been dancing in the Expression Web newsgroup with exactly the same problem...
except I have about a dozen sun webs.

Fails on some sun webs, but does no fail on the root web.

After many weeks of everything being fine, but I was publishing with FrontPage extensions.

FP Extension support has been pulled, so I switch over to FTP.

My sub webs are large. The one I am having a problem with now is 75 MB.

Interesting testing results.

- Does not fail with Dreamweaver.
- Does fail with Front Page 2003
- Does fail with Expression Web
- Have tried both Active and Passive FTP
- Firewall disabled, still fails.

I find publishing works, but the cleanup at the end of publishing produces the error, so the publish aborts. My web
works, but next time I publish a change, the prior published files are not shown as being published, so they get
published again... all 75 MB.

Interesting test...
I have another machine in another town and I have NO problem with it publishing to the same domain/sub web.

From my failing machine, I can publish sub web to a different hosting provider and it works okay.

lurker

 

[Thomas A. Rowe]

FYI: If the FP extensions have been removed, then you no longer have subwebs, just plain folders, as
subwebs are a function of the FP extensions.

--
==============================================
Thomas A. Rowe
Microsoft MVP - FrontPage

http://www.Ecom-Data.com
==============================================

 

[lurker]

FYI: If the FP extensions have been removed, then you no longer have subwebs, just plain folders, as
subwebs are a function of the FP extensions.

Information appreciated.
Now I am confused.

on my machine they are folders with a "special folder" designation produced by Frontpage.

However, on my hosting provider, in the CPANEL, there is a tool to configure sub webs, or so I thought. Here is the one
that's driving my crazy now, but not the only one.
http://arianna.rnc3.com/

Maybe I am mis-using the term sub web.
It's still broke from this machine, but not any other machines.

lurker

 

[Thomas A. Rowe]

arianna is sub-domain of mc3.com

A subweb would be mc3.com/arianna

However a sub-domain can be pointed by the web host / CPanel to a FP subweb, so that the content can
be managed by FP.

--
==============================================
Thomas A. Rowe
Microsoft MVP - FrontPage

http://www.Ecom-Data.com
==============================================