Your best friend for file transfer.

Fetch application logoFetch

Fetch 4 & 5 Connection Problems vs 3.0.3 (2 posts)

  • Started 8 years ago by dmc12
  • Latest reply 8 years ago from Jim Matthews
  • dmc12 Member

    I'm having a problem connecting to any site that is outside our office using Fetch 4, 5.1 and 5.1.1 (running OSX.3.9). However Fetch 3.0.3 in OS9 running on OSX.3.9 works just fine.

    What is the cause of this problem and how can I fix it?

    Shannon

    ---------------------------------------------------
    Fetch 5.1.1 on OSX.3.9:
    -----------------
    Fetch 5.1.1 (5B388) PowerPC running on Mac OS X 10.3.9 (7W98) PowerPC English
    StuffIt Engine 0x820, StuffIt SDK Version 10.1.1b1
    Partial serial FETCH5X003-BRUJ-VMDK T

    Connecting to xxx.xxx.xxx.xxx port 21 (OS X firewall is off) (10/17/06 11:44:03 AM)
    Connected to xxx.xxx.xxx.xxx port 21 (10/17/06 11:44:03 AM)
    220 xxxxxxxxxx FTP Server v6.3...
    USER xxxxxxxxxx
    331 User name okay, need password.
    PASS
    230 User logged in, proceed.
    SYST
    215 UNIX Type: Red Hat Linux
    PWD
    257 "/" is current directory.
    MACB ENABLE
    550 Access is denied.
    PWD
    257 "/" is current directory.
    TYPE A
    200 Type set to A.
    PASV
    500 The server returned invalid response for PASV command.
    PORT xxx.xxx.xxx.xxx
    ABOR
    ftp_list: -30000 (state == GETTING_LIST)
    QUIT
    send_cmd():con_conn->Putline() returns -3208
    ---------------------------------------------------

    ---------------------------------------------------
    Fetch 5.1.1 on OSX.3.9:
    - Disabled MACB probe command
    - Unchecked "Use passive mode transfers (PASV)" box - yet it is still trying to use PASV
    -----------------
    Fetch 5.1.1 (5B388) PowerPC running on Mac OS X 10.3.9 (7W98) PowerPC English
    StuffIt Engine 0x820, StuffIt SDK Version 10.1.1b1
    Partial serial FETCH5X003-BRUJ-VMDK T
    Connecting to xxx.xxx.xxx.xxx port 21 (OS X firewall is off) (10/17/06 12:48:24 PM)
    Connected to xxx.xxx.xxx.xxx port 21 (10/17/06 12:48:24 PM)
    220 xxxxxxxxxx FTP Server v6.3...
    USER xxxxxxxxxx
    331 User name okay, need password.
    PASS
    230 User logged in, proceed.
    SYST
    215 UNIX Type: Red Hat Linux
    PWD
    257 "/" is current directory.
    PWD
    257 "/" is current directory.
    TYPE A
    200 Type set to A.
    PORT xxx.xxx.xxx.xxx
    ABOR
    ftp_list: -30028 (state == GETTING_LIST)
    ftp_list: tw->port_retries == 0, retrying file list
    Connecting to xxx.xxx.xxx.xxx port 21 (OS X firewall is off) (10/17/06 12:49:01 PM)
    Connected to xxx.xxx.xxx.xxx port 21 (10/17/06 12:49:01 PM)
    220 xxxxxxxxxx FTP Server v6.3...
    USER xxxxxxxxxx
    331 User name okay, need password.
    PASS
    230 User logged in, proceed.
    SYST
    215 UNIX Type: Red Hat Linux
    PWD
    257 "/" is current directory.
    PWD
    257 "/" is current directory.
    TYPE A
    200 Type set to A.
    PASV
    500 The server returned invalid response for PASV command.
    PORT xxx.xxx.xxx.xxx
    ABOR
    ftp_list: -30000 (state == GETTING_LIST)
    QUIT
    send_cmd():con_conn->Putline() returns -3208
    ---------------------------------------------------

    ---------------------------------------------------
    Fetch 3.0.3 in OS9 on OSX.3.9:
    -----------------
    Connecting to xxx.xxx.xxx.xxx port 21 (10/17/06 11:14:12 AM)
    220 xxxxxxxxxx FTP Server v6.3...
    USER xxxxxxxxxx
    331 User name okay, need password.
    PASS
    230 User logged in, proceed.
    SYST
    215 UNIX Type: Red Hat Linux
    PWD
    257 "/" is current directory.
    PWD
    257 "/" is current directory.
    PORT xxx.xxx.xxx.xxx
    200 PORT Command successful.
    LIST
    150 Opening ASCII mode data connection for /bin/ls.
    ---------------------------------------------------

    Posted 8 years ago #

  • Jim Matthews Administrator

    My guess is that there are two causes for this problem:

    1) Your server or perhaps the firewall between you and the server does not support passive mode. Passive mode is usually the most reliable way to make FTP connections, but because it's being blocked Fetch has to use active mode instead.

    2) Something about your computer or network setup is blocking active mode connections to Fetch 4 and 5, but not to Fetch 3. Applications that run in Classic, such as Fetch 3, have special network privileges, and that's probably why it's working.

    The transcript indicates that the OS X firewall is turned off, so I wonder whether you have a 3rd party firewall program on this Mac. It might be easier to see what's happening if the IP addresses and port numbers in the transcript weren't obscured; if you like you can email the complete transcripts to bugs at fetchsoftworks dot com.

    Thanks,

    Jim Matthews
    Fetch Softworks

    Posted 8 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.