Your best friend for file transfer.

Fetch application logoFetch

Cannot FTP - Used to be able to now No More TIME OUT (8 posts)

  • Started 9 years ago by Roundsquare1
  • Latest reply 9 years ago from Angie
  • Roundsquare1 Member

    Fetch 5.7.3 (5H683) Intel (Web Store) running on Mac OS X 10.7.5 (11G63b) Intel English
    StuffIt Engine 0x820, StuffIt SDK Version 10.1.1b1
    Partial serial FETCHED001-C4T3-FW57 T
    Connecting to 64.29.151.221 port 21 (Mac OS X firewall is limiting connections to specific applications) (5/8/14 11:26 AM)
    An FTP connection to “64.29.151.221” could not be opened because the connection timed out. (There might be a problem with your network, or the server might not be responding.)
    Connecting to 64.29.151.221 port 21 (Mac OS X firewall is limiting connections to specific applications) (5/8/14 11:28 AM)
    Update check skipped at 5/8/14 11:28 AM (next check after 5/8/14 6:24 PM)
    An FTP connection to “64.29.151.221” could not be opened because the connection timed out. (There might be a problem with your network, or the server might not be responding.)
    Connecting to roundsquare1.site.aplus.net port 21 (Mac OS X firewall is limiting connections to specific applications) (5/8/14 11:30 AM)
    An FTP connection to “roundsquare1.site.aplus.net” could not be opened because the connection timed out. (There might be a problem with your network, or the server might not be responding.)
    Connecting to larryrosa.com port 21 (Mac OS X firewall is limiting connections to specific applications) (5/8/14 12:00 PM)
    Connecting to 64.29.151.221 port 21 (Mac OS X firewall is limiting connections to specific applications) (5/8/14 12:01 PM)
    Connecting to 64.29.151.221 port 21 (Mac OS X firewall is limiting connections to specific applications) (5/8/14 12:01 PM)
    An FTP connection to “64.29.151.221” could not be opened because the connection timed out. (There might be a problem with your network, or the server might not be responding.)
    Connecting to 64.29.151.221 port 21 (Mac OS X firewall is limiting connections to specific applications) (5/8/14 12:15 PM)
    An FTP connection to “64.29.151.221” could not be opened because the connection timed out. (There might be a problem with your network, or the server might not be responding.)
    Connecting to 64.29.151.221 port 21 (Mac OS X firewall is limiting connections to specific applications) (5/8/14 12:30 PM)
    An FTP connection to “64.29.151.221” could not be opened because the connection timed out. (There might be a problem with your network, or the server might not be responding.)
    Connecting to 64.29.151.221 port 21 (Mac OS X firewall is allowing connections) (5/8/14 12:35 PM)
    Connecting to 64.29.151.221 port 21 (Mac OS X firewall is allowing connections) (5/8/14 12:36 PM)
    Connecting to 64.29.151.221 port 21 (Mac OS X firewall is allowing connections) (5/8/14 12:36 PM)
    An FTP connection to “64.29.151.221” could not be opened because the connection timed out. (There might be a problem with your network, or the server might not be responding.)
    An FTP connection to “64.29.151.221” could not be opened because the connection timed out. (There might be a problem with your network, or the server might not be responding.)
    An FTP connection to “64.29.151.221” could not be opened because the connection timed out. (There might be a problem with your network, or the server might not be responding.)

    I've turned off the firewall no luck. I called my web hosting they said nothing is wrong. I call Xfinity no luck.

    I tried every combination password, username, Host with tech support at the web provider.
    no luck.

    this is going on hour 5 now.

    Edited 9 years ago #

  • Jim Matthews Administrator

    It could be that the 64.29.151.221 server was down temporarily. It appears to be responding now. What do you see when you try now?

    Thanks,

    Jim Matthews
    Fetch Softworks

    Posted 9 years ago #

  • Roundsquare1 Member

    I'm at the end of my rope. I haven't been able to connect to ANY FTP server using FETCH or FILZILLA.

    I've spend about 15 hours with tech support with ZERO resolution over at my provider.

    I've spent about 4 hours with COMCAST with zero resolution.

    I"ve disabled firewalls, nothing works.

    ANY HELP PLEASE.

    Posted 9 years ago #

  • Jim Matthews Administrator

    Try connecting to ftp.fetchsoftworks.com, leaving the Username and Password fields blank. What do you see in the Fetch Transcript window then?

    Thanks,

    Jim Matthews
    Fetch Softworks

    Posted 9 years ago #

  • Roundsquare1 Member

    I disabled my firewall on my mac.

    Fetch 5.7.3 (5H683) Intel (Web Store) running on Mac OS X 10.7.5 (11G63b) Intel English
    StuffIt Engine 0x820, StuffIt SDK Version 10.1.1b1
    Partial serial FETCHED001-C4T3-FW57 T
    Connecting to ftp.fetchsoftworks.com port 21 (Mac OS X firewall is allowing connections) (5/12/14 11:06 AM)
    An FTP connection to “ftp.fetchsoftworks.com” could not be opened because the connection timed out. (There might be a problem with your network, or the server might not be responding.)

    here is a tracer route
    Traceroute has started…

    traceroute to 24.130.135.73 (24.130.135.73), 64 hops max, 72 byte packets
    1 c-24-130-135-73.hsd1.ca.comcast.net (24.130.135.73) 0.815 ms 0.587 ms 0.415 ms

    ig-Daddy-Rosa:~ larryrosa$ traceroute 64.29.151.221
    traceroute to 64.29.151.221 (64.29.151.221), 64 hops max, 52 byte packets
    1 10.0.0.1 (10.0.0.1) 0.678 ms 0.300 ms 0.205 ms
    2 24.130.132.1 (24.130.132.1) 8.350 ms 8.419 ms 8.482 ms
    3 te-7-2-ur01.castrovalley.ca.sfba.comcast.net (68.87.197.85) 9.813 ms 8.588 ms 8.823 ms
    4 te-0-0-0-13-ar01.sfsutro.ca.sfba.comcast.net (68.85.155.130) 12.105 ms 13.362 ms 11.832 ms
    5 he-3-11-0-0-cr01.sanjose.ca.ibone.comcast.net (68.86.94.133) 12.098 ms 12.711 ms 15.916 ms
    6 50.242.148.34 (50.242.148.34) 12.356 ms 14.245 ms 11.947 ms
    7 vlan80.csw3.sanjose1.level3.net (4.69.152.190) 79.846 ms
    vlan90.csw4.sanjose1.level3.net (4.69.152.254) 80.789 ms
    vlan60.csw1.sanjose1.level3.net (4.69.152.62) 86.144 ms
    8 ae-61-61.ebr1.sanjose1.level3.net (4.69.153.1) 79.812 ms
    ae-81-81.ebr1.sanjose1.level3.net (4.69.153.9) 80.044 ms
    ae-92-92.ebr2.sanjose1.level3.net (4.69.153.29) 79.952 ms
    9 ae-2-2.ebr2.sanjose5.level3.net (4.69.148.141) 80.467 ms 80.928 ms 80.289 ms
    10 ae-6-6.ebr2.losangeles1.level3.net (4.69.148.201) 80.804 ms 80.470 ms 80.763 ms
    11 ae-3-3.ebr3.dallas1.level3.net (4.69.132.78) 79.466 ms 79.712 ms 79.197 ms
    12 ae-73-73.csw2.dallas1.level3.net (4.69.151.145) 80.690 ms
    ae-3-3.ebr3.dallas1.level3.net (4.69.132.78) 79.120 ms 79.800 ms
    13 ae-83-83.csw3.dallas1.level3.net (4.69.151.157) 81.020 ms
    ae-93-93.csw4.dallas1.level3.net (4.69.151.169) 79.903 ms
    ae-81-81.ebr1.dallas1.level3.net (4.69.151.150) 79.866 ms
    14 ae-2-2.ebr1.miami1.level3.net (4.69.140.134) 80.051 ms 80.620 ms 80.663 ms
    15 ae-2-2.ebr1.miami1.level3.net (4.69.140.134) 79.238 ms
    ae-1-51.edge2.miami2.level3.net (4.69.138.77) 80.086 ms
    ae-2-2.ebr1.miami1.level3.net (4.69.140.134) 79.336 ms
    16 * * *
    17 * * *
    18 * * *
    19 * * *
    20 * * *
    21 * * *
    22 * * *
    traceroute 64.29.151.221:21
    23 * * *
    24 * * *
    25 * * *
    26 * * *
    27 * * *
    28 * * *
    29 * * *
    30 * * *
    31 * * *
    32 * * *
    33 *
    traceroute 64.29.151.221:20
    * *
    34 * * *
    35 * * *
    36 * * *
    37 * * *
    38 * * *
    39 * * *
    40 * * *
    41 * * *
    42 * * *
    43 * * *
    44 * * *
    45 * * *

    Posted 9 years ago #

  • Roundsquare1 Member

    and trying with filezilla

    Status: Resolving address of ftp.fetchsoftworks.com
    Status: Connecting to 216.92.46.39:21...
    Error: Connection timed out
    Error: Could not connect to server
    Status: Waiting to retry...
    Status: Delaying connection for 1 second due to previously failed connection attempt...
    Status: Resolving address of ftp.fetchsoftworks.com
    Status: Connecting to 216.92.46.39:21...
    Error: Connection timed out
    Error: Could not connect to server

    Posted 9 years ago #

  • Jim Matthews Administrator

    Hi,

    It sure looks like something is blocking your network connections. I'm afraid your best course of action is working with Comcast, or getting a different Internet Service Provider.

    Thanks,

    Jim Matthews
    Fetch Softworks

    Posted 9 years ago #

  • Angie Member

    Roundsquare1, Did you ever resolve your problem? I am having the same problem since I signed up with Comcast. When I was with DSL (Windstream) I had no problems with Fetch.

    Thanks,
    Angie

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