Problems using Frontpage 2003 FTP for uploading

[Bernhard]

Hi,

Have a strange problem when trying to use FrontPage 2003 FTP for uploading
to a server. All the files is transferred but at the last one FrontPage FTP
hangs.
Looking at the transmission in Ethereal you se that for all files FrontPage
FTP
issues a PASV command and gets a response with the protnumber to use.
(Sitting behind a NAT so I have to use PASV and the server supprots it).

When the last file is transferred it issues yet another PASV command and
gets a response with a new portnumber. BUT, here comes the strange thing,
it tries to establish a tcp-connectionj using the previous PASV response
portnumber i.e. that used when transferring the last file.

The same happens if I only uploads one file. The file is correctly
transferred but
the FrontaPage tries to establish a new data connection.

I do not understand why this last PASV command is issued as all files have
been
transferred and, furthermore, I don't understand why an old port number is
used by frontpage to set up the TCP connection.

Maybe this have been discussed earlier on this list. If so please forgive me
for my ignorance. Please advise me if and how this problem could be solved.

Thanks!

For those interested in the details I have appended a condesed version of
the Ethereal logs:


TYPE A
200 TYPE is now ASCII
PASV
227 Entering Passive Mode (81,228,11,138,180,63)
Passive port = 46143
STOR aktuellt.htm
150 Accepted data connection
226-459772.9 Mbytes free disk space
226-800 Kbytes used (7%) - authorized: 10240 Kb
226-File successfully transferred
226 2.417 seconds (measured here), 4.20 Kbytes per second

Data thus transferred and the passive data connection is closed but now
FrontPage FTP tries to open a new data connection:

TYPE A
200 TYPE is now ASCII
PASV
227 Entering Passive Mode (81,228,11,138,180,63)
Passive port = 38936
TCP 1927 > 46143 [SYN] Seq=0 Win=65535 Len=0 MSS=1460

I.e. Frontpage FTP tries to use the previous port in a new data connection
without
having anything to send !!!???? And of course the server terminates the
session
and FrontPage tries to login in again and does the same misstake and this
scheme
continues ad nauseum. Aborting makes FrontPage crash!!!

 

[Steve Easton]

FrontPage uses the internet connection and parameters established by and in
Internet Explorer.

Try resetting web settings in IE > Tools > Internet Options > Programs.

--
Steve Easton
Microsoft MVP FrontPage
95isalive
This site is best viewed............
........................with a computer

 

[Bernhard]

Thanks for the fast answer. Unfortuantely´FrontPage FTP still
uses the old portnumber.

Regards,

Bernhard.

"Steve Easton" skrev:

FrontPage uses the internet connection and parameters established by and in
Internet Explorer.

Try resetting web settings in IE > Tools > Internet Options > Programs.

--
Steve Easton
Microsoft MVP FrontPage
95isalive
This site is best viewed............
........................with a computer

Hi,

Have a strange problem when trying to use FrontPage 2003 FTP for uploading
to a server. All the files is transferred but at the last one FrontPage
FTP
hangs.
Looking at the transmission in Ethereal you se that for all files
FrontPage
FTP
issues a PASV command and gets a response with the protnumber to use.
(Sitting behind a NAT so I have to use PASV and the server supprots it).

When the last file is transferred it issues yet another PASV command and
gets a response with a new portnumber. BUT, here comes the strange thing,
it tries to establish a tcp-connectionj using the previous PASV response
portnumber i.e. that used when transferring the last file.

The same happens if I only uploads one file. The file is correctly
transferred but
the FrontaPage tries to establish a new data connection.

I do not understand why this last PASV command is issued as all files have
been
transferred and, furthermore, I don't understand why an old port number is
used by frontpage to set up the TCP connection.

Maybe this have been discussed earlier on this list. If so please forgive
me
for my ignorance. Please advise me if and how this problem could be
solved.

Thanks!

For those interested in the details I have appended a condesed version of
the Ethereal logs:


TYPE A
200 TYPE is now ASCII
PASV
227 Entering Passive Mode (81,228,11,138,180,63)
Passive port = 46143
STOR aktuellt.htm
150 Accepted data connection
226-459772.9 Mbytes free disk space
226-800 Kbytes used (7%) - authorized: 10240 Kb
226-File successfully transferred
226 2.417 seconds (measured here), 4.20 Kbytes per second

Data thus transferred and the passive data connection is closed but now
FrontPage FTP tries to open a new data connection:

TYPE A
200 TYPE is now ASCII
PASV
227 Entering Passive Mode (81,228,11,138,180,63)
Passive port = 38936
TCP 1927 > 46143 [SYN] Seq=0 Win=65535 Len=0 MSS=1460

I.e. Frontpage FTP tries to use the previous port in a new data connection
without
having anything to send !!!???? And of course the server terminates the
session
and FrontPage tries to login in again and does the same misstake and this
scheme
continues ad nauseum. Aborting makes FrontPage crash!!!

 

