Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!usc!zaphod.mps.ohio-state.edu!pacific.mps.ohio-state.edu!linac!mgweed!prg
From: prg@mgweed.UUCP (Gunsul)
Newsgroups: comp.sys.att
Subject: Re: 3b1 uucp problem
Summary: Hummmm...
Message-ID: <7043@mgweed.UUCP>
Date: 20 Dec 90 16:59:40 GMT
References: <1990Dec20.042245.10942@mel.dit.csiro.au>
Organization: AT&T Montgomery Works, Montgomery, IL
Lines: 30

In article <1990Dec20.042245.10942@mel.dit.csiro.au>, hal@manta.mel.dit.csiro.au (Harold A. Miller) writes:

> 
> This only happens on Sun-to-3b1 traffic.  All 3b1-to-Sun works, including
> the bidirectional protocol negotiation and acks.  I keep thinking it might
> have something to do with flow control, but I haven't figured out where it
> could be failing, nor why it works on the Tek.
> 
  
> Thanks.
> HM
> -- 
> -- 
> |Hal Miller, DIT, CSIRO, | Networking Environments Project               |
> |55 Barry St, Carlton,   | (TEL) +61 3 347 8644   (FAX) +61 3 347 8987   |
> |VIC 3053, Australia     | Internet:hal@mel.dit.csiro.au                 |
> Xref: cbnewse unix-pc.general:5792 comp.sys.att:6677

Gosh Hal, this sure sounds strange..  I'm not a bit familiar with any
of the Sun systems, but one thing popped into my mind when I read
this -- could the problem be with using the same port for inbound and
outbound traffic?  I'm not sure if the Sun has something like "uugetty"
for bi-directional uucp connections..  I've seen real strange things
happen on 3B type machines prior to HDB that had a "getty" running on
an "out-bound" port...

-- 
AT&T 		|	 This space		| (708)-859-4485
Phil Gunsul	|	intentionally		| att!mgweed!prg
Montgomery, IL	|	 left blank..		| AT&T Information Systems