Problems With Site To Site Transfer Using Fxp

Hi,

forgive me please if this has been posted before, I have searched the site for it, but as the search parameters in this case are three letter words, it did not yield any result. And yes, I also used searches with words in quotes, but those did not yield results either.

When I want to transfer files from my former website to my new one here, I can download them from there and upload them here. If I do not have a local copy that is. But just to make sure that all the revisions of PHP and HTML files are in place, I would prefer to use FXP. Which is something like "File eXchange Protocol", a subset of the FTP protocol if I am not mistaken. Basically, it transfers files directly from one site to another. All that you send and receive is the commands, but not the files themselves. Now when I do this using Flash FXP, which is a superb FTP client, I get an error message like

[02:36:31] [L] PASV[02:36:31] [L] 227 Entering Passive Mode (213,202,241,26,160,174).[02:36:32] [R] PORT 213,202,241,26,160,174[02:36:32] [R] 500 Illegal PORT command[02:36:32] Site to Site Transfer Failed! (Attempting alternative method)[02:36:33] [R] PASV[02:36:33] [R] 227 Entering Passive Mode (64,69,46,210,208,235).[02:36:34] [L] PORT 64,69,46,210,208,235[02:36:34] [L] 500 Illegal PORT command[02:36:34] Site to Site Transfer Failed![02:36:34] [R] Transfer Failed!

Now, error code 500 stand for "Syntax error, command unrecognized. This may include errors such as command line too long." If I understand if right, and please correct me if I don't, the command PORT is not recognized by the server.

My question is: Is this done deliberately in the setup of the server or is my client the problem? I know from experience, that some site ops do not permit site to site transfers because of security reasons.

This is NOT acomplaint, please don't get it wrong. No problem for me to first d/l and then u/l. I am just asking out of the curosity of a FTP veteran.
Edited November 18, 2005 by miCRoSCoPiC^eaRthLinG (see edit history)

My question is: Is this done deliberately in the setup of the server or is my client the problem? I know from experience, that some site ops do not permit site to site transfers because of security reasons.

It must be done by the server. The admin need to setup that before you can do a Site-to-site transfers. Most server doesn't support that because of security reasons (you knew it).

I don't think so - as far as I know, it can be done by a client too. Besdies you don't need any special setup to have this functioning except for:

Although FXPing is very easy, there are a few restrictions to transferring the files. Both hosts have to support PASV mode and must allow PORT commands to foreign hosts. The FXP client tells the destination FTP to listen for a connection by sending a "PASV" command. The source FTP then connects to the data port reported by the destination server (after a successful PASV command). Thus all the data goes directly from the source to the destination FTP and both servers only report status messages on fail/success to the FTP client.
Source: http://forums.xisto.com/no_longer_exists/

From what I know, it uses the basic FTP protocol to do the transfer - but with another layer of abstraction over it, not letting you see the actual files being transferred. That part of the process is fully automated. My point is, since it still uses FTP in the background, as long as both sites support PASV mode and PORT commands, it shouldn't be difficult at all.

As for Xisto, it supports both PASV and PORT - so no problems at this end.

Might be something to do with the other host you're trying to copy your files from. Find out if they support both these commands.

Regards,
m^e

FrontPage 500 Illegal Port CommandProblems With Site To Site Transfer Using Fxp

I found the fix for this error by Googling the above title but can't remember who had the correct fix.  I thank you whoever you are!

To fix this problem, change your setting on your FTP protocol to "Passive FTP" (It should be a box you have to click).  However, I had to exit the FrontPage program and restart it before it worked.  Yay!

I had been trying to update numerous HTML pages to my remote website host for several months to no avail.  At long last, I found the fix and am updated once again.

I hope this helps!

Peace to you,

Sam

THANKS OMGProblems With Site To Site Transfer Using Fxp

Yeah I had to capslock that title!(G)Sam, thanks how odd, I had to restart my CLIENT after switching to PASV to get it to work.NOTE: what I also did was change both of my servers to a non standard port, in my case 2121.One server was using pure-ftpd and I had to run with -w to enable fxpOther sever was vsftpd which had to run with pasv_promiscuous=YES

-reply by AlfaTrion