Your best friend for file transfer.

Fetch application logoFetch

new version work with MacOSX firewall? (4 posts)

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

    I just updated to 5.1 from an older version of 5, and now I can't transfer files when my MacOSX firewall is on. I can browse files on the server, but can't upload or download, the wheel just spins. Turning off firewall allows it to work fine, but the previous version of Fetch was able to work with my firewall on. Is there a setting I need to change in the new version? I have already tried enabling PASV mode in Fetch, and also tried enabling PASV mode by clicking that button under Network in OSX. Neither works. Does anyone have any suggestions?

    Here is my transcript:
    PWD
    257 "/users/jmurray" is current directory
    SIZE murray-light.gif
    213 8432
    MDTM murray-light.gif
    213 20060529153340
    PORT 192,168,1,121,179,220
    200 command successful
    RETR murray-light.gif
    425 Can't open data connection.
    Active mode connection blocked by OS X firewall, port 46044
    PORT 192,168,1,121,96,9
    200 command successful
    RETR murray-light.gif
    Unsuccessful transfer of murray-light.gif (0 bytes, 0 bytes/sec, 0:40 elapsed) stopped at 6/16/06 2:30:08 PM (error: -128)
    ABOR
    226 abort successful
    425 Can't open data connection.

    Posted 8 years ago #

  • Scott McGuire Administrator

    Hi James,

    If earlier versions of Fetch 5 worked for you with your firewall, Fetch 5.1 should too.

    Could you check the PASV checkbox in Fetch, try to connect to your server, and then post the entire transcript?

    Thanks,

    Scott McGuire
    Fetch Softworks

    Posted 8 years ago #

  • James Murray Member

    Actually, it is working fine now. Not sure what changed. All is well.

    An unrelated problem is that it is possible that the upgrade caused Fetch to use my old password somehow. For another FTP site, it stopped working entirely for me. They eventually reset my password and it worked fine. Maybe Fetch is getting confused (or I am) when the new version looks for passwords in the Keychain vs in the Favorites?

    Posted 8 years ago #

  • Jim Matthews Administrator

    If you previously had a correct password stored in the keychain, and an incorrect password stored in the shortcut, upgrading to 5.1 could result in the correct password being replaced by the incorrect one. The fix, as you discovered, is to enter the correct password in your shortcut in Fetch 5.1.

    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.