Your best friend for file transfer.

Fetch application logoFetch

Return to Message Board

Subscribe to RSS Feed for Fetch Message Board Fetch Message Board

  1. Page 1

PORT command only accepts client IP address? (19 posts)

  • Started 18 years ago by Maurizio
  • Latest reply 18 years ago from Mau
  • Maurizio Member

    Folks,
    I am trying to use an ftp site to transfer data back and foward from the office. From the office I can connect to the ftp site without any problem. With the same settings, from home, I can't. The error message I get is: "Fetch could not get the file liste because theFTP server sent a unexepected response".

    here is what I found in the fetch transcript window:
    ----

    Fetch 5.0.5 (5A835) PowerPC running on Mac OS X 10.4.4 (8G32) PowerPC English
    StuffIt Engine 0x812, StuffIt SDK Version 10.0.1
    Partial serial FETCH5F002-CFQF-KDLQ T
    Connecting to 206.64.140.3 port 21 (OS X firewall is off) (2/25/06 2:12:30 PM)
    Connected to 206.64.140.3 port 21 (2/25/06 2:12:30 PM)
    220 PS FTP
    USER mpenso
    331 Password required for mpenso.
    PASS
    230 User mpenso logged in.
    SYST
    215 UNIX Type: L8
    PWD
    257 "/" is current directory.
    MACB ENABLE
    500 Unknown command.
    PWD
    257 "/" is current directory.
    TYPE A
    200 Type set to A.
    PORT 192,168,0,11,192,153
    530 PORT command only accepts client IP address (72.226.140.168!=192.168.0.11).
    PASV
    ABOR
    ftp_list: -30000 (state == GETTING_LIST)
    QUIT

    ---

    Any idea of what is going on? how can I have it working?
    Thanks you

    Mau

    Posted 18 years ago #

  • Jim Matthews Administrator

    It looks like your computer is behind a router that is not performing Network Address Translation correctly for FTP. You might try connecting your Mac directly to your DSL or cable modem (bypassing the router), or contacting the router vendor for assistance.

    [The technical details: the router is supposed to translate PORT commands, substituting your real IP address (72.226.140.168) for the one assigned by the router (192.168.0.11), but that isn't happening, so the server won't let you download the file list.]

    Thanks,

    Jim Matthews
    Fetch Softworks

    Posted 18 years ago #

  • Mau Member

    Jim,
    thank you for your replay.
    I tried connecting directly to the cable modem instead of using Airport on my Max OS X Tiger as you suggested, but the NAT issue you mentioned is still there, just the IP numbers change. Here the transcript window with the Max directly connected to the cable modem.

    ----
    Fetch 5.0.5 (5A835) PowerPC running on Mac OS X 10.4.5 (8H14) PowerPC English
    StuffIt Engine 0x812, StuffIt SDK Version 10.0.1
    Partial serial FETCH5F002-CFQF-KDLQ T
    Connecting to 206.64.140.3 port 21 (OS X firewall is off) (2/28/06 12:51:46 PM)
    Connected to 206.64.140.3 port 21 (2/28/06 12:51:46 PM)
    220 PS FTP
    USER mpenso
    331 Password required for mpenso.
    PASS
    230 User mpenso logged in.
    SYST
    215 UNIX Type: L8
    PWD
    257 "/" is current directory.
    MACB ENABLE
    500 Unknown command.
    PWD
    257 "/" is current directory.
    TYPE A
    200 Type set to A.
    PORT 192,168,0,13,192,6
    530 PORT command only accepts client IP address (72.226.140.168!=192.168.0.13).
    PASV
    ABOR
    ftp_list: -30000 (state == GETTING_LIST)
    QUIT
    send_cmd():con_conn->Putline() returns -3208

    ---

    Is there anyway to introduce a workaround, maybe using applescript, or changing the settings on the network system preferences of my Mac?
    Thanks
    Mau

    Posted 18 years ago #

  • Jim Matthews Administrator

    It looks like your Mac is still getting its Internet connection from a router. If you choose System Preferences... from the Apple menu and click the Network icon, it should show you your network status. Which interface is listed first (e.g. Built-in Ethernet, Airport, etc.)?

    Thanks,

    Jim Matthews

    Posted 18 years ago #

  • Mau Member

    Jim,
    Thanks you Here you go:

    First interface:
    Build-in Ethernet is currently active and has the IP address 192.168.0.13. You are connected to the internet via Built-in-Ethernet.

    Second:
    Airport is currently off.

    :()

    Thanks
    Mau

    Posted 18 years ago #

  • Jim Matthews Administrator

    And the ethernet wire runs from your Mac to the cable modem? If so I'd conclude that your cable modem includes a router (and that router is not compatible with active mode FTP).

    I would ask the cable company whether they offer a cable modem that does not include a router, or includes one that supports active mode FTP.

    By the way, what is the brand and model number of the cable modem?

    Thanks,

    Jim Matthews
    Fetch Softworks

    Posted 18 years ago #

  • Mau Member

    Jim,
    thank you for giving me hope. My router/cable modem is an Ambit 60740EUW. It works fine connecting to the same FTP site using a windows xp pc with Zillaftp ver. 5.0.0 in active mode... and the pc is wired to the same router.
    I'd rather not change the router to make this work. Any other suggestions?
    Thank you
    Mau

    Posted 18 years ago #

  • Jim Matthews Administrator

    Does ZillaFTP offer a transcript? I'd be interested to see what commands it's sending.

    Thanks,

    Jim Matthews
    Fetch Softworks

    Posted 18 years ago #

  • Mau Member

    Jim,
    here the ftp.log when using ZillaFTP:

    #2006-03-02 17:38:48#
    "220 PS FTP"
    #2006-03-02 17:38:48#
    "USER mpenso"
    #2006-03-02 17:38:48#
    "331 Password required for mpenso."
    #2006-03-02 17:38:48#
    "PASS xxxx"
    #2006-03-02 17:38:48#
    "230 User mpenso logged in."
    #2006-03-02 17:38:48#
    "PWD"
    #2006-03-02 17:38:48#
    "257 ""/"" is current directory."
    #2006-03-02 17:38:48#
    "TYPE A"
    #2006-03-02 17:38:48#
    "200 Type set to A."
    #2006-03-02 17:38:48#
    "PORT 192,168,0,10,4,70"
    #2006-03-02 17:38:48#
    "200 Port command successful."
    #2006-03-02 17:38:48#
    "LIST"
    #2006-03-02 17:38:48#
    "150 Opening data connection for directory list."
    #2006-03-02 17:38:48#
    "226 Transfer ok"

    does it help us?

    Thanks
    Mau

    Posted 18 years ago #

  • Jim Matthews Administrator

    Fetch is sending essentially the same commands, so I don't understand why ZillaFTP is working when Fetch isn't. My best guess is that there's some difference in their network configurations.

    If you connect to http://www.myipaddress.com from each machine, do you get the same address?

    Thanks,

    Jim Matthews
    Fetch Softworks

    Posted 18 years ago #

  • Mau Member

    Jim,
    Yes I do get the same address. It is not the IP address of my Mac or my pc or of the router...
    Anything else I could try?
    Thanks,
    Mau

    Posted 18 years ago #

  • Jim Matthews Administrator

    Could you try running Terminal, and then typing

    ftp 206.64.140.3

    Enter your username (mpenso) and password when prompted, then type

    debug

    and then

    dir

    Does that work? If so, could you post that transcript?

    Thanks,

    Jim Matthews
    Fetch Softworks

    Posted 18 years ago #

  • Mau Member

    Hello Jim,
    here is the transcript of the terminal dialog:
    --
    Last login: Fri Mar 3 13:02:45 on ttyp1
    Welcome to Darwin!
    Cheryl-Y-Computer:~ cheryly$ ftp 206.64.140.3
    Connected to 206.64.140.3.
    220 PS FTP
    Name (206.64.140.3:cheryly): mpenso
    331 Password required for mpenso.
    Password:
    230 User mpenso logged in.
    Remote system type is UNIX.
    Using binary mode to transfer files.
    ftp> debug
    Debugging on (debug=1).
    ftp> dir
    ---> EPSV
    500 Unknown command.
    disabling epsv4 for this connection
    ---> PASV

    it looks like it was going so well before typing 'dir'...
    what do think?
    Thanks,
    Mau

    Posted 18 years ago #

  • Jim Matthews Administrator

    Try typing these commands:

    debug
    passive
    dir

    (i.e. add "passive" before "dir").

    Thanks,

    Jim Matthews
    Fetch Softworks

    Posted 18 years ago #

  • Mau Member

    Jim,
    here we go again:

    Last login: Fri Mar 3 13:22:00 on console
    Welcome to Darwin!
    Cheryl-Y-Computer:~ cheryly$ ftp 206.64.140.3
    Connected to 206.64.140.3.
    220 PS FTP
    Name (206.64.140.3:cheryly): mpenso
    331 Password required for mpenso.
    Password:
    230 User mpenso logged in.
    Remote system type is UNIX.
    Using binary mode to transfer files.
    ftp> debug
    Debugging on (debug=1).
    ftp> passive
    Passive mode: off; fallback to active mode: off.
    ftp> dir
    ---> EPRT |1|192.168.0.12|49891|
    500 Unknown command.
    disabling epsv4 for this connection
    ---> PORT 192,168,0,12,194,227
    530 PORT command only accepts client IP address (72.226.140.168!=192.168.0.12).
    ---> LIST
    550 List failed. No port specified.
    ftp>

    ---

    Jim, I do not undesrtand the dialog but I noticed: no list again :()

    Thanks,
    Maurizio

    Posted 18 years ago #

  • Mau Member

    Jim,
    I tried to toggle the 'passive' command
    and I got this:
    Last login: Fri Mar 3 16:30:38 on ttyp1
    Welcome to Darwin!
    Cheryl-Y-Computer:~ cheryly ftp 206.64.140.3
    Connected to 206.64.140.3.
    220 PS FTP
    Name (206.64.140.3:cheryly): mpenso
    331 Password required for mpenso.
    Password:
    230 User mpenso logged in.
    Remote system type is UNIX.
    Using binary mode to transfer files.
    ftp> debug
    Debugging on (debug=1).
    ftp> passive
    Passive mode: off; fallback to active mode: off.
    ftp> passive
    Passive mode: on; fallback to active mode: on.
    ftp> passive
    Passive mode: off; fallback to active mode: off.
    ftp> passive
    Passive mode: on; fallback to active mode: on.
    ftp> dir
    ---> EPSV
    500 Unknown command.
    disabling epsv4 for this connection
    ---> PASV

    ---
    No progress, eh?

    Thanks,
    Mau

    Posted 18 years ago #

  • Jim Matthews Administrator

    The command line client is having the same problem as Fetch. I'm stumped as to why this problem affects your Mac and not your PC. You might ask the server administrator to allow passive mode, or SFTP; either of those would work around this problem.

    Thanks,

    Jim Matthews
    Fetch Softworks

    Posted 18 years ago #

  • Mau Member

    Jim,
    I'll try. Thanks your help
    Mau

    Posted 18 years ago #

  • Mau Member

    Jim,
    only active mode connections are allowed. I'll move, for the time being, my ftp activity to my pc. Should you come across solutions to this problem. Please post them on here. I'll keep on checking with my fingers crossed.
    Thanks,
    Mau

    Posted 18 years ago #

  1. Page 1

Return to Message Board

Reply

  • Or nickname, if you prefer.
  • This will be kept confidential.
  • This is to ensure that you’re a person, not a spambot.