Your best friend for file transfer.

Fetch application logoFetch

can't connect with new 5.5 (20 posts)

  • Started 4 years ago by Michael Brochin
  • Latest reply 4 years ago from Scott McGuire
  • Michael Brochin Member

    Hello,
    Just bought Fetch 5.5. When I try to connect it appears to start the process, but doesn't get files. Then spinning wheel of death goes on and program quits and I get a non-response. Can't get past that. Please advise!!

    Posted 4 years ago #

  • Scott McGuire Administrator

    Hi Michael,

    We're sorry you're having troubles with the new version of Fetch.

    Could you try restarting your Macintosh, and then try connecting again, and see if that fixes the problem?

    If it does not, please let me know which version of Mac OS X you're using, and we'll gather more information about the problem.

    Thanks,

    Scott McGuire
    Fetch Softworks

    Posted 4 years ago #

  • Boyd Shermis Member

    I'm ditto'ing what Michael Brochin wrote above.

    "Hello,
    Just bought Fetch 5.5. When I try to connect it appears to start the process, but doesn't get files. Then spinning wheel of death goes on and program quits and I get a non-response. Can't get past that. Please advise!! "

    I did try rebooting - several times - no difference. Fortunately I have Filezilla installed. I can connect and d/l, u/l with that, so I know it's not my connection. This is the same on 2 newly updated & licensed Fetch installations...

    System Version: Mac OS X 10.5.7 (9J61)
    Kernel Version: Darwin 9.7.0

    Boyd Shermis

    Posted 4 years ago #

  • Michael Brochin Member

    Hey,

    Just posting that the restarting did the trick for me personally...

    Michael Brochin

    Posted 4 years ago #

  • Scott McGuire Administrator

    Hi Boyd,

    Could you please send an email to us at:

    bugs at fetchsoftworks dot com

    with the same description of the problem you posted here?

    We should be able to help fix the problem.

    Thanks,

    Scott McGuire
    Fetch Softworks

    P.S. Michael, we're glad to hear the problem is fixed for you!

    Edited 4 years ago #

  • DVenolia Member

    Hi Scott,
    I Have been trying to upload my files and I am getting the following message:
    "Fetch could not get the file list because there was a timeout trying to establish a passive mode data connection.
    A server firewall might be blocking passive mode (PASV) transfers. Please ask the server administrator for help."

    I restarted my Macintosh, and then try connecting again, as you suggested for Michael and did not fixed the problem. I also contacted Godaddy, my server administrator, and they said that it is everything how was supposed to be.

    My Mac OS X version is 10.4.11.
    Can you help me fix this problem, please?

    Thank you,

    DVenolia

    Posted 4 years ago #

  • Scott McGuire Administrator

    Hi DVenolia,

    We'd like some more information to help diagnose the problem. 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 figure out what's going on.

    Thanks,

    Scott McGuire
    Fetch Softworks

    Posted 4 years ago #

  • DVenolia Member

    Hi Scott,
    Here what you requested. Good luck!
    Fetch 5.5 (5E596) PowerPC running on Mac OS X 10.4.11 (8S165) PowerPC English
    StuffIt Engine 0x820, StuffIt SDK Version 10.1.1b1
    Partial serial FETCH55001-S3MH-G4G2 T
    Connecting to casadearte.org port 21 (Mac OS X firewall is off) (6/11/09 11:10 AM)
    Connected to 208.109.181.144 port 21 (6/11/09 11:10 AM)
    220 Microsoft FTP Service
    USER dv22461463
    331 Password required for dv22461463.
    PASS
    230 User dv22461463 logged in.
    SYST
    215 Windows_NT
    PWD
    257 "/dv22461463" is current directory.
    MACB ENABLE
    500 'MACB ENABLE': command not understood
    PWD
    257 "/dv22461463" is current directory.
    TYPE A
    200 Type set to A.
    PORT 192,168,1,101,192,137
    ABOR
    get_reply():con_conn->Getline() returns 1,54
    ftp_list: 2,-30028 (state == GETTING_LIST)
    ftp_list: tw->port_retries == 0, retrying file list
    Connecting to casadearte.org port 21 (Mac OS X firewall is off) (6/11/09 11:10 AM)
    Connected to 208.109.181.144 port 21 (6/11/09 11:10 AM)
    220 Microsoft FTP Service
    USER dv22461463
    331 Password required for dv22461463.
    PASS
    230 User dv22461463 logged in.
    SYST
    215 Windows_NT
    PWD
    257 "/dv22461463" is current directory.
    MACB ENABLE
    500 'MACB ENABLE': command not understood
    PWD
    257 "/dv22461463" is current directory.
    TYPE A
    200 Type set to A.
    PASV
    227 Entering Passive Mode (208,109,181,144,13,222).
    Making data connection to 208.109.181.144 port 3550
    ABOR
    225 ABOR command successful.
    PORT 192,168,1,101,192,140
    ABOR
    get_reply():con_conn->Getline() returns 1,54
    ftp_list: 2,-30037 (state == GETTING_LIST)
    ftp_list: tw->pasv_retries == 0, retrying file list
    Connecting to casadearte.org port 21 (Mac OS X firewall is off) (6/11/09 11:11 AM)
    Connected to 208.109.181.144 port 21 (6/11/09 11:11 AM)
    220 Microsoft FTP Service
    USER dv22461463
    331 Password required for dv22461463.
    PASS
    230 User dv22461463 logged in.
    SYST
    215 Windows_NT
    PWD
    257 "/dv22461463" is current directory.
    MACB ENABLE
    500 'MACB ENABLE': command not understood
    PWD
    257 "/dv22461463" is current directory.
    TYPE A
    200 Type set to A.
    PASV
    227 Entering Passive Mode (208,109,181,144,14,1).
    Making data connection to 208.109.181.144 port 3585
    ABOR
    225 ABOR command successful.
    PORT 192,168,1,101,192,143
    ABOR
    get_reply():con_conn->Getline() returns 1,54
    ftp_list: 2,-30037 (state == GETTING_LIST)
    Update check skipped at 6/11/09 11:12 AM (next check after 6/11/09 3:50 PM)

    Posted 4 years ago #

  • Scott McGuire Administrator

    Hi DVenolia,

    Thanks for the transcript.

    Could you please try connecting to ftp.fetchsoftworks.com (leave the username and password blank, they are not required), and tell us if you can connect successfully to it?

    Thanks,

    Scott McGuire
    Fetch Softworks

    Posted 4 years ago #

  • DVenolia Member

    Hi Scott,
    When I typed ftp.fetchsoftworks.com I went to: Index of ftp://ftp.fetchsoftworks.com/

    Up to higher level directory
    Name Size Last Modified
    File:Fetch_4.0.3.sit 1313 KB 3/3/06 12:00:00 AM
    File:Fetch_5.0.5.dmg 3695 KB 1/2/06 12:00:00 AM
    File:Fetch_5.5.dmg 17649 KB 6/2/09 3:57:00 PM
    File:Fetch_5.5_Help.pdf 3899 KB 6/2/09 3:57:00 PM
    example 4/15/09 9:25:00 PM
    incoming 6/11/09 12:35:00 AM

    What else should I do?
    Thank you
    DVenolia

    Edited 4 years ago #

  • Scott McGuire Administrator

    Hi DVenolia,

    The fact that you can connect to ftp.fetchsoftworks.com successfully suggests the problem may be with the server, despite what GoDaddy says.

    However, the next thing I would suggest is restarting your router (the device which lets you share your Internet connection between multiple computers) and/or cable/DSL modem, to see if that helps. (This assumes you have access to that equipment.) We find that sometimes solves problems like yours.

    Follow these exact steps in this order:

    * Shut down your Mac.
    * Unplug your router or wireless base station.
    * Unplug your cable/DSL modem.
    * Plug the cable/DSL modem back in, and wait about a minute for it to get completely started up.
    * Then plug the router or wireless base station back in, and wait another minute for it.
    * Finally, start your Mac.

    Then try connecting and uploading to the problem server. Let us know how it goes.

    Thanks,

    Scott McGuire
    Fetch Softworks

    Posted 4 years ago #

  • Scott McGuire Administrator

    Hi,

    Actually, I meant connect to ftp.fetchsoftworks.com using Fetch, not your web browser. However, please try the steps above to restart everything, and we can come back to ftp.fetchsoftworks.com.

    Thanks,

    Scott McGuire
    Fetch Softworks

    Posted 4 years ago #

  • DVenolia Member

    Hi Scott,
    I did what you suggest about unplug everything but before I tried again to connect using Fetch a I get a different message asking to select a "use passive mode transfers (PASV) under general preferences. So I have my problem fixed but I can not tell you what solved the problem. You might try select this box with another user next time that someone comes with a problem similar with mine, just a suggestion.
    Thank you very much for all your help.
    DVenolia

    Posted 4 years ago #

  • Scott McGuire Administrator

    Hi DVenolia,

    The reason I didn't suggest changing the passive preference in your case is that from your transcript, I was pretty sure it wouldn't fix the problem. I think restarting everything is probably the thing that fixed it.

    But regardless, glad to hear your problem is fixed!

    Best,

    Scott McGuire
    Fetch Softworks

    Posted 4 years ago #

  • Rebecca Member

    I'm looking for further help with this problem!

    I, too, have been having trouble with MACB ENABLE and passive mode and connecting with Fetch. My connection is successful, then MACB ENABLE is sent and the connection kicks into passive mode and I cannot see my folders/files. (transcript below) As suggested previously, I have shut down my computer, and turned off my DSL modem-router and unplugged the modem; waited about a minute; turned the modem fully on; then restarted my computer--without an success in my ftp connection.

    I'm trying to connect to an asp server. I know that I need to connect in active mode (PASV/passive mode turned off), and that firewalls can cause problems. I've turned firewalls off (computer and DLS modem) to reduce potential problems. I have also turned off PASV both in Fetch and in Network in my System Preferences.

    How do I turn off MACB ENABLE communication (which seems to be changing the connection to passive mode and therefore causing my problems)? Any other suggestions?

    Fetch Server Transcript:
    Fetch 5.5 (5E596) Intel running on Mac OS X 10.5.7 (9J61) Intel English
    StuffIt Engine 0x820, StuffIt SDK Version 10.1.1b1
    Partial serial FETCHEX001-689N-5NDR T
    Connecting to 209.35.118.97 port 21 (Mac OS X firewall is allowing connections) (6/24/09 6:55 PM)
    Connected to 209.35.118.97 port 21 (6/24/09 6:55 PM)
    220 Microsoft FTP Service
    USER chaosdesign
    331 Password required for chaosdesign.
    PASS
    230 User chaosdesign logged in.
    SYST
    215 Windows_NT
    PWD
    257 "/" is current directory.
    MACB ENABLE
    500 'MACB ENABLE': command not understood
    PWD
    257 "/" is current directory.
    TYPE A
    200 Type set to A.
    PORT 172,16,1,2,192,1
    500 Invalid PORT Command.
    PASV
    227 Entering Passive Mode (209,35,118,97,19,33).
    Making data connection to 209.35.118.97 port 4897
    ftp_setup_dataconn() passive mode dataconn failed, result = 1,61
    ftp_list: 2,-30000 (state == GETTING_LIST)
    PWD
    257 "/" is current directory.
    PWD
    257 "/" is current directory.
    Update check skipped at 6/24/09 6:57 PM (next check after 6/25/09 1:49 AM)

    Posted 4 years ago #

  • Scott McGuire Administrator

    Hi Rebecca,

    Thanks for including the transcript with your question.

    Actually, I don't think the MACB ENABLE command is causing Fetch to switch to passive mode; from the transcript it looks like it's the PORT command. The PORT command is what tells the server to use active mode, but the server is saying it doesn't like the PORT command that got sent ("500 Invalid PORT Command"). Since the command to use active failed, Fetch switches to trying passive.

    The question is why the PORT command is failing.

    While I don't think this will change things, you can stop Fetch from sending the MACB command, and we'll see if it helps. Here's what to do:

    * Close any open connections in Fetch.
    * Open the Fetch Preferences.
    * Click the Obscure tab.
    * Check the "Do not send MACB probe" checkbox.
    * Try connecting again.

    Let us know what happens, and if you still can't connect, please send another transcript.

    Thanks,

    Scott McGuire
    Fetch Softworks

    Posted 4 years ago #

  • Rebecca Member

    Thanks! I have disabled MACB and it no longer appears on the transcript. The PORT command is still a problem. Do you have any suggestions for addressing this?

    Posted 4 years ago #

  • Scott McGuire Administrator

    Hi Rebecca,

    A couple of questions for you.

    Have you ever been able to connect to this server successfully in the past, using the same computer in the same location (that is, same network) as you are now?

    Can you connect to other servers successfully?

    Thanks,

    Scott McGuire
    Fetch Softworks

    Posted 4 years ago #

  • Rebecca Member

    I have been able to connect to this server (asp server) in the past, but not on the same computer. It was from an older Mac (which died recently), so now I have a new iMac. Same location, but I'm using a new company for DSL connection. In the past, it was only PASV and firewalls that prevented connection/viewing files. (Actually, it seems to connect now, I just can't see my folders and files.)

    I can connect to other servers successfully--particularly a Linux server (Dreamhost).

    Thanks, reb :)___

    Posted 4 years ago #

  • Scott McGuire Administrator

    Hi Rebecca,

    Thanks for that information. Unfortunately - based on the transcript and other information you've provided - we think the problem is being caused by your new DSL company's network or the network equipment. There's no other reason we can think of for the connection to be failing like it is, and there are no settings in Fetch that can work around the problem.

    You could try asking if the server supports SFTP connections, which might work when FTP does not (Fetch supports SFTP connections); unfortunately, many servers do not support SFTP.

    Otherwise, you should check with the DSL company to see if you can get updated or different hardware, and see if that fixes the problem.

    Sorry that we don't have a better answer for you.

    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.