Your best friend for file transfer.

Fetch application logoFetch

inexistent file or no access rights error (4 posts)

  • Started 8 years ago by colemc
  • Latest reply 8 years ago from colemc
  • colemc Member

    I have some outside vendors using fetch with this error. I have used cute on mac and ftp commander on pc and have no problem. Seems to be we are setting up fetch incorrectly.

    I am attempting to connect to a snap server running snap os

    Fetch 5.0.5 (5A835) PowerPC running on Mac OS X 10.3.9 (7W98) PowerPC English
    StuffIt Engine 0x811, StuffIt SDK Version 9.0.1
    Expires 02/09/2006 T
    Connecting to 192.168.1.10 port 21 (OS X firewall is off) (1/26/06 2:20:16 PM)
    Connected to 192.168.1.10 port 21 (1/26/06 2:20:17 PM)
    220 Service ready for new user.
    USER gprx01
    331 User name okay, need password.
    PASS
    230 User logged in, proceed.
    SYST
    215 UNIX Type: L8 Version: SnapOS.
    PWD
    257 "/" is your working directory.
    MACB ENABLE
    502 Command not implemented.
    PWD
    257 "/" is your working directory.
    TYPE A
    200 Command okay.
    PASV
    227 Entering Passive Mode (192,168,1,10,5,60).
    LIST -al
    450 Requested file action not taken. Inexistent file or no access rights.
    ftp_list: -30000 (state == GETTING_LIST)

    Posted 8 years ago #

  • Scott McGuire Administrator

    Hi,

    They should try the following:

    Go to the "Miscellaneous" tab of the Fetch Preferences, and uncheck the "Use 'LIST -al' command to reveal hidden files" checkbox. Then try connecting again.

    (The LIST -al command is supported by most servers, but there are a few that don't like it.)

    If that still doesn't fix the problem, let us know and we'll investigate further.

    Thanks,

    Scott McGuire
    Fetch Softworks

    Posted 8 years ago #

  • colemc Member

    that was already checked. still a problem.

    Posted 8 years ago #

  • colemc Member

    Unchecking the option caused it to work.

    Thanks

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