Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.2 9/18/84; site qantel.UUCP
Path: utzoo!watmath!clyde!bonnie!akgua!mcnc!philabs!prls!amdimage!amdcad!amd!vecpyr!lll-crg!dual!qantel!stv
From: stv@qantel.UUCP (Steve Vance@ex2499)
Newsgroups: net.dcom,net.bugs.uucp
Subject: Re: Micom 224+ problems
Message-ID: <421@qantel.UUCP>
Date: Sat, 20-Apr-85 02:36:54 EST
Article-I.D.: qantel.421
Posted: Sat Apr 20 02:36:54 1985
Date-Received: Mon, 22-Apr-85 07:31:43 EST
References: <306@linus.UUCP> <403@mnetor.UUCP>
Reply-To: stv@qantel.UUCP (Steve Vance@ex2499)
Distribution: net
Organization: MDS Qantel, Hayward, CA
Lines: 22
Xref: watmath net.dcom:946 net.bugs.uucp:517
Summary: 

In article <403@mnetor.UUCP> clewis@mnetor.UUCP (Chris Lewis) writes:
>We are encountering a very similar problem when our Pyramid (BSD4.2
>uucp) trys to converse with System V's (VME10 and EXORmacs using
>dialup or direct lines).  They *always* TIMEOUT.  We don't have this 
>problem when conversing with other BSD4.2s...  

I believe that this is a different problem.  When System V came out,
early Unisoft ports of every flavor had a bug in uucp, whereby they
could only talk to other Unisoft-System-V machines.  You have described
the symptoms precisely--connection is made, then the System V side does
not respond further, then timeout occurs.  I have heard that a patch
has been available to fix this for over a year.  You'll have to talk to
your system supplier--Unisoft won't talk to you directly.  In our
situation, we are out of luck, since our system supplier seems to have
gone belly-up.  Good thing we had the wherewithall to just junk the
machine.
-- 

Steve Vance
{dual,hplabs,intelca,nsc,proper}!qantel!stv
dual!qantel!stv@berkeley
Qantel Corporation, Hayward, CA