Your best friend for file transfer.

Fetch application logoFetch

problems with connection (15 posts)

  • Started 7 years ago by blt
  • Latest reply 6 years ago from blt
  • blt Member

    I'm on a mac running system 10.4.8 with fetch 5.2. A server I need to work with recently underwent some changes and now I can not connect with them. I verified address and passwords with them, but still am not connecting. I've switched back and forth with the passive mode - still nothing. Could you look at this transcript and tell me if you see what the problem is? Thanks so much.

    Fetch 5.2 (5C121) PowerPC running on Mac OS X 10.4.8 (8L127) PowerPC English
    StuffIt Engine 0x820, StuffIt SDK Version 10.1.1b1
    Partial serial FETCH5X001-4VL2-9SRU T
    Connecting to 216.61.239.3 port 21 (Mac OS X firewall is off) (4/18/07 10:59:20 AM)
    Connected to 216.61.239.3 port 21 (4/18/07 10:59:20 AM)
    220--------------------------------------------------------------------------------
    220- Thanks for your business. All of us at NPC wish you a great day.
    220--------------------------------------------------------------------------------
    220-
    220 npcxserve.local FTP server ready.
    USER generic
    331 Password required for generic.
    PASS
    230--------------------------------------------------------------------------------
    230-This is the Nowata Printing Company FTP server. No anonymous logins are allowed. Call Dusty for login info.
    230--------------------------------------------------------------------------------
    230-
    230 User generic logged in.
    SYST
    215 UNIX Type: L8 Version: BSD-199506
    PWD
    257 "/" is current directory.
    MACB ENABLE
    502 'MACB ENABLE': command not understood.
    PWD
    257 "/" is current directory.
    TYPE A
    200 Type set to A.
    PORT 192,168,100,25,192,141
    500 Illegal PORT Command
    PASV
    227 Entering Passive Mode (10,0,33,3,242,206)
    Making data connection to 216.61.239.3 port 62158
    ABOR
    225 ABOR command successful.
    ftp_list: 2,-30000 (state == GETTING_LIST)
    PWD
    257 "/" is current directory.
    Update check skipped at 04/18/2007 11:01 AM (next check after 04/23/2007 05:08 PM)
    PWD
    257 "/" is current directory.
    PWD
    257 "/" is current directory.
    PWD
    257 "/" is current directory.
    PWD
    257 "/" is current directory.
    QUIT
    221-You have transferred 0 bytes in 0 files.
    221-Total traffic for this session was 141 bytes in 0 transfers.
    221-Thank you for using the FTP service on npcxserve.local.
    221 Goodbye.

    Posted 7 years ago #

  • Scott McGuire Administrator

    Hi,

    Could you please try a couple of things to help us analyze the problem?

    First, try this:

    * Choose Preferences from the Fetch menu.
    * Click the General tab.
    * Make sure "Use passive mode transfers" is checked.
    * Then click the Miscellaneous tab.
    * Look at the "Use 'LIST -al' command to reveal hidden files" checkbox. If it is unchecked, check it; if it is checked, uncheck it. That is, whatever it is now, change it to the other setting.
    * Try connecting again.

    If that doesn't help, try connecting to ftp.fetchsoftworks.com - leave the username and password fields blank. Can you connect successfully to ftp.fetchsoftworks.com?

    Thanks,

    Scott McGuire
    Fetch Softworks

    Posted 7 years ago #

  • blt Member

    Thank you for your quick response.

    I checked the box for "Use passive mode transfers".
    I checked the box for "Use 'LIST-al'".
    Still could not connect.

    I tried the ftp.fetchsoftworks.com address and it appeared to connect just fine.

    Posted 7 years ago #

  • blt Member

    I'm sorry - about the error message when I could not connect - it said:
    Fetch could not get the file list because there was a timeout trying to establish a passive mode data connection.

    Posted 7 years ago #

  • Scott McGuire Administrator

    Hi,

    Sorry to hear that did not fix the problem.

    Could you show us a transcript of trying to connect to the problem server, with both the "Use passive" and "Use LIST -al" checkboxes checked?

    Thanks,

    Scott McGuire
    Fetch Softworks

    Posted 7 years ago #

  • blt Member

    With both options checked I got the response: An FTP connection could not be opened because the connection timed out.

    Following is the transcript:
    Fetch 5.2 (5C121) PowerPC running on Mac OS X 10.4.8 (8L127) PowerPC English
    StuffIt Engine 0x820, StuffIt SDK Version 10.1.1b1
    Partial serial FETCH5X001-4VL2-9SRU T
    Connecting to 216.61.23.3 port 21 (Mac OS X firewall is off) (4/18/07 1:46:41 PM)
    Update check skipped at 04/18/2007 01:48 PM (next check after 04/23/2007 05:08 PM)

    Posted 7 years ago #

  • blt Member

    I just tried it again to see what it would do with those options checked -

    Fetch 5.2 (5C121) PowerPC running on Mac OS X 10.4.8 (8L127) PowerPC English
    StuffIt Engine 0x820, StuffIt SDK Version 10.1.1b1
    Partial serial FETCH5X001-4VL2-9SRU T
    Connecting to 216.61.23.3 port 21 (Mac OS X firewall is off) (4/18/07 1:46:41 PM)
    Update check skipped at 04/18/2007 01:48 PM (next check after 04/23/2007 05:08 PM)
    Connecting to 216.61.239.3 port 21 (Mac OS X firewall is off) (4/18/07 2:17:25 PM)
    Connected to 216.61.239.3 port 21 (4/18/07 2:17:27 PM)
    220--------------------------------------------------------------------------------
    220- Thanks for your business. All of us at NPC wish you a great day.
    220--------------------------------------------------------------------------------
    220-
    220 npcxserve.local FTP server ready.
    USER generic
    331 Password required for generic.
    PASS
    230--------------------------------------------------------------------------------
    230-This is the Nowata Printing Company FTP server. No anonymous logins are allowed. Call Dusty for login info.
    230--------------------------------------------------------------------------------
    230-
    230 User generic logged in.
    SYST
    215 UNIX Type: L8 Version: BSD-199506
    PWD
    257 "/" is current directory.
    MACB ENABLE
    502 'MACB ENABLE': command not understood.
    PWD
    257 "/" is current directory.
    TYPE A
    200 Type set to A.
    PASV
    227 Entering Passive Mode (10,0,33,3,14,65)
    Making data connection to 216.61.239.3 port 3649
    ABOR
    225 ABOR command successful.
    PORT 192,168,100,25,194,144
    500 Illegal PORT Command
    ftp_list: 2,-30027 (state == GETTING_LIST)

    Posted 7 years ago #

  • Scott McGuire Administrator

    Hi,

    Thanks for the additional transcripts.

    We'd like you to try to connect to your server using the command line ftp client that's built into Mac OS X. That will help us determine whether this is a Fetch problem, or a problem with something else. To do this:

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

    ftp -a your-server-address

    * Replace "your-server-address" with the hostname (or IP address) for your server.
    * And then press the Return key.
    * Then the command-line ftp client will prompt you 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.)
    * 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 exit the command-line ftp client by typing "quit" (without the quotes).

    Thanks,

    Scott McGuire
    Fetch Softworks

    Posted 7 years ago #

  • blt Member

    The response:

    Password:
    230--------------------------------------------------------------------------------
    230-This is the Nowata Printing Company FTP server. No anonymous logins are allowed. Call Dusty for login info.
    230--------------------------------------------------------------------------------
    230-
    230 User generic logged in.
    Remote system type is UNIX.
    Using binary mode to transfer files.
    ftp>

    Posted 7 years ago #

  • Scott McGuire Administrator

    Hi,

    Thanks for the info from the command line.

    If you saw my previous suggestion to try Fetch 5.1.1, please disregard that request for now.

    Instead, could you please connect again with the command line ftp client (as above), and once you get the "ftp>" prompt, do the following:

    * Type "debug" (no quotes), and press the Return key.
    * Then type "dir" (no quotes), and press the Return key.

    Please copy the response, and paste it into a reply to this message.

    Thanks, and sorry to keep asking you to do all these things, but we are trying to figure out where the problem lies.

    Scott McGuire
    Fetch Softworks

    Posted 6 years ago #

  • blt Member

    I'm sorry I don't know much about this 'terminal' business?? I hope I did what you asked...

    Last login: Fri Apr 20 08:01:03 on console
    Welcome to Darwin!
    Brendas-computer:~ brenda$ ftp debug
    ftp: No address associated with nodename
    ftp> debug
    Debugging on (debug=1).
    ftp> dir
    Not connected.
    ftp> quit

    Posted 6 years ago #

  • Scott McGuire Administrator

    Hi,

    No, sorry, that wasn't quite what I was looking for.

    But I realize that working with the Terminal isn't familiar to most people, and I should have been more specific, sorry.

    Here are the exact steps I would like you to follow:

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

    ftp -a your-server-address

    * Replace "your-server-address" with the hostname (or IP address) for your server.
    * And then press the Return key.
    * Then the command-line ftp client will prompt you 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.)
    * At the "ftp>" prompt, type "debug" (no quotes), and press the Return key.
    * Then type "dir" (no quotes), and press the Return key.

    Then please copy the response, and paste it into a reply to this message.

    Thanks,

    Scott McGuire
    Fetch Softworks

    Posted 6 years ago #

  • blt Member

    Thanks for your directions! Is this correct?

    Last login: Fri Apr 20 08:40:32 on ttyp1
    Welcome to Darwin!
    Brendas-computer:~ brenda$ ftp 216.61.239.3
    Connected to 216-61-239-3.ded.swbell.net.
    220--------------------------------------------------------------------------------
    220- Thanks for your business. All of us at NPC wish you a great day.
    220--------------------------------------------------------------------------------
    220-
    220 npcxserve.local FTP server ready.
    Name (216.61.239.3:brenda): generic
    331 Password required for generic.
    Password:
    230--------------------------------------------------------------------------------
    230-This is the Nowata Printing Company FTP server. No anonymous logins are allowed. Call Dusty for login info.
    230--------------------------------------------------------------------------------
    230-
    230 User generic logged in.
    Remote system type is UNIX.
    Using binary mode to transfer files.
    ftp> debug
    Debugging on (debug=1).
    ftp> dir
    ---> EPSV
    502 'EPSV': command not understood.
    disabling epsv4 for this connection
    ---> PASV
    227 Entering Passive Mode (10,0,33,3,63,139)

    ---> PORT 192,168,100,25,193,165
    500 Illegal PORT Command
    ---> LIST

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

    Posted 6 years ago #

  • Scott McGuire Administrator

    Hi,

    It looks like Fetch and the command-line ftp client are seeing the same problem.

    We believe the problem connecting to this server is the result of a combination of a problem with the server, and a router problem.

    There are two "modes" for connecting to FTP servers, active (the PORT command) and passive (the PASV command). Passive is usually more compatible with routers and NATs, so that's what Fetch and the command-line ftp client try first. Unfortunately, the server you're connecting to doesn't support passive mode connections. So then Fetch tries an active mode connection, and that fails as well, probably because of your router (some routers have a problem where they garble active mode connections).

    You can connect to ftp.fetchsoftworks.com, and other servers, successfully because they support passive mode connections.

    So you should talk to the folks running the server and see if they can fix it so that it supports passive mode connections. Otherwise, you might be able to connect to it if you plug your Macintosh directly into your cable/DSL modem (assuming you have one), but that isn't very convenient.

    Sorry, I wish we had a better answer for you. Please let us know if you want clarifications about the above or have more questions.

    Thanks,

    Scott McGuire
    Fetch Softworks

    Posted 6 years ago #

  • blt Member

    Thank you, I appreciate all the time you've spent.

    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.