Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!sharkey!math.lsa.umich.edu!zaphod.mps.ohio-state.edu!brutus.cs.uiuc.edu!psuvax1!psuvm!CORNELLA!NJG
From: NJG@CORNELLA.BITNET (Nick Gimbrone)
Newsgroups: bit.listserv.ibmtcp-l
Subject: Re: Loopback problems
Message-ID: <IBMTCP-L%90020323020399@CUNYVM>
Date: 4 Feb 90 03:53:45 GMT
Sender: IBM TCP/IP For VM List <IBMTCP-L@CUNYVM>
Reply-To: IBM TCP/IP For VM List <IBMTCP-L@CUNYVM>
Lines: 20
Approved: NETNEWS@PSUVM Gateway
In-Reply-To:  Message of Wed, 31 Jan 90 08:54:49 PST from <SPGMNF@UCBCMSA>

On Wed, 31 Jan 90 08:54:49 PST Mike Friedman said:
>So, if NETSTAT is to be believed, there is no data transfer going on.
>Why is this?  As I said in an earlier note, if I connect to LOOPBACK,
>instead of cmsa.Berkeley.EDU, I have no trouble.  Also, since putting
>the 8232 into production Sunday, I'm not aware of any file transfer
>problems between us and a different host.
LOOPBACK is a software transfer (the IP packets never leave the TCPIP
server, who pretends to send them on the network and then pretends
to recieve them from the network by simply moving the packet from the
IP output queue to the IP input queue... basicly speaking...). Use of
either the host name or IP address will cause the same code paths as
use of another host name or IP address (i.e. IP packets actually hit
the network attachment box). With both 7170s and 8232s (I don't know
about other boxes) these packets will actually be sent on the real
network and then recieved by the sender...

So, could it be that you have a hardware problem with your 8232's
network card? Some cards can't recieve data from themselves reliably...
yet they can talk to others just fine... seems to match your symptoms.
(Hum, must be a software type... blaming the hardware again! :-)