FTP PORT command binds to localhost?



Hi,

Does anyone know why FTP.EXE in the windows command prompt is binding to
127.0.0.1 when issuing a PORT command on a remote FTP server on the Internet?
the FTP client doesn't support passive transfers so I need active FTP to
work. I can get it to work by using "ftp -a ftp.ftpserver.com" but I'd really
want to know why I suddenly need the "-a" switch.

When using my FTP client in Total Commander I can se in the log that it's
binding to my actual IP address and everything works fine...

Example1 using FTP.EXE without the -a switch:

"D:\Downloads>ftp -d ftp.sunet.se
Connected to ftp.sunet.se.
220 Welcome to ftp.sunet.se
User (ftp.sunet.se:(none)):
---> USER
331 Any password will work
Password:
---> PASS
230 Any password will work
ftp> ls
---> PORT 127,0,0,1,5,21
200 PORT command successful
---> NLST
150 Connecting to port 16716"

....and then nothing happens!

Example 2 using the FTP.EXE with the "-a" switch:

"D:\Downloads>ftp -d -a ftp.sunet.se
Connected to ftp.sunet.se.
220 Welcome to ftp.sunet.se
User (ftp.sunet.se:(none)):
---> USER
331 Any password will work
Password:
---> PASS
230 Any password will work
ftp> ls
---> PORT 0,0,0,0,5,207
200 PORT command successful
---> NLST
150 Connecting to port 16722
bin
dev
etc
lib
ls-lR
ls-lR.gz
pub
usr
226 8 matches total
ftp: 47 bytes received in 0,00Seconds 47000,00Kbytes/sec.
ftp>"

...this one works but it seems to bind to IP 0.0.0.0 .

Example 3 using TotalCommander FTP client:

"Connect to: (2006-05-10 19:23:39)
hostname=ftp.sunet.se
username=anonymous
startdir=
ftp.sunet.se=194.71.11.70
220 Welcome to ftp.sunet.se
USER anonymous
331 Any password will work
PASS ***********
230 Any password will work
SYST
215 UNIX Type: L8
FEAT
211-Extensions supported:
EPRT
IDLE
MDTM
SIZE
REST STREAM
MLST type*;size*;sizd*;modify*;UNIX.mode*;UNIX.uid*;UNIX.gid*;unique*;
MLSD
TVFS
ESTP
PASV
EPSV
SPSV
ESTA
211 End.
Connect ok!
PWD
257 "/" is your current location
Get directory
TYPE A
200 TYPE is now ASCII
PORT 192,168,5,160,6,13
200 PORT command successful
LIST
150 Connecting to port 16732
Download
Waiting for server...
226-Options: -l
226 8 matches total"

Binding to my correct LAN IP address.

Is there any recently released windows security patch that causes this
behaviour of the FTP.EXE client ?

Thanks in advance for any input what so ever.


.



Relevant Pages

  • [NEWS] Symantec Enterprise Firewall FTP Bounce Vulnerability (Patch Available)
    ... The following security advisory is sent to the securiteam mailing list, and can be found at the SecuriTeam web site: http://www.securiteam.com ... Raptor Firewall FTP Bounce Vulnerability. ... PORT command referenced a destination that doesn't ...
    (Securiteam)
  • Re: FTP on IIS6.0 Not Working
    ... > 220 Microsoft FTP Service ... > 331 Password required for username. ... > 200 PORT command successful. ... > 150 Opening ASCII mode data connection for /bin/ls. ...
    (microsoft.public.inetserver.iis.ftp)
  • Re: FTP error using a MAC
    ... If we switch to active mode then the port command fails as the IP address issued is the local IP associated with the miniMac running behind a firewall, the same firewall as the windows PC; ... attempting to FTP to a Microsoft Windows 2003 FTP Server ...
    (microsoft.public.inetserver.iis.ftp)
  • Re: Mainframe FTP
    ... Subject: Mainframe FTP ... 331 Password required for mainframe. ... 200 PORT command successful. ... For IBM-MAIN subscribe / signoff / archive access instructions, ...
    (bit.listserv.ibm-main)
  • Re: Extremely abnormal behaviour: ftp client does show a file list in a folder occasionally
    ... from ftp client and its folder auto searching. ... 250 CWD command successful. ... connecting to xxx.xxx.xx.xx:21 ... 227 Entering Passive Mode. ...
    (microsoft.public.inetserver.iis.ftp)