Your best friend for file transfer.

Fetch application logoFetch

5.5.2: Says server is unreachable (33 posts)

  • Started 14 years ago by Paul Bordenkircher
  • Latest reply 11 years ago from Jim Matthews
  • Paul Bordenkircher Member

    I downloaded the new Fetch, entered my serial number, and I suddenly have what appears to be several dozen alert windows which all say: "These settings cannot be used because the server is unreachable. Check your network connection and settings..." etc."

    My settings are fine because I'm online typing this. I even did a full uninstall with App Cleaner, only leaving Fetch.Shortcuts.plist behind. Reinstalled from the .dmg file - No Change. Any suggestions?

    Posted 14 years ago #

  • Scott McGuire Administrator

    Hi Paul,

    I see you've sent messages about other problems you're experiencing to our support email address; we'll follow up with you there.

    Thanks,

    Scott McGuire
    Fetch Softworks

    Posted 14 years ago #

  • David L Good Member

    It would be nice if you resolved this problem in public, as I'm also having a problem with Fetch uploading to a server. I continue to get the error, "An FTP connection to "ftp.serevernamehere.com" could not be opened because the FTP server sent an unexpected response. Check the Fetch Transcript window for more information. Server responded: "Security mechanism not implemented."

    Here is what the Transcript window has to say:

    Connecting to ftp.servername.com port 21 (Mac OS X firewall is allowing connections) (9/14/09 7:33 AM)
    Connected to 99.99.999.99 port 21 (9/14/09 7:33 AM)
    220 Microsoft FTP Service
    ADAT
    502 'ADAT': command not implemented.
    AUTH This command is checking whether this server supports Kerberos or GSS security, see RFC 2228
    226 ADAT command successful.
    USER myusername
    504 Security mechanism not implemented.

    All the other FTP applications I have, such as Cyberduck, have no issues with this FTP site. Fetch also has no problems connecting to any bookmarked sites... only this 'new' site (which is identical to my other sites, since it's the same hosting provider).

    Thoughts?

    Posted 14 years ago #

  • Scott McGuire Administrator

    Hi David,

    We weren't deliberately withholding the resolution from the public; Paul had sent more information via email and it didn't seem to make sense to repeat the entire conversation here, that's all.

    But for the record, the most common cause of Fetch giving an error message that the server is unreachable is because the server is off-line or experiencing problems.

    As it happens, your problem is not the same as Paul's. In your case, since you're receiving a "security mechanism not implemented" error (not "server is unreachable") when trying to connect to this server, please try the following:

    * Open Fetch.
    * Go to the Fetch menu, and choose Preferences.
    * Click the Obscure tab.
    * Check the "Do not send ADAT probe command" checkbox.
    * Close the preferences.

    Then try connecting to the server in question again.

    If that doesn't fix the problem, please let us know.

    Here's what appears to be going on: Fetch sends the special ADAT command to servers to see if they support Kerberos security. Servers are supposed to return an error code if they get a command they don't support, so sending this command is normally harmless. But some servers erroneously drop the connection when they get this command, and this appears to be the case with this particular server. The reason you aren't experiencing problems with other FTP applications is they don't support Kerberos like Fetch does, and so they don't send this command to servers. (And it sounds like the rest of the servers you connect to don't have a problem with this command; you won't notice any change in behavior when connecting to them with this command off.)

    Thanks,

    Scott McGuire
    Fetch Softworks

    Posted 14 years ago #

  • David L Good Member

    Scott

    Thanks for the quick resolve. Checking the "Do not send ADAT probe command" box worked like a charm.

    Also, I'm sorry if I implied that you were "deliberately" withholding resolution from the public -- that was not my intent at all, sorry it came across like that. I just had a very specific interest in the resolution, so was a bit eager to see potential resolutions listed. I didn't realize at the time that your monitoring and replies to this forum would be so FAST. Wow. I'm very impressed (makes me glad I've been keeping up with my Fetch license all this time -- I can always appreciate supporting hard working software developers).

    David L Good

    Posted 14 years ago #

  • Scott McGuire Administrator

    Hi David,

    You're welcome, and thanks for the kind words! I'm glad to hear that fixed the problem.

    No worries - I just wanted to clarify why the resolution wasn't here in this case; in most cases we do post the answers here on the message board.

    Please let us know if we can be of assistance again in the future.

    Best,

    Scott McGuire
    Fetch Softworks

    Posted 14 years ago #

  • paceman Member

    THANK YOU GUYS FOR RESOLVING THIS IN PUBLIC ;o)

    Posted 14 years ago #

  • netman12 Member

    My version of Fetch does not have an OBSCURE tab so how am I to check "Do not send ADAT probe command" box?

    Posted 14 years ago #

  • Scott McGuire Administrator

    Hi netman12,

    Which version of Fetch do you have?

    Thanks,

    Scott McGuire
    Fetch Softworks

    Posted 14 years ago #

  • netman12 Member

    4.0.3

    Found the "Do not send ADAT probe command" box? under Misc/Options.
    Thank you for the quick response.

    Posted 14 years ago #

  • Scott McGuire Administrator

    Hi netman12,

    Okay, I'm glad you found it. So you're all set now?

    Thanks,

    Scott McGuire
    Fetch Softworks

    Posted 14 years ago #

  • mark Member

    Hi Fetch and help,

    I am getting the "server is unreachable " issue for a certain ftp. I use fetch for multiple domains but I cannot access this particular one from home. At work, using the same login info it works just fine. Any help would be greatly appreciated.

    Thanks,
    Mark

    Posted 13 years ago #

  • Scott McGuire Administrator

    Hi Mark,

    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 13 years ago #

  • damian Member

    i am getting this error also...i restarted the app and it worked, but it seems kind of intermittent now. (Fetch 5.3)

    Posted 13 years ago #

  • Scott McGuire Administrator

    Hi Damian,

    If you are getting this error intermittently - connecting to the same server sometimes works, and sometimes doesn't - then that almost certainly indicates either a problem with the server, or a problem on the network between you and the server (causing your connections to fail), because Fetch does exactly the same thing each time it tries to connect to a server. So if it sometimes works and sometimes doesn't, the problem is outside of Fetch.

    If the problem doesn't resolve itself in a day or so, you should contact the company or person who run the server to see if there are problems with the server (or a new hostname you should use for contacting the server).

    If you still have questions or problems after that, please let us know.

    Thanks,

    Scott McGuire
    Fetch Softworks

    Posted 13 years ago #

  • Keiffer Member

    Thank you for this message thread. It quickly resolved my problem.

    Posted 13 years ago #

  • Gina Member

    Hi,

    I've tried to do the suggestions listed above and I'm getting the same error messages, it keeps telling me to check the Network settings, but I checked everything and it's fine. I also checked the ADAT probe command and nothing– this only happened when I recently updated the app. I'm running on Lion, could this be the problem? I tried to access the servers with Cyberduck and it worked- but I prefer Fetch!

    Thanks,
    gina

    Posted 12 years ago #

  • Jim Matthews Administrator

    Hi Gina,

    Could you choose "Fetch Transcript" from the Window menu after you get the error and post the entire contents of that window?

    Thanks,

    Jim Matthews
    Fetch Softworks

    Posted 12 years ago #

  • Gina Member

    Sure Jim!

    Fetch 5.7.1 (5H459) Intel (Web Store) running on Mac OS X 10.7.3 (11D50b) Intel English
    StuffIt Engine 0x820, StuffIt SDK Version 10.1.1b1
    Partial serial FETCH55001-CMTT-SJAQ T

    Posted 12 years ago #

  • Jim Matthews Administrator

    Could you do that again, immediately after you try to connect and get the error? Then it should show more information.

    Thanks,

    Jim Matthews
    Fetch Softworks

    Posted 12 years ago #

  • Gina Member

    Hi Jim,

    I'm sorry this is the only thing that comes up– the problem is that I'm not even able to insert the password to the ftp- as such there is no other error message.

    Thanks,
    Gina

    Posted 12 years ago #

  • Jim Matthews Administrator

    What happens when you try to connect?

    Posted 12 years ago #

  • Gina Member
  • Gina Member

    Sorry! That didn't work, here's a direct link to the screen image: http://s79.photobucket.com/albums/j153/smartazzqt/?action=view&current=ScreenShot2012-04-16at45920PM.png

    Posted 12 years ago #

  • Jim Matthews Administrator

    Thanks for the screenshot, that's helpful.

    To get more information about the error, I'd like to see the Fetch.log file. To find Fetch.log:

    1) Run Fetch
    2) Choose "Fetch Transcript" from the Window menu
    3) Choose "Show Fetch.log in Finder" from the File menu

    You can email it to bugs@fetchsoftworks.com

    Thanks,

    Jim Matthews
    Fetch Softworks

    Posted 12 years ago #

  • Gina Member

    And trying again, this is the transcript:

    Fetch 5.7.1 (5H459) Intel (Web Store) running on Mac OS X 10.7.3 (11D50b) Intel English
    StuffIt Engine 0x820, StuffIt SDK Version 10.1.1b1
    Partial serial FETCH55001-CMTT-SJAQ
    Connecting to experientia.com port 21 (Mac OS X firewall is allowing connections) (4/16/12 5:09 PM)
    An FTP connection to “experientia.com” could not be opened because the connection was refused. (Contact the server administrator for more information.)
    Connecting to experientia.com port 21 (Mac OS X firewall is allowing connections) (4/16/12 5:09 PM)
    An FTP connection to “experientia.com” could not be opened because the connection was refused. (Contact the server administrator for more information.)

    Posted 12 years ago #

  • Jim Matthews Administrator

    It looks like the experientia.com server is refusing connection. You should contact the server administrator about that.

    Posted 12 years ago #

  • Gina Member

    I did, everyone can access it except me, and this only happened since I updated Fetch- before the update everything was working fine. I'm not sure what to do, is it possible to install the previous version again?
    Thanks!
    Gina

    Posted 12 years ago #

  • Jim Matthews Administrator

    You can download a previous version from http://fetchsoftworks.com/fetch/download .

    I should note that when I try to open an FTP connection to experientia.com the connection is immediately dropped. So it isn't just you seeing this problem.

    Jim Matthews
    Fetch Softworks

    Posted 12 years ago #

  • Mark Member

    Will this issue ever be resolved in the open? Not much good if the solutions are never posted?

    Cannot connect to server, server is unreachable, yadda yadda

    Fetch 5.3 (5D161) Intel running on Mac OS X 10.7.4 (11E53) Intel English
    StuffIt Engine 0x820, StuffIt SDK Version 10.1.1b1
    Partial serial FETCH5X001-4X8F-9CEE T
    Update check started at 05/12/2012 12:41 PM
    Update check skipped at 05/12/2012 12:42 PM (next check after 05/13/2012 05:03 AM)

    Edited 11 years ago #