Link to home
Start Free TrialLog in
Avatar of vlachosg
vlachosg

asked on

FTP over vpn points

Trying to transfer a file through ftp from one VPN point A to VPN point B.

ftp
open ip-for-point-A
ftp> put c:\posdata\002\FORHTA02.TXT forhta
501 IP Address for data destination doesn't match client's.
425      No data connection
: The type of socket is not supported in this protocol family.

the operating system from on point a is IBM AIX and the one in point b is WINDOWS XP.

any ideas?

Avatar of lucius_the
lucius_the
Flag of Croatia image

Before the transfer, try to switch to FTP passive mode. The command issued before the transfer is PASV.
Hm hm... The biult in Windows FTP client doesn't seem to support passive mode FTP. Try using Total Commander (http://www.ghisler.com/download.htm) or some other program.
Avatar of dfke
dfke

Is the Windows XP in a Vmware environment? If so change network type from nat to brigde mode.  If using FTP from a machine which doesn't have a correct IP address such as private network, try setting up the IP address correctly.
Avatar of vlachosg

ASKER

It is a real Windows XP not a virtual machine.

trying passive

ftp> quote pasv
227 Entering Passive Mode (192,168,11,1,131,196)
ftp> put c:\posdata\002\forhta02.txt forhta

...never ended


trying total commander it transfered the file.

The problem is that I have scrips already running from the command line that will need the native ftp windows client to work. Otherwise I ll need to find a way of running totalcommander's ftp from the command line?

Any ideas?

Yes, use anohter command line client - I used ftps.exe, gimme a moment to find the link...
ASKER CERTIFIED SOLUTION
Avatar of lucius_the
lucius_the
Flag of Croatia image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
so just out of curiosity why isn't it working with the freaking native win xp ftp client?
I don't know actually. I've read that windows FTP client doesn't work well on passive mode transfers, and never really digged :)

FTP is an old protocol. It was designed to be used in early Internet, when all computers on the network had a fixed (public) IP address and there were no firewalls - all ports were accessible. Then, with time, firewall started to block ports, and things like NAT devices were invented, so that more computers in LAN could share a single public IP address. That's when the default (active) FTP stopped working and passive FTP was the way around - it enables client devices to connect to FTP server when opening data links and not the other way around which is the case with active FTP - since that won't work behind firewalls and NAT devices.

But, as FTP is probably as old as Internet, and there are other, better ways of transfering files... I guess nobody at Microsoft bothered to support this more than "declaratively". And so we have a partially working client built in, one that works in LAN, but doesn't work well in other situations ;)