Your best friend for file transfer.

Fetch application logoFetch

fetch access not working to firewall-protected server (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 10 years ago by wglass
  • Latest reply 10 years ago from wglass
  • wglass Member

    Hi,

    I'm a server administrator (Linux) and I just installed a software firewall (iptables). One of my users is using Fetch and all of a sudden he can't access the server. Is there a specific port that i need to let through to the server? (currently it's port 21).

    As a side note, other FTP clients can access the site (in passive mode). Fetch (v4.0.3) on his machine can't access the site in passive or active mode.

    Any suggestions?

    Thanks, WILL

    Posted 10 years ago #

  • Jim Matthews Administrator

    In passive mode the server has to be able to accept connections in the dynamic port range, 49152-65535. Could you post a transcript from one of these other FTP clients that is connecting in passive mode, and one from Fetch trying to connect in passive mode?

    Thanks,

    Jim Matthews
    Fetch Softworks

    Posted 10 years ago #

  • wglass Member

    Hi Jim,

    Thanks for the quick reply. iptables is supposed to allow this (a stateful related inbound connection) but I'm no iptables expert, I'll probably have to mess more with it. But it's odd that some programs work and some don't.

    Here's Fetch (v.4.0.3). Unsucessful (running dog as it tries to get file list)
    Fetch 4.0.3 System 0x1021 Expires 10/09/2003 TR
    Connecting to sportsbusinesssims.com port 21 (1/20/04 8:19:47 PM)
    220 ProFTPD 1.2.8 Server (ProFTPD) [forio.com]
    USER admin_sports
    331 Password required for admin_sports.
    PASS
    230 User admin_sports logged in.
    SYST
    215 UNIX Type: L8
    PWD
    257 "/" is current directory.
    MACB ENABLE
    500 MACB not understood
    PWD
    257 "/" is current directory.
    PWD
    257 "/" is current directory.
    PASV
    227 Entering Passive Mode (66,98,176,233,151,193).
    LIST
    421 No Transfer Timeout (300 seconds): closing control connection.
    ftp_list: -30001 (state == GETTING_LIST)
    QUIT
    send_cmd():con_conn->Putline() returns -3155

    Here's SmartFTP (v.1.0.978). Works in passive mode.
    Resolving host name sportsbusinesssims.com...
    Connecting to (sportsbusinesssims.com) -> IP: 66.98.176.233 PORT: 21
    Connected to (sportsbusinesssims.com) -> Time = 120ms
    Socket connected waiting for login sequence.
    220 ProFTPD 1.2.8 Server (ProFTPD) [forio.com]
    USER admin_sports
    331 Password required for admin_sports.
    PASS (hidden)
    230 User admin_sports logged in.
    SYST
    215 UNIX Type: L8
    FEAT
    211-Features:
    MDTM
    REST STREAM
    SIZE
    211 End
    PWD
    257 "/" is current directory.
    TYPE A
    200 Type set to A
    PASV
    227 Entering Passive Mode (66,98,176,233,157,250).
    Opening data connection IP: 66,98,176,233,157,250 PORT: 40442.
    The operation completed successfully.
    PORT 192,168,123,167,19,135
    200 PORT command successful
    Opening data connection IP: 192.168.123.167 PORT: 4999.
    LIST -aL
    150 Opening ASCII mode data connection for file list
    773 bytes received successfully. (773 B/s) (00:00:01).
    226-Transfer complete.
    226 Quotas off

    Posted 10 years ago #

  • Jim Matthews Administrator

    That transcript actually shows SmartFTP first trying passive mode (with the PASV command), and then giving up and using the PORT command instead. So it looks like passive mode won't work. I would try turning off passive mode in the Firewall section of Fetch Preferences. Also be sure to turn off your Mac OS X firewall, if you have that enabled.

    Thanks,

    Jim Matthews
    Fetch Softworks

    Posted 10 years ago #

  • wglass Member

    Ah. That explains why there was an unusual pause when SmartFTP logs in.

    Active mode didn't work for Fetch, but it could be the Mac OS X firewall. We'll try this.

    Thanks again.

    Posted 10 years ago #

Topic closed

This topic has been closed.