Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!rutgers!apple!vsi1!wyse!mips!prls!philabs!linus!raybed2!rayssd!mirror!frog!barr
From: barr@frog.UUCP (Chris Barr)
Newsgroups: comp.protocols.tcp-ip.ibmpc
Subject: Novell & TCP/IP integration
Summary: Successful INTERLAN tcp/ip -> Novell
Message-ID: <1420@frog.UUCP>
Date: 13 May 89 01:00:00 GMT
References: <mcvax!huldra!haho@UUNET.UU.NET> <8905110833.aa03916@louie.udel.edu>
Organization: Charles River Data Systems, Framingham MA
Lines: 21

DOBEIRNE@IRLEARN.BITNET (Dermot O'Beirne) writes:
> >Netware TCP/IP Option (MICOM-INTERLAN).
> From any accounts I have heard I would keep clear of this. Maybe its just
> the lack of support here but one site I know looking for just vt100 and

One Interlan site I spoke with today says 
  a) they had several bugs fixed last year in NP600 tcp code (NP627)
  b) now use sockets mostly, but also FTP as follows:

                               PC AT (np600)
                                / \
                               /   \
                    TCP/IP mini     Novell NW file server (N5210)

The PC can 
  a) logon to Netware server
  b) FTP logon to the mini
  c) ftp a file from the mini to the Novell server,
     by specifiying server drive prefix in filename

Interlan's tcp code was originally written for VAX tcp/ip.