FXP'ing

ppolo99 · 17-01-2004, 11:06

I have found out that when i go on holiday or to a friends i can still transfer files from work to home and visa versa. I tred it from my friends house yesterday, worked great.

But toda when I woke up my mate said he still had the details of both servers in his PC so he will FXP me some more (just to test agen)

This time it was wierd, He said he got errors, here is what shown up on my Server:

(000003) 17/01/2004 12:04:30 - wF (****) > PORT 82,0,144,113,12,138
(000003) 17/01/2004 12:04:30 - wF (****) > 200 Port command successful.
(000003) 17/01/2004 12:04:30 - wF (****) > LIST
(000003) 17/01/2004 12:04:30 - wF (****) > 150 Opening data connection for directory list.
(000003) 17/01/2004 12:04:30 - wF (****) > 226 Transfer ok
(000003) 17/01/2004 12:04:42 - wF (****) > SIZE scan.txt
(000003) 17/01/2004 12:04:42 - wF (****) > 213 0
(000003) 17/01/2004 12:04:42 - wF (****) > PORT 24,91,124,222,4,118
(000003) 17/01/2004 12:04:42 - wF (****) > 200 Port command successful.
(000003) 17/01/2004 12:04:42 - wF (****) > STOR scan.txt
(000003) 17/01/2004 12:04:42 - wF (****) > asked to upload 'scan.txt' in 'F:\uploads\WrestlingFreaks\' --> Access allowed.
(000003) 17/01/2004 12:04:42 - wF (****) > 150 Opening data connection for scan.txt.
(000003) 17/01/2004 12:05:03 - wF (****) > 425 Cannot open data connection (10065).
(000003) 17/01/2004 12:05:16 - wF (****) > PORT 82,0,144,113,12,140
(000003) 17/01/2004 12:05:16 - wF (****)> 200 Port command successful.
(000003) 17/01/2004 12:05:16 - wF (****) > LIST
(000003) 17/01/2004 12:05:16 - wF (****) > 150 Opening data connection for directory list.
(000003) 17/01/2004 12:05:16 - wF (****) > 226 Transfer ok

I disabled Zone Alarm, Iv uninstalled it, iv re-installed it, and iv uninstalledit agen.

I just dont know whats wrong :s
Please help

Sociable · 17-01-2004, 11:13

Which server program are you using at home and which FXP program is he using to send and from where? (Assuming its FXP not FTP.)

Could be something simple like the way passive mode is being used (or not) but may be easier to track down the problem knowing which two programs are in use.

ppolo99 · 17-01-2004, 11:46

He is using Flash FXP With Passive Mode Off.

Im Using Bulletproof FTP Server.

Work is also using Bulletproof FTP server.

He is FXP'ing yes

Bifta · 17-01-2004, 11:49

If it's a problem solely with FXP'ing files, you could try FTP'ing down the files from work to wherever you're located then re-ftp'ing them back to where you need them, it might help isolate where the problem you're having lies.

ppolo99 · 17-01-2004, 11:50

Yeah he tryed that and it worked fine.

this is what he said he gets on his Flash FXP program:

PASV
227 Entering Passive Mode (24,91,124,222,4,134)
PORT 24,91,124,222,4,134
200 Port command successful.
STOR scan.txt
150 Opening data connection for scan.txt.
RETR scan.txt
425 Cannot open data connection (10065).
ABOR
150 Opening ASCII mode data connection for scan.txt (248 bytes).
426 Data connection closed, file transfer scan.txt aborted.
226 ABOR command successful.
Transfer Failed!
PORT 82,0,144,113,13,132
200 PORT Command successful.
LIST
150 Opening ASCII mode data connection for /bin/ls.
226 Transfer complete.
List Complete: 4 KB in 3.91 (1.24 KBps)
PORT 82,0,144,113,13,133
200 Port command successful.
LIST
150 Opening data connection for directory list.
226 Transfer ok
List Complete: 69 bytes in 0.05 (0.07 KBps)
Transfer queue completed
1 File failed to transfer

Bifta · 17-01-2004, 11:57

Quote:

Originally Posted by ppolo99