[Bernhard]

Just to clarify - I reset the web settings ut still the same strange
behaviour. Also, I have been trying other FTP software like CuteFTP without
any problem towards the same server and in passive mode. Anyone expericing
something similar with Frontpage FTP?

Regards,

Bernhard.


"Steve Easton" skrev:

FrontPage uses the internet connection and parameters established by and in
Internet Explorer.

Try resetting web settings in IE > Tools > Internet Options > Programs.

--
Steve Easton
Microsoft MVP FrontPage
95isalive
This site is best viewed............
........................with a computer

Hi,

Have a strange problem when trying to use FrontPage 2003 FTP for uploading
to a server. All the files is transferred but at the last one FrontPage
FTP
hangs.
Looking at the transmission in Ethereal you se that for all files
FrontPage
FTP
issues a PASV command and gets a response with the protnumber to use.
(Sitting behind a NAT so I have to use PASV and the server supprots it).

When the last file is transferred it issues yet another PASV command and
gets a response with a new portnumber. BUT, here comes the strange thing,
it tries to establish a tcp-connectionj using the previous PASV response
portnumber i.e. that used when transferring the last file.

The same happens if I only uploads one file. The file is correctly
transferred but
the FrontaPage tries to establish a new data connection.

I do not understand why this last PASV command is issued as all files have
been
transferred and, furthermore, I don't understand why an old port number is
used by frontpage to set up the TCP connection.

Maybe this have been discussed earlier on this list. If so please forgive
me
for my ignorance. Please advise me if and how this problem could be
solved.

Thanks!

For those interested in the details I have appended a condesed version of
the Ethereal logs:


TYPE A
200 TYPE is now ASCII
PASV
227 Entering Passive Mode (81,228,11,138,180,63)
Passive port = 46143
STOR aktuellt.htm
150 Accepted data connection
226-459772.9 Mbytes free disk space
226-800 Kbytes used (7%) - authorized: 10240 Kb
226-File successfully transferred
226 2.417 seconds (measured here), 4.20 Kbytes per second

Data thus transferred and the passive data connection is closed but now
FrontPage FTP tries to open a new data connection:

TYPE A
200 TYPE is now ASCII
PASV
227 Entering Passive Mode (81,228,11,138,180,63)
Passive port = 38936
TCP 1927 > 46143 [SYN] Seq=0 Win=65535 Len=0 MSS=1460

I.e. Frontpage FTP tries to use the previous port in a new data connection
without
having anything to send !!!???? And of course the server terminates the
session
and FrontPage tries to login in again and does the same misstake and this
scheme
continues ad nauseum. Aborting makes FrontPage crash!!!

 

[bluegrass]

I have the exact same problem, the primary difference is that I get no file
transfered
whatsoever. I've checked the IE settings. Used Ethereal. Etc. I have no
trouble using
other ftp clients with PASV mode. It just appears the the winxp ftp client
is simply not initiating PASV mode correctly.

 

[bluegrass]

Further tests with IE show that when using ftp://user[email protected]
IE requests PASV just fine. FrontPage, however, is not invoking PASV, so I'm
wondering about all this advice I see that says, "IE has to be set to use
PASV."
Yeah? It clearly doesn't affect the behavior FP2003.

D.

 

[John Malone]

The Use Passive FTP check box may look pretty insignificant at first, but
it's a good idea to know what it does. First, a little background about FTP
connections will help.

When using FTP, there are two connections that are made. FrontPage makes the
first connection by connecting to the server. This connection is not used to
publish any files. It merely acts as a means of communication between
FrontPage and the server so that the two can send commands back and forth to
each other.

The server makes the second connection between it and FrontPage. This is the
connection that is used to actually publish files in either direction.
However, many firewalls do not like outside servers to establish that second
connection. After all, the purpose of a firewall is to protect you from
possible outside harm.

If this is the case, you may need to select the Use Passive FTP check box.
With it selected, the server will not attempt to make the second connection.
Instead, FrontPage will establish the second connection, and the publishing
process can continue from there.

Note: You may notice slower publishing performance with Passive FTP
selected.
=====================================
Did you check the box for passive in FrontPage?
In Web Site view
At the bottom select "Remote Web Site"
At the top click on "Remote Web Site Properties"
New Window
Select FTP
Make sure the "Use Passive FTP" box is checked.

HTH

--
John Malone
==============
| Further tests with IE show that when using ftp://user[email protected]
| IE requests PASV just fine. FrontPage, however, is not invoking PASV, so
I'm
| wondering about all this advice I see that says, "IE has to be set to use
| PASV."
| Yeah? It clearly doesn't affect the behavior FP2003.
|
| D.

 

[John Malone]

For more information try this...
http://office.microsoft.com/training/training.aspx?AssetID=RC010405101033

