Your best friend for file transfer.

Fetch application logoFetch

Getting file list... forever! (5 posts)

This is an archived topic. The information in it is likely to be out-of-date and no longer applicable to current versions of Fetch.
  • Started 11 years ago by murlyn
  • Latest reply 11 years ago from Jim Matthews
  • murlyn Member

    Ok it looks like the same problem other people have had and I have unchecked and checked PASV mode... to no avail. I can access the same server with a different username and password and host and if I use the IP instead of ftp.baskettcase.com it works.. so not sure what's going on.. here is my transcript:

    Fetch 4.0.3 System 0x1025 Serial FETCHFL001-174L-8AQA TR
    Connecting to ftp.baskettcase.com port 21 (4/18/03 2:30:39 PM)
    220 Welcome. Please login...
    ADAT
    500 ADAT not understood
    USER baskettcas
    331 Password required for baskettcas.
    PASS
    230 User baskettcas logged in.
    SYST
    215 UNIX Type: L8
    PWD
    257 "/" is current directory.
    MACB ENABLE
    500 MACB not understood
    PWD
    257 "/" is current directory.
    PASV
    227 Entering Passive Mode (216,190,225,238,178,0)
    LIST

    Oh and I can ftp to it using the CLI.. so Im really not sure what is going on.. :()

    [This message has been edited by murlyn (edited 04-18-2003).]

    Posted 11 years ago #

  • Jim Matthews Administrator

    I'd be interesting in comparing that transcript to a successful one using an IP address instead of ftp.baskettcase.com. It might also be interesting to see a transcript from the command line ftp client. To generate a transcript there type "debug" before typing the "dir" command to download a file list.

    Thanks,

    Jim Matthews
    Fetch Softworks

    Posted 11 years ago #

  • murlyn Member

    Here is using the IP address:

    Fetch 4.0.3 System 0x1025 Serial FETCHFL001-174L-8AQA TR
    Connecting to 216.190.225.234 port 21 (4/21/03 9:15:47 AM)
    220 Welcome. Please login...
    USER baskettcas
    331 Password required for baskettcas.
    PASS
    230 User baskettcas logged in.
    SYST
    215 UNIX Type: L8
    PWD
    257 "/" is current directory.
    PWD
    257 "/" is current directory.
    PASV
    227 Entering Passive Mode (216,190,225,234,133,79)
    LIST
    150 Opening ASCII mode data connection for file list
    drwx--x--x 3 504 staff 102 Apr 2 00:36 Desktop
    drwxr-xr-x 7 504 staff 238 Apr 17 19:54 Documents
    drwx--x--x 20 504 staff 680 Apr 2 00:27 Library
    drwxr-xr-x 4 504 staff 136 Feb 21 17:15 Public
    drwxr-xr-x 8 504 staff 272 Apr 16 04:52 Sites
    226 Transfer complete.

    Posted 11 years ago #

  • murlyn Member

    Ok it looks like the same problem occurs there.. I never took it that far when using the command line..

    Connected to ftp.baskettcase.com.
    220 Welcome. Please login...
    Name (ftp.baskettcase.com:murlyn): baskettcas
    331 Password required for baskettcas.
    Password:
    230 User baskettcas logged in.
    Remote system type is UNIX.
    Using binary mode to transfer files.
    ftp> debug
    Debugging on (debug=1).
    ftp> dir
    ---> EPSV
    500 EPSV not understood
    disabling epsv4 for this connection
    ---> PASV
    227 Entering Passive Mode (216,190,225,238,141,98)

    and then after a long pause

    PORT 192,168,1,100,192,43
    200 PORT command successful
    ---> LIST
    425 Unable to build data connection: Connection refused

    Posted 11 years ago #

  • Jim Matthews Administrator

    I'm not sure what is going on, but it appears that you're dealing with two different IP addresses. When you connect to "ftp.baskettcase.com" it asks Fetch to connect back to 216.190.225.238, but when you are connecting by IP address you're connecting to 216.190.225.234 (and it asks you to connect back to that same address). It could be that the server is misconfigured, or that those are actually two different machines (one at .238 and one at .234). I would talk to the server administrator about this.

    Thanks,

    Jim Matthews
    Fetch Softworks

    Posted 11 years ago #

Topic closed

This topic has been closed.