Your best friend for file transfer.

Fetch application logoFetch

file list not appearing (8 posts)

  • Started 6 years ago by nspo
  • Latest reply 4 years ago from Scott McGuire
  • nspo Member

    I'm using Fetch 4.0.3 with MacOS 10.5.5

    Used it for years w/ no problem, suddenly it connects but won't do anything else. I haven't changed anything that I'm aware of...

    Have tried complete re-boot.

    Have tried toggling both PASV's that I could find.

    Classicftp suffers the same symptoms as Fetch.

    Server (members.cox.net) will ftp back & forth-- but only does one file at a time...

    Interarchy also works, but it's not as easy as Fetch (worse, it's $60).

    System Preferences panels for Sharing and Network don't tell me much, and I don't understand them anyway. I'm just a simple caveman; connectivity issues confuse & frighten me.

    Here's about all I can tell you:

    Connecting to members.cox.net port 21 (9/25/08 9:24:59 PM)
    220 68.99.123.140 FTP server ready
    USER papiotom
    331 Password required for papiotom.
    PASS
    230 User papiotom logged in.
    SYST
    215 UNIX Type: L8
    PWD
    257 "/" is current directory.
    MACB ENABLE
    500 MACB not understood
    PWD
    257 "/" is current directory.
    PASV
    227 Entering Passive Mode (68,99,123,140,4,103).
    LIST
    421 No Transfer Timeout (300 seconds): closing control connection.
    ftp_list: -30001 (state == GETTING_LIST)
    QUIT
    send_cmd():con_conn->Putline() returns -3155

    Hoping it's a simple fix; I love Fetch!
    Tom

    Posted 6 years ago #

  • Scott McGuire Administrator

    Hi Tom,

    It looks like Cox's servers are having problems with passive mode connections. I was able to duplicate your problem.

    However, turning off passive mode allowed me to connect to a Cox server successfully; so I think you should try that again. Here are instructions:

    * Open Fetch.
    * Click Cancel in the New Connection dialog that appears when Fetch starts.
    * Go to the Fetch menu, and choose Preferences.
    * Click the Firewall tab.
    * Make sure the "Use passive mode transfers (PASV)" checkbox is unchecked.
    * Click the OK button.
    * Try connecting to your server again.

    This worked for me using Fetch 4.0.3 connecting to members.cox.net.

    Please let us know if it works for you or not.

    Thanks,

    Scott McGuire
    Fetch Softworks

    Posted 6 years ago #

  • nspo Member

    I axed for a simple fix? I guess I didn't juggle my PASV's correctly, earlier. I am almost instantly happy.

    Did I mention I love Fetch? Now I have to add Support to my list of Why. Thank you very much!

    Posted 6 years ago #

  • Scott McGuire Administrator

    Hi,

    You're welcome, and I'm glad to hear that worked for you. And thanks for the kind words!

    Best,

    Scott McGuire
    Fetch Softworks

    Posted 6 years ago #

  • mojord Member

    I have the same problem EXCEPT, toggling does not work. Please advise. The only CHANGE in my system is the new AIRPORT EXTREME (802.11n). Here is the FETCH SCRIPT>
    Please advise... and THANKS!!

    Fetch 5.3 (5D161) PowerPC running on Mac OS X 10.4.11 (8S165) PowerPC English
    StuffIt Engine 0x820, StuffIt SDK Version 10.1.1b1
    Partial serial FETCH5X001-CATH-LQZ9 T
    Connecting to nynoise.com port 21 (Mac OS X firewall is on) (11/15/08 10:07:21 AM)
    Connected to 64.148.130.30 port 21 (11/15/08 10:07:21 AM)
    220 ProFTPD 1.3.1 Server (64.148.130.30) [64.148.130.30]
    USER nynoise
    331 Password required for nynoise
    PASS
    230 User nynoise logged in
    SYST
    215 UNIX Type: L8
    PWD
    257 "/" is the current directory
    MACB ENABLE
    500 MACB not understood
    CWD /nynoise.com/nyn_Clients
    250 CWD command successful
    PWD
    257 "/nynoise.com/nyn_Clients" is the current directory
    TYPE A
    200 Type set to A
    PORT 10,0,1,11,194,20
    200 PORT command successful
    LIST -al
    Active mode connection blocked by Mac OS X firewall, port 49684
    ABOR
    ftp_list: 2,-30030 (state == GETTING_LIST)
    ftp_list: tw->port_retries == 0, retrying file list
    Connecting to nynoise.com port 21 (Mac OS X firewall is on) (11/15/08 10:07:58 AM)
    Connected to 64.148.130.30 port 21 (11/15/08 10:07:58 AM)
    220 ProFTPD 1.3.1 Server (64.148.130.30) [64.148.130.30]
    USER nynoise
    331 Password required for nynoise
    PASS
    230 User nynoise logged in
    SYST
    215 UNIX Type: L8
    PWD
    257 "/" is the current directory
    MACB ENABLE
    500 MACB not understood
    CWD /nynoise.com/nyn_Clients
    250 CWD command successful
    PWD
    257 "/nynoise.com/nyn_Clients" is the current directory
    TYPE A
    200 Type set to A
    PASV
    227 Entering Passive Mode (64,148,130,30,226,147).
    Making data connection to 64.148.130.30 port 58003
    ABOR
    226 Abort successful
    PORT 10,0,1,11,194,24
    200 PORT command successful
    LIST -al
    Active mode connection blocked by Mac OS X firewall, port 49688
    ABOR
    ftp_list: 2,-30031 (state == GETTING_LIST)
    QUIT
    send_cmd():con_conn->Putline() returns 2,32767
    Update check skipped at 11/15/2008 10:09 AM (next check after 11/16/2008 09:23 PM)

    Posted 6 years ago #

  • Scott McGuire Administrator

    Hi mojord,

    Sorry for the delay in replying.

    There are two different "modes" for connecting to FTP servers - "passive" and "active" mode connections. Fetch supports both of these. Passive is recommended, because it is the only mode that works when you have the Mac OS X firewall turned on. Active mode connections will not work while the firewall is on.

    If one mode fails, Fetch automatically tries the other. According to the transcript you sent, Fetch is trying active mode first, and it fails, because you have your Mac OS X firewall enabled. Then Fetch tries passive mode too, and it also fails. Usually passive mode fails because the server does not support it, or because the server is behind its own firewall. A new Airport Extreme base station should not cause passive modes to fail; we know from experience that passive mode connections do work with them.

    So I am not sure why the Airport Extreme would suddenly cause passive mode to fail, but we will investigate.

    To begin, could you try using Fetch to connect to ftp.fetchsoftworks.com ? (Leave the username and password blank, they are not required.) Let us know if you can connect successfully to it or not.

    Thanks,

    Scott McGuire
    Fetch Softworks

    Posted 6 years ago #

  • daloveboat Member

    I am having issues with my new Aiport Extreme Base Station connecting through Fetch 4.03 to my FTP.
    It worked wonderfully with my old Airport Express unit. And it does connect if I hook up the
    ethernet cable directly. There must be a setting needing to be changed in either my Fetch Firewall Preferences or My Airport Extreme Setup. I already tried the method mentioned above in a solution to an earlier post.
    This one below.

    "However, turning off passive mode allowed me to connect to a Cox server successfully; so I think you should try that again. Here are instructions:

    * Open Fetch.
    * Click Cancel in the New Connection dialog that appears when Fetch starts.
    * Go to the Fetch menu, and choose Preferences.
    * Click the Firewall tab.
    * Make sure the "Use passive mode transfers (PASV)" checkbox is unchecked.
    * Click the OK button.
    * Try connecting to your server again."

    But no luck.

    Thank you

    Posted 4 years ago #

  • Scott McGuire Administrator

    Hi Daloveboat,

    Could you please do the following?

    * Quit Fetch.
    * Open Fetch again.
    * Try connecting to your server.
    * After you receive the error, go to the Window menu, and choose Fetch Transcript.
    * Copy the entire contents of the transcript window, and paste them into a reply to this message.

    We'll take a look and see if we can advise.

    Thanks,

    Scott McGuire
    Fetch Softworks

    Posted 4 years ago #

Reply

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