Path: utzoo!news-server.csri.toronto.edu!cs.utexas.edu!swrinde!zaphod.mps.ohio-state.edu!magnus.acs.ohio-state.edu!tut.cis.ohio-state.edu!ucbvax!ASYLUM.SF.CA.US!romkey
From: romkey@ASYLUM.SF.CA.US (John Romkey)
Newsgroups: comp.protocols.tcp-ip
Subject: FTP ISC 2.2 Woes.
Message-ID: <9103161737.AA06656@asylum.sf.ca.us>
Date: 17 Mar 91 01:37:40 GMT
References: <808@essnj1.ESSNJAY.COM>
Sender: daemon@ucbvax.BERKELEY.EDU
Reply-To: romkey@asylum.sf.ca.us
Organization: The Internet
Lines: 16

Here's a guess...

SCO uses Lachman's TCP. ISC bought Lachman (much to SCO's
consternation, I expect). I see a similar problem on my SCO system
sometimes. One thing that brings it out is if my system can't resolve
the hostname of the client. So, verify that it can resolve your
client's hostname (try telneting to the ISC system and then netstat to
see if the name is listed). If it can't, try reconfiguring your system
so it can and try it again.

I doubt *very* much that it's a hardware problem. If it is, it's
probably something like an ethernet board that drops packets and is
consistently dropping a packet. Are you using a 3C501? Anyway, I do
doubt it's a hardware problem.
		- john romkey			Epilogue Technology
USENET/UUCP/Internet:  romkey@asylum.sf.ca.us	voice/fax: 415 594-1141