Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!know!zaphod.mps.ohio-state.edu!brutus.cs.uiuc.edu!ux1.cso.uiuc.edu!pequod.cso.uiuc.edu!dorner
From: dorner@pequod.cso.uiuc.edu (Steve Dorner)
Newsgroups: comp.sys.mac.comm
Subject: Re: Problem with MacTCP & documentation for MacTCP.
Message-ID: <1990Jul25.142159.16148@ux1.cso.uiuc.edu>
Date: 25 Jul 90 14:21:59 GMT
References: <11012@chaph.usc.edu> <1990Jul24.224344.9702@ux1.cso.uiuc.edu>
Sender: usenet@ux1.cso.uiuc.edu (News)
Reply-To: dorner@pequod.cso.uiuc.edu (Steve Dorner)
Distribution: na
Organization: University of Illinois at Urbana-Champaign
Lines: 18

In article <1990Jul24.224344.9702@ux1.cso.uiuc.edu> resnick@lees.cogsci.uiuc.edu (Pete Resnick) writes:
>The error code -23015 is listed as openFailed. This is indicative of
>a connection that started to open but did not complete in the specified
>timeout period. That means that this particular host is taking longer
>than most to get a connection.

Actually, all it means is the connection "ain't happening".  It might
be a timeout, but it also might be a connection refused, or a net
unreachable; MacTCP doesn't discriminate.  This is a pain, because
you can't give good error messages.

In all fairness, MacTCP is too low-level to give you a "net unreachable"
error in the open call itself, as that comes in over ICMP.  But to not
distinguish between "nobody home" and "somebody actively barring the door"
is unfortunate.
--
Steve Dorner, U of Illinois Computing Services Office
Internet: s-dorner@uiuc.edu  UUCP: {convex,uunet}!uiucuxc!dorner