Your best friend for file transfer.

Fetch application logoFetch

Error: Server response - Can't open data connection (8 posts)

  • Started 7 years ago by rojam
  • Latest reply 7 years ago from Scott McGuire
  • rojam Member

    I'm using Fetch 4.0.3 with Mac OS X 10.4.7 on an Intel MacPro.

    I've configured a new connection to post web pages to my ISP. Fetch seems to start the connection then after a short while the above message is displayed. The detail from the Fetch log file is:
    425 Can't open data connection.
    ftp_list: -30000 (state == GETTING_LIST)

    Then main Fetch window then shows "getting file list..." followed by "connected". The error would indicate though that the connection hasn't been successful.

    When I try and send a simple html page (index.html) the same message is displayed.

    Is this simply a problem with my ISP?

    Posted 7 years ago #

  • Scott McGuire Administrator

    Hi,

    Could you please post the entire transcript? The information written there when the connection is being established may be helpful in figuring out what's going on.

    Thanks,

    Scott McGuire
    Fetch Softworks

    Posted 7 years ago #

  • rojam Member

    Hi Scott the full log is as follows:
    Fetch 4.0.3 System 0x1047 Serial FETCHFL001-FWSQ-C1Q1 TR
    Connecting to dslftp.dsl.pipex.com port 21 (9/9/06 01:40:47)
    220 Microsoft FTP Service
    ADAT
    500 'ADAT This command is checking whether this server supports Kerberos or GSS security, see RFC 2228': command not understood
    USER atnv43
    331 Password required for atnv43.
    PASS
    230 User atnv43 logged in.
    SYST
    215 Windows_NT
    PWD
    257 "/" is current directory.
    MACB ENABLE
    500 'MACB ENABLE': command not understood
    SITE DIRSTYLE
    200 MSDOS-like directory output is off
    PWD
    257 "/" is current directory.
    PWD
    257 "/" is current directory.
    PASV
    227 Entering Passive Mode (194,154,164,80,75,35).
    LIST
    425 Can't open data connection.
    ftp_list: -30000 (state == GETTING_LIST)
    PWD
    257 "/" is current directory.
    PWD
    257 "/" is current directory.
    PWD
    257 "/" is current directory.
    PWD
    257 "/" is current directory.

    [This message has been edited by rojam (edited 09-08-2006).]

    Posted 7 years ago #

  • Scott McGuire Administrator

    Hi,

    Try the following:

    * Choose Fetch > Preferences
    * Click the Misc tab
    * Click on Obscure Options
    * Choose "Send LIST -al to UNIX servers"
    * Try reconnecting

    And see if that fixes the problem.

    If that does not help, check to see if your Mac OS X firewall is on; if it is, turn it off. To do this, Go to the Mac OS X System Preferences, click the Sharing icon, click the Firewall tab, and click the Stop button if it says "Firewall On." Then try reconnecting.

    Please let us know if either of these fixes the problem.

    Thanks,

    Scott McGuire
    Fetch Softworks

    [This message has been edited by ScottMcGuire (edited 09-09-2006).]

    Posted 7 years ago #

  • mk Member

    Hi there -

    I've been running into this same problem trying to connect to a friend's FTP who hosts sites for a joint client.

    Unfortunately I can't get in using Fetch, but can via CuteFTP, which I'd rather not buy, since I already own Fetch.

    I tried your two suggestions - firewall was already off & I then selected "Send LIST -al to UNIX servers". Tried it, same error, closed and reopened fetch and still get original error.

    Any other suggestions?
    Thanks,
    ML

    Posted 7 years ago #

  • Scott McGuire Administrator

    Hi ML,

    If you could post the entire transcript from an attempt to connect to your friend's server, we'll take a look and see what else you should try.

    Thanks,

    Scott McGuire
    Fetch Softworks

    Posted 7 years ago #

  • rojam Member

    Hi Scott,
    Tried the suggestion as below. This had no affect. I had found prior to this, you other suggetion, disabling my Firewall allowed the connection to be made.

    I have to admit, I'd rather not do this. I should be able to open the specific port on the Firewall and connect, no?

    Thanks,
    Jamie.

    Originally posted by ScottMcGuire:

    Hi,

    Try the following:

    * Choose Fetch > Preferences
    * Click the Misc tab
    * Click on Obscure Options
    * Choose "Send LIST -al to UNIX servers"
    * Try reconnecting

    And see if that fixes the problem.

    If that does not help, check to see if your Mac OS X firewall is on; if it is, turn it off. To do this, Go to the Mac OS X System Preferences, click the Sharing icon, click the Firewall tab, and click the Stop button if it says "Firewall On." Then try reconnecting.

    Please let us know if either of these fixes the problem.

    Thanks,

    Scott McGuire
    Fetch Softworks

    [This message has been edited by ScottMcGuire (edited 09-09-2006).]

    Posted 7 years ago #

  • Scott McGuire Administrator

    Hi Jamie (rojam),

    Unfortunately, the way FTP works, you would have to open a whole range of ports in the firewall - while FTP uses a standard port to make the connection, it chooses from a range of ports to send the data.

    I was only suggesting that you turn off the firewall temporarily and do a quick test, just so we can tell if it's contributing to the problem or not; I believe it should be safe to turn it off for the short time it would take to make an FTP connection. You could turn it back on as soon as the test was complete, and if that appeared, we could talk about what ports need to be opened.

    However, if you want to leave that as a last resort, I'd recommend that you download and try Fetch 5.0.5 and see if that fixes the problem for you. (Our latest release is Fetch 5.1, but there is a bug on the Mac Pro that prevents it from working until Apple releases a software update.) You can download Fetch 5.0.5 from http://www.fetchsoftworks.com/downloads.html .

    Thanks,

    Scott McGuire
    Fetch Softworks

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