Re: OT vs. socket calls on 10.2
Re: OT vs. socket calls on 10.2
- Subject: Re: OT vs. socket calls on 10.2
- From: "Peter Li" <email@hidden>
- Date: Sat, 07 Sep 2002 09:10:09 +1000
Jim,
Sounds like a fascinating challenge to solve this puzzle.
In case it wasn't a "spurious event", did you try rebooting the OS?
Another thing that comes to mind is maybe its a port range issue.
Maybe command line FTP uses/binds to lower ports locally and OT apps from
Carbon use higher ports and maybe Classic OT apps use yet another different
port range.
It may be that something is allowing certain port ranges but not others out.
Or looking at it another way the server the user is connecting to has a
firewall that only allows incoming connections from a certain port range at
the remote end (the FTP client end).
Since Fetch Classic works under OSX, and since Fetch 3.0.3 supports
specifying port ranges to use, why not try a port range that command line
FTP appears to use.
Its a pity the "shift key down at startup" does not apply to OSX.
Another test may be to test FTP'ing in PASV mode to themselves (enable FTP
server on OSX) and see if that works. I don't think firewalls can firewall
yourself out of your own box. If that works then its most probably a
firewall setting somewhere. Its just a matter of finding out where. Also,
since OSX 10.2 has its own firewall, maybe its enabled and maybe its
conflicting with Norton's Firewall?
I will be curious to know the cause of this problem when its resolved.
Regards,
Peter
--
+-------------------------------------------------------+
| Peter LI (B.Sc B.E., The University of Sydney) |
| e-mail: email@hidden |
|
http://www.ozemail.com.au/~pli/netfinder/ |
+-------------------------------------------------------+
Written on 100% recycled electrons.
>
At 10:11 AM -0700 9/5/02, Vincent Lubet wrote:
>
>The OT framework is just using the straight BSD Sockets API and --
>
>beside evil patching of the OT framework -- no firewall should
>
>affect OT but not the Sockets.
>
>
Experience suggests that Norton Personal Firewall does just that
>
(patches the OT framework) -- how would I tell for sure?
>
>
>It would be useful to know exactly how this is failing and where.
>
>
Here's a transcript from a successful data connection with the
>
command line ftp client (with the debug flag set, to provide the
>
transcript, and the addresses cloaked for privacy):
>
>
---> PASV
>
227 Entering Passive Mode (xxx,1,243,79,7,141)
>
---> LIST
>
150 Data connection accepted from yyy.3.241.218:29084; transfer starting.
>
>
Here's a transcript from Fetch 4.0.2; SimpleFTP, Captain FTP and
>
NetFinder all report the same error:
>
>
PASV
>
227 Entering Passive Mode (xxx,1,243,79,17,49)
>
LIST
>
550 Could not accept passive data connection - timed out.
>
>
This is happening on a customer's machine, so I can't easily monitor
>
packet traffic, but it certainly looks as if Fetch's attempt to
>
establish the data connection isn't leaving the machine. If it was
>
getting out, what would block it (and not similar data connections
>
from the command line client)?
>
>
Thanks,
>
--
>
Jim Matthews
>
Fetch Softworks
>
http://fetchsoftworks.com
_______________________________________________
macnetworkprog mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/macnetworkprog
Do not post admin requests to the list. They will be ignored.