Yeah he tryed that and it worked fine.

this is what he said he gets on his Flash FXP program:

PASV
227 Entering Passive Mode (24,91,124,222,4,134)
PORT 24,91,124,222,4,134
200 Port command successful.
STOR scan.txt
150 Opening data connection for scan.txt.
RETR scan.txt
425 Cannot open data connection (10065).
ABOR
150 Opening ASCII mode data connection for scan.txt (248 bytes).
426 Data connection closed, file transfer scan.txt aborted.
226 ABOR command successful.
Transfer Failed!
PORT 82,0,144,113,13,132
200 PORT Command successful.
LIST
150 Opening ASCII mode data connection for /bin/ls.
226 Transfer complete.
List Complete: 4 KB in 3.91 (1.24 KBps)
PORT 82,0,144,113,13,133
200 Port command successful.
LIST
150 Opening data connection for directory list.
226 Transfer ok
List Complete: 69 bytes in 0.05 (0.07 KBps)
Transfer queue completed
1 File failed to transfer

Sorry, I'm probably being daft, you said he's got passive mode off, but the log here suggests he hasn't.

ppolo99 · 17-01-2004, 12:01

I know, but he shown me screen shot to prove it

Frank · 17-01-2004, 12:04

Have you got port bouncing turned on on both servers?

ppolo99 · 17-01-2004, 12:06

I have Block Port-to-Port FXP Turned off.

It was all working yesterday, nothing has been changed

Sociable · 17-01-2004, 12:20

I think you may have your answer ppolo99

It could be simply that what was working was FTP from your mate but not FXP.

FXP has always been a little more tempremental with specific combinations of server and Sever/FTP/FXP programs so what works perfectly from one location wont work from another and even from same locations on a day to day basis. (With FXP the combinations increase as three parties are involved not just two)

Usually you can find a work-around by changing one of the ingredients.

Also, as Keyser points out, you will find that some settings in your server will allow FTP but block FXP so double check all of them are set corectly too, including any permissions based on IP just in case that is an issue too. I have even found changing the specific port for your server can make a difference but have no idea why that could be.

**Paul** · 17-01-2004, 12:29

Quote:

Originally Posted by Sociable

I think you may have your answer ppolo99

It could be simply that what was working was FTP from your mate but not FXP.

FXP has always been a little more tempremental with specific combinations of server and Sever/FTP/FXP programs so what works perfectly from one location wont work from another and even from same locations on a day to day basis. (With FXP the combinations increase as three parties are involved not just two)

Usually you can find a work-around by changing one of the ingredients.

Also, as Keyser points out, you will find that some settings in your server will allow FTP but block FXP so double check all of them are set corectly too, including any permissions based on IP just in case that is an issue too. I have even found changing the specific port for your server can make a difference but have no idea why that could be.

Error 10065 is a "No route to host" error, which can under some circumstances be caused by the remote host appearing to be down (which could be the port chosen being blocked at the said host).

Sociable · 17-01-2004, 12:35

Quote:

Originally Posted by pem

Error 10065 is a "No route to host" error, which can under some circumstances be caused by the remote host appearing to be down (which could be the port chosen being blocked at the said host).

Ahh that could be down to a system admin at work having noticed unusual traffic and blocked a port or banned an IP then.

ppolo99 · 17-01-2004, 12:52

Quote:

Originally Posted by Sociable

Ahh that could be down to a system admin at work having noticed unusual traffic and blocked a port or banned an IP then.

Iv Tryed FXP'ing to myself, No luck. Iv tryed from other FXP enabled Servers. Its 100% My end. But i tryed Serv-U and same errors

iv reset cable modem and PC a few times.

ppolo99 · 17-01-2004, 12:57

I installed Windows Xp SP1 last night, dya think thats the culprit?

Sociable · 17-01-2004, 13:21

Shouldn't be as I run G6 without any problems at all on XP pro with SP1 and all updates installed.

That said could make sense to re-install your server just in case anything has been changed by the install of SP1.

Maybe also see if you can grab a trial version of G6 as changing server client may help.

If I can find a link later will post back OK.

EDIT: http://international.tucows.com/prev...-001-007C.html