Your best friend for file transfer.

passive address trouble (2 posts)
- Started 17 years ago by WHITE
- Latest reply 17 years ago from Scott McGuire
-
WHITE Member
-
Scott McGuire Administrator
Hi,
The problem is the second server you're trying to connect to does not support passive connections (each server handles passive connections differently).
So when Fetch discovers that that server doesn't support passive connections, it automatically tries an active connection, which also fails, because your Mac OS X firewall is on (active connections do not work with the Mac OS X firewall).
Unfortunately, the only way to connect to that server is to turn off your Mac OS X firewall temporarily - once you're done working with the server, you can turn it back on. (To turn the firewall off, go to the Mac OS X System Preferences, click the Sharing icon, click the Firewall tab, and click the Stop button.)
You can also ask the owners of that server to look into supporting passive connections.
Thanks,
Scott McGuire
Fetch Softworks
- Page 1
hi. i keep trying to get your to work. i've written you before.
with another client, much older one, i succeed.
i think because i can get a certain passive addresss.
with fetch it trys for a different passive address. any ideas?
partial transcript of other client:
PASV
227 Entering Passive Mode (192,168,0,2,16,57)
Connection established.
LIST
150 Opening ASCII mode data connection for /bin/ls.
440 Bytes transferred in 0:00:00 at 1 KB per second
Connection released.
226 Transfer complete.
partial transcript of fetch client:
TYPE A
200 Type set to A.
PASV
227 Entering Passive Mode (192,168,0,2,14,67)
Update check skipped at 05/27/2006 11:31 AM (next check after 06/01/2006 10:50 AM)
ABOR
226 ABOR command successful.
PORT 192,168,0,104,192,15
200 PORT Command successful.
LIST -al
150 Opening ASCII mode data connection for /bin/ls.
Active mode connection blocked by OS X firewall, port 49167
ABOR
426 Transfer aborted.
how can i stay in passive mode and get the right address?
Posted 17 years ago #