Your best friend for file transfer.

Fetch application logoFetch

failed ftp outbound on NAT'd LAN (7 posts)

  • Started 8 years ago by rennyo
  • Latest reply 8 years ago from Jim Matthews
  • rennyo Member

    I'm having a problem using a Mac to ftp out with Fetch. Normally this is resolved on a pc using MS proxy client, which performs DNS duties and makes internal sockets visible to extranets. Is there such an equivalent for Mac? I was using PASV and it still doesn't work.

    Posted 8 years ago #

  • Scott McGuire Administrator

    Hi,

    Does your LAN have a firewall on it?

    If you normally have to specify proxy settings when using FTP on Windows, you might need to set proxy settings in Fetch too - you can do this using the Proxy pane of the Fetch Preferences.

    But before you poke at the Proxy settings, could you try to make a connection, and after it either times out or you get an error message, could you please choose Fetch Transcript from the Window menu, copy the entire contents of the transcript window, and paste them here? We'll take a look and see if we can figure out what you need to do.

    Thanks,

    Scott McGuire
    Fetch Softworks

    Posted 8 years ago #

  • rennyo Member

    [QUOTE]Originally posted by ScottMcGuire:
    [B]Hi,

    Does your LAN have a firewall on it?

    Scott, thanks--yes it does. Ports 80 and 21 are bidirectionally enabled, and normally the MSPCL resolves the problem of outbound ftp for us. I'll get back to you after trying your suggestion.

    Posted 8 years ago #

  • rennyo Member

    It never seems to time or error out.

    Fetch 5.1 (5B286) PowerPC running on Mac OS X 10.4.7 (8J135) PowerPC English
    StuffIt Engine 0x820, StuffIt SDK Version 10.1.1b1
    Partial serial FETCHEX001-FA66-WMPX T
    Using SOCKS v5 gateway host: 172.17.1.18, port: 1080
    Connecting to varidoc.zftp.com port 21 (OS X firewall is off) (7/13/06 10:10:38 AM)
    Update check started at 07/13/2006 10:12 AM
    Update check skipped at 07/13/2006 10:13 AM (next check after 07/14/2006 06:24 AM)
    Using SOCKS v5 gateway host: 172.17.1.18, port: 1080
    Connecting to 204.60.194.82 port 21 (OS X firewall is off) (7/13/06 10:32:13 AM)
    Using SOCKS v5 gateway host: 172.17.1.18, port: 80
    Connecting to 204.60.194.82 port 21 (OS X firewall is off) (7/13/06 10:34:03 AM)
    Using SOCKS v5 gateway host: 172.17.1.18, port: 80
    Connecting to 204.60.194.82 port 21 (OS X firewall is off) (7/13/06 10:46:28 AM)

    Posted 8 years ago #

  • Scott McGuire Administrator

    Hi,

    I see that you've set up Fetch to use a SOCKS5 proxy. Was that deliberate?

    And if so, does the proxy require a username and password?

    Thanks,

    Scott McGuire
    Fetch Softworks

    Posted 8 years ago #

  • rennyo Member

    I was told it had to be SOCKS5. It shouldn't require a username and password

    Posted 8 years ago #

  • Jim Matthews Administrator

    To debug this problem I would need a packet trace. You can collect one by running Terminal and typing

    sudo tcpdump -i en0 -s 0 -w DumpFile.dmp

    You will be prompted for your administrator password. Then try to connect with Fetch. Then, when that has failed, type Control-C in Terminal and email the DumpFile.dmp file to bugs at fetchsoftworks dot com. I'll take a look and see if I can figure out what is going wrong.

    Thanks,

    Jim Matthews
    Fetch Softworks

    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.