Path: utzoo!mnetor!uunet!lll-winken!lll-tis!ames!ll-xn!mit-eddie!uw-beaver!ssc-vax!bcsaic!vader!bcs212
From: bcs212@vader.UUCP (Vince Skahan)
Newsgroups: comp.mail.uucp
Subject: Re: Why does UUCP "HANDSHAKE FAILED" when calling a 3B2?
Message-ID: <158@vader.UUCP>
Date: 12 Mar 88 12:41:40 GMT
References: <8366@eddie.MIT.EDU> <16516@pyramid.pyramid.com>
Organization: Boeing Computer Services - Phila.
Lines: 22
Summary: thanks for the info

In article <16516@pyramid.pyramid.com>, csg@pyramid.pyramid.com (Carl S. Gutekunst) writes:
> It means that the 3B2 does not have your login name in its USERFILE (if it is
> an old machine) or Permissions (if it is running Basic Networking Utilities.)
> 
> The key is the reply to the initial handshake. It should be:
...[lots of other good stuff]...
> 
> [Hey Spaf, when are you going to add this to the list of "most frequently asked
> questions on the Usenet" ? :-)]


As far as I'm concerned, remove the :-) from the last line above and do
just that !!! I know many of you folks out there have access to the
source code but many (like poor old me and the other Apollo workstation
users) don't.  Having this sucker on-line would be a great aid.
(for example, it will probably help me fix a certain site I'm trying to
get connected to who can't get his UUCP to dial out and I can't get in
because I get one of the messages CSG explained above).

-- 
     Vince Skahan            Boeing Computer Services - Phila.
    (215) 591-4116           INTERNET:  bcs212%psev@boeing.com
UUCP: {...rutgers!bpa | uw-beaver!uw-june!bcsaic}!vader!bcs212