Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!uwm.edu!psuvax1!psuvm!XLNVAX!RONC
From: ronc@XLNVAX.EXCELAN.COM (Ron Cully)
Newsgroups: bit.listserv.novell
Subject: Re:  novell on token ring
Message-ID: <9001162027.AA08512@la.excelan.com>
Date: 16 Jan 90 20:27:20 GMT
Sender: Novell LAN Interest Group <NOVELL@SUVM>
Reply-To: Novell LAN Interest Group <NOVELL@SUVM>
Lines: 59
Approved: NETNEWS@PSUVM Gateway
X-To:         NOVELL%SUVM@pucc.PRINCETON.EDU


  > We are currently looking into ways to connect a Novell network
  > (which is using IBM token-ring adapters) onto a TCP/IP network.
  > I am aware of Wollongong and Interlan software available to do
  > this.  Has anyone else tried modifying the Clarkson "stuff" to
  > do this, or have you found any other ways to accomplish this?
  >
  > Maria Neugebauer
  >

When you say you want to connect a Novell network, what exactly
do you mean.  There are many different aspects of connecting
a Novell network to TCP/IP.  Do you mean you want IPX over TCP/IP
routing, do you want TCP/IP client access from NetWare clients,
do you want TCP/IP host access to NetWare servers, etc..

There is one way for you to connect into TCP/IP networks for
a number of things if you have a VAX and are willing to purchase
some software for it.  In your situation, you can install a
NetWare router (formerly and incorrectly known as a bridge)
so you connect the Novell network to a Ethernet network.  On
the Ethernet, you install a VAX with NetWare for VMS, LAN Service
NFS, and either Multinet or LAN Service for VMS (TCP/IP host
based and front-end-processor based respectively).  All of these
products are available from Novell.  Alternately, you can use
another TCP/IP implmenetation on the VAX (if one all ready exists)
like Wollongong, DEC, CMC etc..  LAN Service NFS will work with
Wollogong and DEC, but other transport dependent NFS implmentations
(like Wollongong's) should work too.  I have experience with the
LAN Service NFS, Multinet, and NetWare for VMS configuration and
I recommend it (but then I'm biased being from Novell).

Anyway, with the VAX configured this way, you get the
following functionality:

1. NetWare clients see the VAX as a typical NetWare server
2. NetWare clients can use TES to log directly into the VAX.
   From there, the NetWare user is effectively a remote
   terminal to the VAX and the user has access to all VAX
   applications.  Hence, the user can then Telnet from the
   VAX to any other TCP/IP hosts and FTP files to/from other
   non-NFS hosts.  The user also has access to SMTP mail.
3. NFS clients (e.g. Suns or PCs with PC-NFS) on the Ethernet
   can mount volumes on the VAX.  These volumes can be the
   same directories used by the NetWare clients.  Hence, NFS
   clients and NetWare clients can share files.  Conversely,
   NetWare clients can access files deposited by the NFS clients.
4. Non-NFS TCP/IP hosts can access NetWare files on the VAX
   through FTP.

This may be too expensive for some sites but it does offer
a lot of unique functionality which is unavailable otherwise
(at least to date).

Hope this offers something useful (if not to you, someone else).

Ron Cully
Product Marketing Engineer
NetWare for VMS