Check for wrapping of that link...
--
John Malone
==============
| The Use Passive FTP check box may look pretty insignificant at first, but
| it's a good idea to know what it does. First, a little background about
FTP
| connections will help.
|
| When using FTP, there are two connections that are made. FrontPage makes
the
| first connection by connecting to the server. This connection is not used
to
| publish any files. It merely acts as a means of communication between
| FrontPage and the server so that the two can send commands back and forth
to
| each other.
|
| The server makes the second connection between it and FrontPage. This is
the
| connection that is used to actually publish files in either direction.
| However, many firewalls do not like outside servers to establish that
second
| connection. After all, the purpose of a firewall is to protect you from
| possible outside harm.
|
| If this is the case, you may need to select the Use Passive FTP check box.
| With it selected, the server will not attempt to make the second
connection.
| Instead, FrontPage will establish the second connection, and the
publishing
| process can continue from there.
|
| Note: You may notice slower publishing performance with Passive FTP
| selected.
| =====================================
| Did you check the box for passive in FrontPage?
| In Web Site view
| At the bottom select "Remote Web Site"
| At the top click on "Remote Web Site Properties"
| New Window
| Select FTP
| Make sure the "Use Passive FTP" box is checked.
|
| HTH
|
| --
| John Malone
| ==============
| || Further tests with IE show that when using ftp://user[email protected]
|| IE requests PASV just fine. FrontPage, however, is not invoking PASV, so
| I'm
|| wondering about all this advice I see that says, "IE has to be set to use
|| PASV."
|| Yeah? It clearly doesn't affect the behavior FP2003.
||
|| D.
|
|

 

[bluegrass]

Excellent explanation of PASV mode John. I have used and understood PASV
for years, however a review is always appreciated, especially mid-way
through a thread that others will read.

I think you may have inadvertently solved the problem. My version on FP
doesn't include the options you so thoughtfully described and provided
links for.

This lead me to double check just what version of FP I have. It turns out I
have FP2002, which apparently may not support PASV mode. (Do you
have any knowledge of this?) I have gone through ALL the menu options
and I find nothing for configuring ftp.

I have read through far too many posts in forums, etc. without once coming
across the info you provided. Maybe I'm unlucky, or maybe I'm an idiot, but
before now I could find nothing that contained the info you just provided.

The further benefit may be that now I can upgrade to the latest version
of FP and know that it does, in fact, support PASV mode. I found nothing
about it in the product descriptions on the MSoft web site.

Thanks for taking the time to help a stranger. Hopefully I can pass on
the favor to someone else in the future.

Thanks,

Dustin

 

[John Malone]

Well... I had FrontPage 2002 but I have "never" used FTP.
I always published via HTTP do to the fact that FTP will break the FrontPage
extensions.
If that happens you can no longer use the HTTP and other things fail as
well... .

Sounds like you know what you are doing wish I could help more.
FrontPage 2003 has the Pasv feature but that will be the last one made.
Support will be till 2009 though.
Expression Web Design will replace FrontPage (out this fall I hope)

http://www.microsoft.com/products/expression/en/web_designer/default.mspx

Check for wrapping of the URL's

Good luck!
--
John Malone
==============
| Excellent explanation of PASV mode John. I have used and understood PASV
| for years, however a review is always appreciated, especially mid-way
| through a thread that others will read.
|
| I think you may have inadvertently solved the problem. My version on FP
| doesn't include the options you so thoughtfully described and provided
| links for.
|
| This lead me to double check just what version of FP I have. It turns out
I
| have FP2002, which apparently may not support PASV mode. (Do you
| have any knowledge of this?) I have gone through ALL the menu options
| and I find nothing for configuring ftp.
|
| I have read through far too many posts in forums, etc. without once coming
| across the info you provided. Maybe I'm unlucky, or maybe I'm an idiot,
but
| before now I could find nothing that contained the info you just provided.
|
| The further benefit may be that now I can upgrade to the latest version
| of FP and know that it does, in fact, support PASV mode. I found nothing
| about it in the product descriptions on the MSoft web site.
|
| Thanks for taking the time to help a stranger. Hopefully I can pass on
| the favor to someone else in the future.
|
| Thanks,
|
| Dustin
|
| "John Malone" wrote:
|
| > For more information try this...
| >
http://office.microsoft.com/training/training.aspx?AssetID=RC010405101033
| >
| > Check for wrapping of that link...
|

 

[Ronx]

FP2003 is the first FrontPage version to support PASV mode FTP.

 

[Bernhard]

Just to clarfy a bit more. Setting PASV mode in IE does not
affect the PASV mode for FP2003 (I have checked with
Ethereal). You have to set PASV mode option in FP2003.
The problem for me is that all files get transferred but
after this FP2003 issues yet another PASV mode FTP
command to the server who the accepts and returns
the port number to use. Then FP2003 waits for eternal
without having anything to send. No synchronization
notification is done. All files on both sides remain with
question marks.

I would prefer to use HTTP but unfortunatley I am upploading
to a web hotel server without FP support so I am forced to use FTP.

Regards,

Bernhard.
"John Malone" skrev: