Your best friend for file transfer.

Fetch application logoFetch

Return to Message Board

Subscribe to RSS Feed for Fetch Message Board Fetch Message Board

  1. Page 1

POSIX Error 51 (11 posts)

  • Started 14 years ago by rhegyi
  • Latest reply 13 years ago from Jim Matthews
  • rhegyi Member

    I'm connecting via Fetch to an Apple Xserve running 10.6.3. I configured the FTP service to use FTP Root and share Points. I set up an ftpuser and a Share FTPshare. I gave the box a 192.168.1.33 inside address. In the router I mapped an outside address to point to the 192.168.1.33 address. When I connect inside using the .33 address I can get in via Fetch without issue, I can get and put files. If I connect via the outside address I get. "connecting - POSIX Error 51, entering passive mode, 192,168,1,33,106,4. I'm connected but can't see any files. Can anyone let me know what's going on here? thanks, Rick

    Posted 14 years ago #

  • Scott McGuire Administrator

    Hi Rick,

    In order to give the best advice, we'd like to see a full transcript of your attempt to connect to the server with the outside address.

    So could you please do the following?

    * Quit Fetch.
    * Open Fetch again.
    * Try connecting to your server.
    * After you receive the error, go to the Window menu, and choose Fetch Transcript.
    * Copy the entire contents of the transcript window, and paste them into a reply to this message.

    We'll take a look and see if we can provide advice.

    Thanks,

    Scott McGuire
    Fetch Softworks

    Posted 14 years ago #

  • rhegyi Member

    Fetch 5.5.3 (5E778) Intel running on Mac OS X 10.6.3 (10D573) Intel English
    StuffIt Engine 0x820, StuffIt SDK Version 10.1.1b1
    Expires 4/17/10 T
    Connecting to 98.168.127.9 port 21 (Mac OS X firewall is allowing connections) (4/9/10 2:37 PM)
    Connecting to 98.110.127.9 port 21 (Mac OS X firewall is allowing connections) (4/9/10 2:37 PM)
    Connected to 98.110.127.9 port 21 (4/9/10 2:37 PM)
    220--------------------------------------------------------------------------------
    220-Please enter your FTP username and Password.
    220-
    220--------------------------------------------------------------------------------
    220-
    220 new-host-18.home FTP server ready.
    USER ftpuser
    331 Password required for ftpuser.
    PASS
    230-No directory! Logging in with home=/
    230--------------------------------------------------------------------------------
    230-Welcome to the Hartz Mountain FTP Server.
    230-
    230--------------------------------------------------------------------------------
    230-
    230 User ftpuser 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 (192,168,1,33,16,126)
    Making data connection to 98.110.127.9 port 4222
    ftp_setup_dataconn() passive mode dataconn failed, result = 1,51
    PORT 192,168,1,15,193,20
    500 Illegal PORT Command
    ftp_list: 1,51 (state == GETTING_LIST)
    Update check skipped at 4/9/10 2:38 PM (next check after 4/10/10 3:39 AM)
    PWD
    257 "/" is current directory.

    Posted 14 years ago #

  • Jim Matthews Administrator

    Hi Rick,

    Running an FTP server on a private IP address (e.g. 192.168.1.33) is difficult. In the transcript above your server told Fetch to make a passive mode data connections to port 4222 of 192.168.1.33, but of course that address is not accessible outside your network. Fetch tries to be clever and attempts to connect to port 4222 at 98.110.127.9 (your public address) instead, but your router does not know to forward that connection to your server.

    I would look into configuring your FTP server to use a certain range of ports for data connections (e.g. 4000-4999). Then configure your router to forward all of those ports to the Xserve at 192.168.1.33.

    Let us know how it goes.

    Thanks,

    Jim Matthews
    Fetch Softworks

    Posted 14 years ago #

  • rhegyi Member

    Jim:

    Thanks for the reply. I'll give that a shot and let you know. Again, thanks for the quick response.

    Rick

    Posted 14 years ago #

  • rhegyi Member

    Jim,

    I added ports 4000-4999 as you suggested on the router to point to 192.168.1.33.

    I turned on the OSX server firewall and added those ports as well. This is what I got.

    Fetch 5.5.3 (5E778) Intel running on Mac OS X 10.6.3 (10D573) Intel English
    StuffIt Engine 0x820, StuffIt SDK Version 10.1.1b1
    Expires 4/17/10 T
    Connecting to 98.110.127.9 port 21 (Mac OS X firewall is allowing connections) (4/13/10 11:12 AM)
    Connected to 98.110.127.9 port 21 (4/13/10 11:12 AM)
    220--------------------------------------------------------------------------------
    220-Please enter your FTP username and Password.
    220-
    220--------------------------------------------------------------------------------
    220-
    220 new-host-18.home FTP server ready.
    USER ftpuser
    331 Password required for ftpuser.
    PASS
    230-No directory! Logging in with home=/
    230--------------------------------------------------------------------------------
    230-Welcome to the Hartz Mountain FTP Server.
    230-
    230--------------------------------------------------------------------------------
    230-
    230 User ftpuser 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 (192,168,1,33,169,194)
    Making data connection to 98.110.127.9 port 43458
    ftp_setup_dataconn() passive mode dataconn failed, result = 1,51
    PORT 192,168,1,25,204,59
    500 Illegal PORT Command
    ftp_list: 1,51 (state == GETTING_LIST)
    QUIT
    send_cmd():con_conn->Putline() returns 2,-50

    Did it now try using port 43458?
    I'm getting confused.
    Thanks,
    Rick

    Posted 14 years ago #

  • Jim Matthews Administrator

    Hi,

    You need to configure the FTP server to only use ports 4000-4999 for passive data connections, since those are the ports that will be forwarded from the router to the server. I do not know off the top of my head how to configure the Xserve FTP server to only use certain ports. If you do not find that information in the documentation, let me know, and I'll see if I can help.

    Thanks,

    Jim Matthews
    Fetch Softworks

    Posted 14 years ago #

  • rhegyi Member

    Hey Jim:

    O.K. I tired turning on the OSX server firewall and opening up those ports 40000-49999. I changed the port mapping on the router. Didn't work so I ditched the OSX firewall.

    This is what I get:
    Using 192.168.1.33 - I get in and can get and put files, no problem. I try it via the outside address and I get the following:
    Connecting to 98.110.127.9 port 21 (Mac OS X firewall is allowing connections) (4/13/10 2:35 PM)
    Connected to 98.110.127.9 port 21 (4/13/10 2:35 PM)
    220--------------------------------------------------------------------------------
    220-Please enter your FTP username and Password.
    220-
    220--------------------------------------------------------------------------------
    220-
    220 new-host-18.home FTP server ready.
    USER ftpuser
    331 Password required for ftpuser.
    PASS
    230-No directory! Logging in with home=/
    230--------------------------------------------------------------------------------
    230-Welcome to the Hartz Mountain FTP Server.
    230-
    230--------------------------------------------------------------------------------
    230-
    230 User ftpuser 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 (192,168,1,33,193,215)
    Making data connection to 98.110.127.9 port 49623
    ftp_setup_dataconn() passive mode dataconn failed, result = 1,51
    PORT 192,168,1,25,218,182
    500 Illegal PORT Command
    ftp_list: 1,51 (state == GETTING_LIST)
    QUIT
    221-You have transferred 0 bytes in 0 files.
    221-Total traffic for this session was 103 bytes in 0 transfers.
    221-Thank you for using the FTP service on new-host-18.home.
    221 Goodbye.

    It says connected but I can not see any files or put any files. I'm close.....close doesn't cut it.

    Thanks,
    Rick

    Posted 14 years ago #

  • Jim Matthews Administrator

    Do you have access to the server logs? Do see any information there?

    Thanks,

    Jim Matthews
    Fetch Softworks

    Posted 14 years ago #

  • rhegyi Member

    Jim / Sott:

    I wanted to get back you and let you know I think I figured it out ( Maybe ).

    I think I was getting the POSIX 51 error because I was running Fetch from my Mac that was on the non routing I.P. sub net 192.168.X.X then telling fetch to go to the outside address then back in port mapping to the 192.168.1.33 address. I found this out by connecting into my home mac via back to my mac then running Fetch from there and BAM! no problem with POSIX errors! I hope that I was clear? Does that make any sense?

    Thanks for your response,
    RIck

    Posted 13 years ago #

  • Jim Matthews Administrator

    Thanks for the update, Rick, it's good to hear that it's working now.

    Jim Matthews
    Fetch Softworks

    Posted 13 years ago #

  1. Page 1

Return to Message Board

Reply

  • Or nickname, if you prefer.
  • This will be kept confidential.
  • This is to ensure that you’re a person, not a spambot.