X-Envelope-to: BANYAN-L@VM1.CC.UAKRON.EDU
Newsgroups: bit.listserv.banyan-l
Date:         Mon, 6 Apr 1992 14:47:30 AES
From:         Ian=Brabham%CC%Monash@BANYAN.CC.MONASH.EDU.AU
Subject:      re: UNIX box on VINES
X-To:         BANYAN-L@VM1.CC.UAKRON.EDU

Jeffrey G. Brown

>We have a Token Ring network in our company offices and an Ethernet
>network in our shop and labs. ..... We would like to make it possible
>for our users to log into the UNIX box either through VINES or, at the
>very least, through the existing network.

You don't say whether your Token Ring is direct connected to the backbone
or only to a Vines server.  If it is only connected via a server then you
may need a TCP/IP routing option (TCP100) for that server or some other
method for getting IP packets out onto the backbone.  I have no personal
experience with T-R and there was a Banyan-L thread a little while ago
about T-R and TCP100 options not working.  I forget the outcome, someone
else maybe able to enlighten us as to the result.

>1) using the Banyan server as a router between the clients and the UNIX
>   box, using TCP/IP. How is this done? .... How much PC memory does this
>   require, compared (for example) to running Banyan's Token Ring drivers?

The TCP/IP routing option (TCP100) allows you to configure a Vines server
as an IP router such that it will pass IP packets from one of it's interface
to another.  The server routing functionality itself costs no memory in the
client PC's, but to use it you obviously need some client software which
will take memory.

>2) using a product called FTP, which I've been told runs both the VINES
>   IP and TCP/IP on the PC client. Is this a viable option? What is its
>   comparative memory requirement?

Banyan sell 2 (two) Vines specific version of FTP corp's PC/TCP software,
TCP120 - PC/TCP (PC's on non-Ethernet LANs) also known as IBANYAN and
TCP121 - PC/TCP (PC's on Ethernet LANs) also known as EBANYAN.

For your T-R users you will have to use TCP120 (IBANYAN) version.  The
TCP120 (ibanyan) version also requires a server somewhere in your network
to be running the TCP/IP routing option (TCP100) to convert the VinesIP
packets from the client into real TCP/IP packets for the Host.  [Both
options can be purchased together at a discount by ordering option TCP110]

Both PC/TCP versions use an unloadable TCP kernal which uses about 70-80K,
we provide Batch files to load the kernal, do a Telnet and unload the
kernal for our users.  The telnet application (TN.EXE) is about 210K plus
about 6-10K per extra session, all up about 300K.

>3) using another product called Power Fusion,

Sorry I don't know about this one.

Another options would be to use NDIS drivers or Packet Drivers with some
other Telnet package.  NDIS tends to be a bit of a pig to get working.

Here apart from PC/TCP we use Packet Drivers with Banyan's Cabletron
interface (available as a patch for 4.00 and 4.10, native in 4.11 and
unavailable as yet for Rev 5.00) together with many TCP/IP packages
like NCSA Telnet or the Clarkson varient, Trumpet News reader, WINQVTnet
for windows, etc

Ian Brabham                 email: ian@banyan.cc.monash.edu.au
Micro Support Group         phone: +61 3 565 4742
Monash University           fax:   +61 3 565 4746
Melbourne Australia
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU