TCP does re-send packets. TCP sits on top of IP and
provides connection services.
It is up to the stack implementation
to track packets and re-send the missing ones.  We have seen
several instances of problems with the Novell stack for which
patches have been provided.  I don't know what the current
Novell TCP patch level is, but it is vital to ensure that
you're at the latest level.

Barry Fruchtman
ADSM Development

On Thu, 4 Apr 1996, Joe Morris wrote:

> On Thu, 4 Apr 1996, Jerry Lawson wrote:
>
> > I am NOT a network Guru (or evenclose to it), so perhaps someone who is 
> > closer
> > to that status can clarify for us.  However, I was under the problem that a
> > major difficulty with TCP/IP as a protocol, was that there was no ability 
> > to r
> > esend missing blocks (or are they called packets?).  Protocols such as SNA 
> > pay
> > the high overhead of doing this validity checking and retrying, but IP does
> > not.
>
> That's why I'm confused.  TCP/IP does resend failed packets (can't
> remember what layer does this) and performs some error checking to make
> sure the packet is not corrupted.  Putting the TCP issue aside, I'm still
> curious about missing blocks.  Think I might call this one in to tech
> support -- will let you know what I find out.
>
> BTW, I could not find the option to adjust the timeout.  Is this on the
> server or client side?
>
> BTW, to further clarify error:
>
> ANS4017E Session rejected: TCP/IP connection failure
> ___________________________________________________________
> Joe Morris - morris AT unc DOT edu - http://sunsite.unc.edu/morris
> OIT/Computing Systems, Development
> University of North Carolina at Chapel Hill
>