Xref: utzoo comp.dcom.lans:1918 comp.dcom.modems:2655 comp.protocols.tcp-ip.ibmpc:840 comp.sys.ibm.pc:20139
Path: utzoo!attcan!uunet!portal!cup.portal.com!mhyman
From: mhyman@cup.portal.com
Newsgroups: comp.dcom.lans,comp.dcom.modems,comp.protocols.tcp-ip.ibmpc,comp.sys.ibm.pc
Subject: Re: Communication problems involving PC-Interface and Procomm /
Message-ID: <9925@cup.portal.com>
Date: 10 Oct 88 15:40:29 GMT
References: <1053@rivm05.UUCP> <13035@cisunx.UUCP>
Organization: The Portal System (TM)
Lines: 19
XPortal-User-Id: 1.1001.2549

In article <13035@cisunx.UUCP> jlfox@cisunx.UUCP (James L Fox) says
> hen he runs kermit he gets what appear to be flow control problems
> resulting in a messed up screen display...
> ...  I'm using an IBM-PC/XT with a 3COM 3C501
> board running SUN's PC-NFS and kermit v2.30 and I'm experiencing alomost
> identical symptoms to yours. I'm on a thinwire with a SUN 3 local host.


I've seen the same problem running an IBM AT, PC NFS, and a home grown
comm program.  However, The problem only occurs on com2.  Also, re-booting
and *not* logging in seems to solve the problem.  You can then use the 
"net name" command to log in.  Also,  I've never seen the problem using
"telnet com[12]".

--Marc

....
Marco S. Hyman			mhyman@cup.portal.com
				...!sun!portal!cup.portal.com!mhyman