Your best friend for file transfer.

Fetch application logoFetch

Passive Nightmare (6 posts)

  • Started 6 years ago by lukeMV
  • Latest reply 6 years ago from Scott McGuire
  • lukeMV Member

    I have been using Fetch to FTP several servers that I do work on. Last night, out of the blue, one of my accounts no longer worked...it would die on listing the file and then give the use passive mode error. I haven't made any changes to my software nor computer. I am using OS X10.5.5. Oddly enough, it only gives an error for 2 of the 10 sites that I work on. I talked to my host and they have not made any changes to the server and I can connect fine from work. Anyone have any idea of something that I may have done to prevent my access from my home?

    Posted 6 years ago #

  • Scott McGuire Administrator

    Hi,

    If you have made no changes to your software or network setup (including your router and cable modem), and passive connections to most servers still work, then, despite what the host says, the change and problem is most likely on their end. Any change you might have made that prevented passive connections from working would affect passive connections to all servers, not just a couple of servers.

    Normally Fetch should retry in active mode if passive mode fails - of course, there are setups where active mode connections can fail as well.

    If you could send us a transcript from one of the failed connections, we'll take a look and try to figure out what might be going on and offer suggestions for solving the problem.

    To do this:

    * Quit Fetch.
    * Open Fetch again.
    * Connect to the problem server.
    * 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.

    Thanks,

    Scott McGuire
    Fetch Softworks

    Posted 6 years ago #

  • lukeMV Member

    Thanks for the prompt reply!

    Here is the transcript:

    Fetch 5.3 (5D161) PowerPC running on Mac OS X 10.5.5 (9F33) PowerPC English
    StuffIt Engine 0x820, StuffIt SDK Version 10.1.1b1
    Partial serial FETCHED001-05MN-91F2 T
    Connecting to laurinslist.com port 21 (Mac OS X firewall is allowing connections) (9/30/08 10:32:36 PM)
    Connected to 208.109.181.210 port 21 (9/30/08 10:32:36 PM)
    220---------- Welcome to Pure-FTPd [privsep] [TLS] ----------
    220-You are user number 9 of 50 allowed.
    220-Local time is now 19:32. Server port: 21.
    220-This is a private system - No anonymous login
    220 You will be disconnected after 3 minutes of inactivity.
    USER laurinbechard
    331 User laurinbechard OK. Password required
    PASS
    230-User laurinbechard has group access to: 450
    230 OK. Current directory is /
    SYST
    215 UNIX Type: L8
    PWD
    257 "/" is your current location
    MACB ENABLE
    500 Unknown command
    PWD
    257 "/" is your current location
    TYPE A
    200 TYPE is now ASCII
    PASV
    227 Entering Passive Mode (208,109,181,210,219,35)
    Making data connection to 208.109.181.210 port 56099
    ABOR
    500 ?
    PORT 192,168,1,101,217,120
    ABOR
    ftp_list: 2,-30027 (state == GETTING_LIST)
    QUIT
    send_cmd():con_conn->Putline() returns 2,32767

    I also did a tracer root, if that helps:
    traceroute ftp.laurinslist.com
    traceroute to laurinslist.com (208.109.181.210), 64 hops max, 40 byte packets
    1 192.168.1.1 (192.168.1.1) 2.354 ms 1.273 ms 1.208 ms
    2 10.80.32.1 (10.80.32.1) 8.978 ms 11.423 ms 9.130 ms
    3 172.20.15.105 (172.20.15.105) 10.037 ms 9.243 ms 9.668 ms
    4 172.20.15.101 (172.20.15.101) 11.907 ms 9.513 ms 9.753 ms
    5 so-7-1.car2.Boston1.Level3.net (4.79.0.89) 17.171 ms 18.787 ms 17.848 ms
    6 ae-2-5.bar2.Boston1.Level3.net (4.69.132.250) 19.955 ms 20.904 ms 18.525 ms
    7 ae-8-8.ebr1.NewYork1.Level3.net (4.69.140.98) 20.258 ms 21.131 ms 20.515 ms
    8 ae-91-91.csw4.NewYork1.Level3.net (4.69.134.78) 20.694 ms 22.463 ms ae-61-61.csw1.NewYork1.Level3.net (4.69.134.66) 17.575 ms
    9 ae-63-63.ebr3.NewYork1.Level3.net (4.69.134.97) 20.642 ms 27.684 ms 18.897 ms
    10 ae-6.ebr2.Dallas1.Level3.net (4.69.137.121) 66.272 ms 65.155 ms 73.149 ms
    11 ae-82-82.csw3.Dallas1.Level3.net (4.69.136.146) 57.873 ms 65.228 ms 55.817 ms
    12 ae-81-81.ebr1.Dallas1.Level3.net (4.69.136.129) 85.670 ms 58.263 ms 57.117 ms
    13 ae-8-8.car1.Phoenix1.Level3.net (4.69.133.29) 88.023 ms 88.304 ms 88.856 ms
    14 THE-GO-DADD.car1.Phoenix1.Level3.net (4.53.104.2) 80.670 ms 90.399 ms 81.333 ms
    15 ip-208-109-112-153.ip.secureserver.net (208.109.112.153) 80.671 ms 80.084 ms 78.738 ms
    16 ip-208-109-112-142.ip.secureserver.net (208.109.112.142) 79.758 ms 81.248 ms 79.872 ms
    17 ip-216-69-188-33.ip.secureserver.net (216.69.188.33) 81.825 ms 82.243 ms 82.126 ms
    18 * * *
    19 * * *
    20 * * *
    21 * * *
    22 * * *
    23 * * *
    24 * * *
    25 * * *
    26 * * *
    27 * * *
    28 * * *
    29 * * *
    30 * * *
    31 * * *
    32 * * *
    33 * * *
    34 * * *
    35 * * *
    36 * * *
    37 * * *
    38 * * *
    39 * * *
    40 * * *
    41 * * *
    42 * * *
    43 * * *
    44 * * *
    45 * * *
    46 * * *
    47 * * *
    48 * * *
    49 * * *
    50 * * *
    51 * * *
    52 * * *
    53 * * *
    54 * * *
    55 * * *
    56 * * *
    57 * * *
    58 * * *
    59 * * *
    60 * * *
    61 * * *
    62 * * *
    63 * * *
    64 * * *

    Thanks for your help!

    Originally posted by ScottMcGuire:

    Hi,

    If you have made no changes to your software or network setup (including your router and cable modem), and passive connections to most servers still work, then, despite what the host says, the change and problem is most likely on their end. Any change you might have made that prevented passive connections from working would affect passive connections to all servers, not just a couple of servers.

    Normally Fetch should retry in active mode if passive mode fails - of course, there are setups where active mode connections can fail as well.

    If you could send us a transcript from one of the failed connections, we'll take a look and try to figure out what might be going on and offer suggestions for solving the problem.

    To do this:

    * Quit Fetch.
    * Open Fetch again.
    * Connect to the problem server.
    * 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.

    Thanks,

    Scott McGuire
    Fetch Softworks

    Posted 6 years ago #

  • Scott McGuire Administrator

    Hi,

    Thanks for the transcript. This does look like either a server or a network problem.

    I'm not sure if the traceroute - odd though it looks, since it never finds the server - is relevant, since the transcript shows you are actually successfully connecting to the server.

    If you open the Fetch Preferences, and uncheck the "Use passive mode transfers" checkbox, then try to connect again, can you connect successfully?

    Thanks,

    Scott McGuire
    Fetch Softworks

    Posted 6 years ago #

  • lukeMV Member

    Just to let you know, the problem was with my ISP. After a call into them, they had done some work on the lines and after a hard restart to the router, it appears to have fixed the problem. Odd! THanks for taking the time to help me out.

    Originally posted by ScottMcGuire:

    Hi,

    Thanks for the transcript. This does look like either a server or a network problem.

    I'm not sure if the traceroute - odd though it looks, since it never finds the server - is relevant, since the transcript shows you are actually successfully connecting to the server.

    If you open the Fetch Preferences, and uncheck the "Use passive mode transfers" checkbox, then try to connect again, can you connect successfully?

    Thanks,

    Scott McGuire
    Fetch Softworks

    Posted 6 years ago #

  • Scott McGuire Administrator

    Hi,

    You're welcome, and thanks for the followup - we're glad to hear the problem is sorted out.

    Best,

    Scott McGuire
    Fetch Softworks

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