Your best friend for file transfer.

Fetch application logoFetch

FTP could not be opened because the FTP server dropped the connection (39 posts)

  • Started 5 years ago by jlseattle
  • Latest reply 3 years ago from Scott McGuire
  • jlseattle Member

    FTP could not be opened because the FTP server dropped the connection.

    Hi, I'm having the above issue when connecting to my work's ftp site. I don't have this problem with any other site except this one. I have figured out the culprit but can't fix it. I have the new dual band AEBS and when I try to connect through that it gives me the error. When I disconnect the AEBS and plug directly into the cable modem via ethernet it works fine. Anyone have any idea what could cause this?? I think it has something to do with port mapping settings on the AEBS.

    Posted 5 years ago #

  • Scott McGuire Administrator

    Hi,

    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 the problem 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 5 years ago #

  • thoroughlycurly Member

    I am having this same problem. I can connect with other sites but not with one. The transcript:

    Fetch 5.2 (5C121) Intel running on Mac OS X 10.4.9 (8S2167) Intel English
    StuffIt Engine 0x820, StuffIt SDK Version 10.1.1b1
    Partial serial FETCH5X001-P6FS-3LLA T
    Connecting to www.sarahgoldfarb.com port 21 (Mac OS X firewall is off) (4/19/09 12:42:45 PM)
    Update check started at 04/19/2009 12:44 PM
    Connecting to www.sarahgoldfarb.com port 21 (Mac OS X firewall is off) (4/19/09 12:44:15 PM)
    Update check skipped at 04/19/2009 12:45 PM (next check after 04/20/2009 04:00 AM)
    Connecting to www.sarahgoldfarb.com port 21 (Mac OS X firewall is off) (4/19/09 12:46:26 PM)
    Connecting to www.sarahgoldfarb.com port 21 (Mac OS X firewall is off) (4/19/09 12:48:39 PM)
    Connecting to www.sarahgoldfarb.com port 21 (Mac OS X firewall is off) (4/19/09 12:53:19 PM)
    Connecting to www.sarahgoldfarb.com port 21 (Mac OS X firewall is off) (4/19/09 12:55:03 PM)
    Connecting to www.sarahgoldfarb.com port 21 (Mac OS X firewall is off) (4/19/09 1:05:52 PM)

    Posted 5 years ago #

  • Scott McGuire Administrator

    Hi Sarah,

    I did some tests and looks like that server is not responding to FTP requests for some reason.

    You should contact the people or company who runs the server (the hosting company) and have them look into the problem; this is a problem with the server, and there's nothing to be done on the Fetch end.

    Please let us know if you have more questions after talking to them.

    Thanks,

    Scott McGuire
    Fetch Softworks

    Posted 5 years ago #

  • david Member

    Fetch 5.3.1 (5D226) Intel running on Mac OS X 10.5.7 (9J61) Intel English
    StuffIt Engine 0x820, StuffIt SDK Version 10.1.1b1
    Partial serial FETCH5X001-WSPN-NNGN T
    Connecting to ftp.hathcoxphoto.com port 21 (Mac OS X firewall is allowing connections) (7/10/09 6:30:51 PM)
    Connected to 207.176.31.200 port 21 (7/10/09 6:30:51 PM)
    Update check skipped at 07/10/2009 06:31 PM (next check after 07/11/2009 05:26 AM)
    Connecting to ftp.hathcoxphoto.com port 21 (Mac OS X firewall is allowing connections) (7/10/09 6:32:26 PM)
    Connected to 207.176.31.200 port 21 (7/10/09 6:32:26 PM)

    Posted 5 years ago #

  • Scott McGuire Administrator

    Hi David,

    I assume you are having problems connecting to your server?

    It looks like there may have been a temporary problem with your server. You should try again this morning and see if you can connect now. If not, you should contact the people or company who runs the server and have them look into the problem. I don't think there is anything you can do on the Fetch end, but please let us know if you have more questions after talking to them.

    Thanks,

    Scott McGuire
    Fetch Softworks

    Posted 5 years ago #

  • david Member

    I have checked with the server provider several times and they have checked and attempted to determine if there are any problems on their end.

    I have talked at length with Apple tech and they have scheduled an engineer to look at an error transcript as well.

    I have talked to Comcast about their service and modem (linksys).

    I have discussed this with my ftp server tech and they have checked their systems and so far found no problem.

    But no relief yet.

    Again let me describe what is happening. I get the error dropped server message when trying to connect to the server that hosts my website when I try to do it from my home office. This happens both using wireless and a ethernet connection.

    I can connect to other ftp servers other than my own. I can go to an offsite hotspot and connect to my website ftp server, I just cannot do it from my office.

    This is the error transcript I am getting this morning.

    Fetch 5.3.1 (5D226) Intel running on Mac OS X 10.5.7 (9J61) Intel English
    StuffIt Engine 0x820, StuffIt SDK Version 10.1.1b1
    Partial serial FETCH5X001-WSPN-NNGN T
    Connecting to ftp.hathcoxphoto.com port 21 (Mac OS X firewall is allowing connections) (7/12/09 11:16:13 AM)
    Connected to 207.176.31.200 port 21 (7/12/09 11:16:13 AM)

    Posted 5 years ago #

  • Scott McGuire Administrator

    Hi David,

    Based on the description of your problem - that you can connect to other servers from home but not this one, and that you can connect to this one from all locations but your home - the most likely explanations are:

    * Some servers disallow connections from certain IP addresses (a computer's Internet address). Possibly the server is refusing connections from your home address, but not from the addresses of the offsite locations you tried.

    * For some reason, your ISP's network (Comcast) is having trouble sending data to the server's network (there is a break in the network somewhere).

    There are no settings or problems in Fetch that would keep it from reaching a certain server only in a certain location, so the problem is external to Fetch.

    Unfortunately, the trick is figuring out where the problem lies, and convincing someone to fix it.

    I would try doing the following to help isolate the problem:

    * Open the Applications folder.
    * Open the Utilities folder.
    * Open the Terminal application.
    * At the prompt, type:

    ping ftp.hathcoxphoto.com

    * Let it run for 30 seconds.
    * Type Control-C to stop the command from running.

    Copy and paste any output here. This should help tell us whether it is a problem with reaching the server from your home address, or if it is a problem with the FTP software on the server rejecting you in particular.

    (Then you can just quit the Terminal application.)

    Thanks,

    Scott McGuire
    Fetch Softworks

    Posted 5 years ago #

  • david Member

    Last login: Mon Jul 13 10:50:53 on console
    david-hathcoxs-macbook-pro:~ davidhathcox$ ping ftp.hathcoxphoto.com
    PING ftp.hathcoxphoto.com (207.176.31.200): 56 data bytes
    64 bytes from 207.176.31.200: icmp_seq=0 ttl=57 time=14.144 ms
    64 bytes from 207.176.31.200: icmp_seq=1 ttl=57 time=13.160 ms
    64 bytes from 207.176.31.200: icmp_seq=2 ttl=57 time=11.388 ms
    64 bytes from 207.176.31.200: icmp_seq=3 ttl=57 time=15.774 ms
    64 bytes from 207.176.31.200: icmp_seq=4 ttl=57 time=12.904 ms
    64 bytes from 207.176.31.200: icmp_seq=5 ttl=57 time=11.440 ms
    64 bytes from 207.176.31.200: icmp_seq=6 ttl=57 time=12.033 ms
    64 bytes from 207.176.31.200: icmp_seq=7 ttl=57 time=12.894 ms
    64 bytes from 207.176.31.200: icmp_seq=8 ttl=57 time=11.225 ms
    64 bytes from 207.176.31.200: icmp_seq=9 ttl=57 time=14.645 ms
    64 bytes from 207.176.31.200: icmp_seq=10 ttl=57 time=12.707 ms
    64 bytes from 207.176.31.200: icmp_seq=11 ttl=57 time=11.063 ms
    64 bytes from 207.176.31.200: icmp_seq=12 ttl=57 time=12.278 ms
    64 bytes from 207.176.31.200: icmp_seq=13 ttl=57 time=12.518 ms
    64 bytes from 207.176.31.200: icmp_seq=14 ttl=57 time=13.244 ms
    64 bytes from 207.176.31.200: icmp_seq=15 ttl=57 time=14.582 ms
    64 bytes from 207.176.31.200: icmp_seq=16 ttl=57 time=12.485 ms
    64 bytes from 207.176.31.200: icmp_seq=17 ttl=57 time=10.999 ms
    64 bytes from 207.176.31.200: icmp_seq=18 ttl=57 time=14.465 ms
    64 bytes from 207.176.31.200: icmp_seq=19 ttl=57 time=12.583 ms
    64 bytes from 207.176.31.200: icmp_seq=20 ttl=57 time=13.209 ms
    64 bytes from 207.176.31.200: icmp_seq=21 ttl=57 time=14.148 ms
    64 bytes from 207.176.31.200: icmp_seq=22 ttl=57 time=13.389 ms
    64 bytes from 207.176.31.200: icmp_seq=23 ttl=57 time=11.683 ms
    64 bytes from 207.176.31.200: icmp_seq=24 ttl=57 time=12.323 ms
    64 bytes from 207.176.31.200: icmp_seq=25 ttl=57 time=13.341 ms
    64 bytes from 207.176.31.200: icmp_seq=26 ttl=57 time=11.634 ms
    64 bytes from 207.176.31.200: icmp_seq=27 ttl=57 time=13.210 ms
    64 bytes from 207.176.31.200: icmp_seq=28 ttl=57 time=20.369 ms
    64 bytes from 207.176.31.200: icmp_seq=29 ttl=57 time=11.746 ms
    64 bytes from 207.176.31.200: icmp_seq=30 ttl=57 time=12.345 ms
    64 bytes from 207.176.31.200: icmp_seq=31 ttl=57 time=13.109 ms
    64 bytes from 207.176.31.200: icmp_seq=32 ttl=57 time=11.425 ms
    64 bytes from 207.176.31.200: icmp_seq=33 ttl=57 time=12.599 ms
    64 bytes from 207.176.31.200: icmp_seq=34 ttl=57 time=12.960 ms
    64 bytes from 207.176.31.200: icmp_seq=35 ttl=57 time=11.646 ms
    64 bytes from 207.176.31.200: icmp_seq=36 ttl=57 time=12.236 ms
    64 bytes from 207.176.31.200: icmp_seq=37 ttl=57 time=13.285 ms
    64 bytes from 207.176.31.200: icmp_seq=38 ttl=57 time=14.148 ms
    64 bytes from 207.176.31.200: icmp_seq=39 ttl=57 time=13.245 ms
    64 bytes from 207.176.31.200: icmp_seq=40 ttl=57 time=13.110 ms
    64 bytes from 207.176.31.200: icmp_seq=41 ttl=57 time=11.530 ms
    64 bytes from 207.176.31.200: icmp_seq=42 ttl=57 time=12.246 ms
    64 bytes from 207.176.31.200: icmp_seq=43 ttl=57 time=13.050 ms
    64 bytes from 207.176.31.200: icmp_seq=44 ttl=57 time=11.505 ms
    64 bytes from 207.176.31.200: icmp_seq=45 ttl=57 time=12.303 ms
    64 bytes from 207.176.31.200: icmp_seq=46 ttl=57 time=12.684 ms
    64 bytes from 207.176.31.200: icmp_seq=47 ttl=57 time=13.421 ms
    ^C
    --- ftp.hathcoxphoto.com ping statistics ---
    48 packets transmitted, 48 packets received, 0% packet loss
    round-trip min/avg/max/stddev = 10.999/12.884/20.369/1.502 ms
    david-hathcoxs-macbook-pro:~ davidhathcox$

    Posted 5 years ago #

  • Scott McGuire Administrator

    Hi David,

    The ping test shows that data from your computer is able to make it to the server and back again, so it's not a break in the network between you and it. So the problem probably isn't being caused by Comcast, although there could still be something odd in the network or that they're doing that is casing the problem.

    More likely the problem is on the server end somewhere, perhaps having to do with your IP address, as I suggested before.

    Could you do the following, just to confirm that the problem happens with another FTP client (the command-line one built into Mac OS X)?

    * Open the Applications folder.
    * Open the Utilities folder.
    * Open the Terminal application.
    * At the prompt, type:

    ftp ftp.hathcoxphoto.com

    (note you need to type ftp twice - first is the command, the second is part of the server's hostname).

    * And then press the Return key.
    * Then the command-line ftp client will either give you an error, or prompt you for "Name:". If you get an error, copy and paste it in a reply to this message, and skip the rest of the steps.
    * If you get a prompt for "Name:", type your username and press the Return key.
    * Then you will be prompted to enter your password; enter your password and press the Return key. (The letters you type won't appear on the screen, for privacy.)
    * Type "debug" (without quotes), and press the Return key.
    * Type "ls" (without quotes), and press the Return key.
    * You'll get a response from the server at this point. Please copy the response, and paste it into a reply to this message.
    * Then you can exit the command-line ftp client by typing "quit" (without the quotes).

    Thanks,

    Scott McGuire
    Fetch Softworks

    Posted 5 years ago #

  • david Member

    Last login: Mon Jul 13 11:18:44 on ttys000
    david-hathcoxs-macbook-pro:~ davidhathcox$ ftp ftp.hthcoxphoto.com
    ftp: ftp.hthcoxphoto.com: nodename nor servname provided, or not known
    ftp> ftp ftp.hathcoxphoto.com
    Connected to ftp.hathcoxphoto.com.
    421 Service not available, remote server has closed connection.
    ftp> ftp.hathcoxphoto.com
    ?Invalid command.
    ftp>

    Posted 5 years ago #

  • Scott McGuire Administrator

    Hi David,

    Thanks. The command-line FTP client can't connect either, and it in fact suggests that it was the server that deliberately disconnected you.

    It looks like you need to talk with the server people again and see if you can get them to figure out what the problem is. You might want to tell them you tried from the command line FTP client and send them the output from it.

    Good luck, and please let us know if there are any other questions we can answer.

    Thanks,

    Scott McGuire
    Fetch Softworks

    Posted 5 years ago #

  • Steve Member

    I suddenly cannot connect to my ftp server or any ftp server through Fetch? Any ideas?

    Imac 10.4.11

    Note: recently installed a Lexmark wifi printer - if that makes any diff

    Posted 4 years ago #

  • Scott McGuire Administrator

    Hi Steve,

    When you suddenly can't connect to a server that you have previously been able to connect to, and you haven't made any changes, this almost always means the server is experiencing problems.

    Installing the printer shouldn't have affected Fetch in any way.

    You should contact the people who run the server to see if they are aware of any problems and verify the hostname, username, and password you are using to make sure that there hasn't been a change in the connection information.

    If you still have questions after talking to them, please let us know.

    Thanks,

    Scott McGuire
    Fetch Softworks

    Posted 4 years ago #

  • Steve Member

    I have spoken to easyspace - the host - and they have tested the server - no changes and everything works from their end.??

    Posted 4 years ago #

  • Scott McGuire Administrator

    Hi Steve,

    Thanks for that information.

    Two questions for you:

    Are you trying to connect to the problem server using FTP or SFTP?

    And can you connect to our server? Try connecting using the following information:

    Hostname: ftp.fetchsoftworks.com
    Username: (leave empty)
    Password: (leave empty)

    Thanks,

    Scott McGuire
    Fetch Softworks

    Posted 4 years ago #

  • Gay Jacobs Member

    Hi. I keep getting "An FTP connection could not be opened because the FTP server dropped the connection. Try again or contact the server administrator to verify that that server is running"

    Two things - first, it said it didn't recognize my password. I realized it was probably because I had changed my Yahoo! password and may not have changed it on Fetch. Once I tried the new password, I got the "FTP server dropped the connection" error.

    Secondly - I have a Mac and I now have Snow Leopard. Could that have an impact on this?

    Thanks for any help you can provide.

    Posted 4 years ago #

  • Scott McGuire Administrator

    Hi Gay,

    The upgrade to Snow Leopard should not affect or change your ability to connect to a server.

    You should contact the company or people who run the server, and verify the hostname, username, and password that you need to use to connect to the server. One of those may have changed, which is why you are running into a problem.

    Here at Fetch Softworks we don't run the server that you are trying to connect to; we just make Fetch, software that lets you move files from your Macintosh to servers run by other companies or people. So we don't have access to the information you need to use to connect.

    Please let us know if you have more questions after talking to the server folks.

    Thanks,

    Scott McGuire
    Fetch Softworks

    Posted 4 years ago #

  • Gay Jacobs Member

    Hi Scott,

    I found out that Yahoo! changed the username setup and that was what was causing the error. All's fixed now, though. Yay.

    Thanks for your quick reply though.

    Posted 4 years ago #

  • Scott McGuire Administrator

    Hi Gay,

    You're welcome, we're glad to hear you're all set.

    Best,

    Scott McGuire
    Fetch Softworks

    Posted 4 years ago #

  • Matt Member

    Hi Scott,
    I am having the same type of problem. I was able to connect to a partner's FTP site, then they made the switch to SFTP, now I can no longer connect. Although I believe my client has been able to access the FPT using only FTP protocol. I did the ping test like above. What can you tell from these results?
    Thanks

    46 packets transmitted, 0 packets received, 100% packet loss

    Posted 4 years ago #

  • Scott McGuire Administrator

    Hi Matt,

    The most likely explanation of those ping results is that either the computer at the hostname you pinged is not working properly, or that there is no computer at that hostname. (The computer could be blocking ping requests or something on your network could be blocking them, but those are less likely.)

    I would contact the people who run the server and verify the hostname you should use to contact the server; it could be that it has changed and you need to be using a different hostname - that is why attempts to connect with Fetch and ping aren't working. (You should verify the username and password to use as well.)

    Please let us know if you have additional questions after talking to them.

    Thanks,

    Scott McGuire
    Fetch Softworks

    Posted 4 years ago #

  • Matt Member

    Thanks, Scott, I will look into it further.

    Posted 4 years ago #

  • Nate Member

    I've tried all the above and believe it is the host, but they don't open for another hour so thought I'd see if I am forgetting anything here.

    I have tried Fetch and opened the window in terminal, get connected, but no option to enter Name or Password, just sits there at connected until this comes up:

    421 Service not available, remote server timed out. Connection closed.

    Just wanting to make sure that I'm not missing anything. Any additional thoughts?

    Thanks for the help!
    Nate

    Posted 4 years ago #

  • Scott McGuire Administrator

    Hi Nate,

    That definitely sounds like a problem with the host's server. I don't think there's anything more you can do on your end, sorry.

    But please let us know if you have further questions after talking to them.

    Thanks,

    Scott McGuire
    Fetch Softworks

    Posted 4 years ago #

  • kenny k Member

    I am also having an issue however i think its either with my macbook pro settings or my internet. i do believe its my computers because i plugged directly into my cable modem and bypassed the wireless router. what is happening is no data connection is being made. i can connect to the server, but the data connection never happens. i went thru the trouble shooting steps and i was able to ping and set the ftp server to pasv but when it tries to list the directory i get error 425: cant open data connection. Any help!?!?!?!?!

    Thanks
    Kenny

    Posted 4 years ago #

  • Scott McGuire Administrator

    Hi Kenny,

    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 #

  • kenny k Member

    I got it working! i downloaded little snitch and allowed some ports that were blocked... leave it to apple with their snow leopard to UNDO the good things about their software.

    Posted 4 years ago #

  • Scott McGuire Administrator

    Hi Kenny,

    Glad to hear you're all set.

    Best,

    Scott McGuire
    Fetch Softworks

    Posted 4 years ago #

  • seiji Member

    I am also having a problem with connecting to the server.
    it keeps dropping.

    I use tiger on Macbook pro. here is what I have...

    34 packets transmitted, 2 packets received, 94% packet loss
    round-trip min/avg/max/stddev = 192.503/192.633/192.764/0.130 ms

    please advice me..

    Posted 3 years ago #