Your best friend for file transfer.

Fetch application logoFetch

Invalid PORT Command? (11 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 12 years ago by jason@coopersco.com
  • Latest reply 12 years ago from jason@coopersco.com
  • jason@coopersco.com Member

    I'm trying to use Fetch 4 to connect to a FTP server running on NT 4. The NT server admin has set up a non-standard port (22) for me to connect to a particular share on the server. I am able to connect with Fetch, but anything I try (getting, putting, creating new directories, etc.) gets me a error reading "Server Response: Invalid PORT Command". Any ideas what is going on and what can be done to fix this? Thanks!

    Posted 12 years ago #

  • Jim Matthews Administrator

    It sounds like that's the WAR FTP server, which does not (in all versions) support passive mode transfers. I would suggest unchecking the "Use passive mode transfers (PASV)" box in the Firewall section of Preferences. Does that resolve the problem?

    Jim Matthews
    Fetch Softworks

    Posted 12 years ago #

  • jason@coopersco.com Member

    No help; the "Use passive mode transfers (PASV)" option is, and has been, unchecked. Any other ideas? AFAIK the FTP server is the default server run by NT 4. Not sure if that is a WAR server.

    Posted 12 years ago #

  • Jim Matthews Administrator

    Hmm. Just for completeness I'd try checking "Use passive mode transfers (PASV)". And if that does not work, could you post a transcript (from the Fetch Transcript window)?

    Thanks,

    Jim Matthews
    Fetch Softworks

    Posted 12 years ago #

  • jason@coopersco.com Member

    Here is the Fetch Transcript for a login with PASV unchecked:

    System Version = 0x910
    Connecting to 64.174.156.98 port 22 (7/11/01 6:35:35 PM)
    220 digiserver1 Microsoft FTP Service (Version 4.0).
    ADAT
    500 'ADAT Hi there, do you support security?': command not understood
    USER jason
    331 Password required for jason.
    PASS
    230 User jason logged in.
    SYST
    215 Windows_NT version 4.0
    PWD
    257 "/" is current directory.
    MACB ENABLE
    500 'MACB ENABLE': command not understood
    SITE DIRSTYLE
    200 MSDOS-like directory output is on
    SITE DIRSTYLE
    200 MSDOS-like directory output is off
    PWD
    257 "/" is current directory.
    PWD
    257 "/" is current directory.
    PORT 192,168,123,146,183,172
    500 Invalid PORT Command.
    ftp_list: -30000 (state == GETTING_LIST)
    NOOP
    200 NOOP command successful.

    Posted 12 years ago #

  • Jim Matthews Administrator

    Could you post a transcript with "Use passive mode transfers (PASV)" checked?

    Posted 12 years ago #

  • jason@coopersco.com Member

    Hmmm, when I was trying it with PASV checked it worked but produced the same Invalid PORT Command errors. This morning it did this instead:

    System Version = 0x910
    Connecting to 64.174.156.98 port 22 (7/13/01 7:37:18 AM)
    220 digiserver1 Microsoft FTP Service (Version 4.0).
    ADAT
    500 'ADAT Hi there, do you support security?': command not understood
    USER jason
    331 Password required for jason.
    PASS
    230 User jason logged in.
    SYST
    215 Windows_NT version 4.0
    PWD
    257 "/" is current directory.
    MACB ENABLE
    500 'MACB ENABLE': command not understood
    SITE DIRSTYLE
    200 MSDOS-like directory output is on
    SITE DIRSTYLE
    200 MSDOS-like directory output is off
    PWD
    257 "/" is current directory.
    PWD
    257 "/" is current directory.
    PASV
    227 Entering Passive Mode (192,168,1,100,16,11).
    LIST
    426 Connection closed; transfer aborted.
    ftp_list: -30000 (state == GETTING_LIST)
    NOOP
    200 NOOP command successful.
    NOOP
    200 NOOP command successful.
    NOOP
    200 NOOP command successful.
    NOOP
    200 NOOP command successful.

    Posted 12 years ago #

  • Jim Matthews Administrator

    Okay, now I see what's going on. You are using Network Address Translation, presumably to share one Internet address among multiple computers. Apparently the NAT router knows about FTP on port 21, and so can translate the addresses in PORT and PASV commands. But it doesn't know about doing FTP on port 22, so that fails.

    I'd recommend contacting the NAT router vendor, to see if they have a way around the problem.

    Jim Matthews
    Fetch Softworks

    Posted 12 years ago #

  • jason@coopersco.com Member

    Would that be the NAT router on my end (letting us share a single DSL connection between a couple Macs) or on the server end (which I though wasn't doing any NAT for the FTP server, but maybe I'm wrong)?

    Posted 12 years ago #

  • Jim Matthews Administrator

    My guess would be the NAT on your end, sharing your DSL line.

    Jim Matthews
    Fetch Softworks

    Posted 12 years ago #

  • jason@coopersco.com Member

    You are right! Thanks; I added port 22 as a non-standard FTP port on my NAT router and everything now works fine.

    Posted 12 years ago #

Topic closed

This topic has been closed.