Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!ucbvax!VAX.FTP.COM!jbvb
From: jbvb@VAX.FTP.COM (James Van Bokkelen)
Newsgroups: comp.protocols.tcp-ip.ibmpc
Subject: Re: HELP: Novell Netware Network <---> TCP/IP Network (long)
Message-ID: <8908251319.AA00582@vax.ftp.com>
Date: 25 Aug 89 13:19:19 GMT
References: <8908241213.aa05666@louie.udel.edu>
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: The Internet
Lines: 25

As things are right now, there are two ways you can get TCP/IP access
from the workstations:

1. Via the Interlan server-based gateway product (add-in board in the server).
2. Via the Wollongong IP-over-NETBIOS and a separate PC with two network
   interfaces.

In either case, the Netware thin Ethernet could either be connected directly
to the backbone, or left separate (the netware traffic really won't have
much impact on a backbone with only 30 hosts, but the backbone could have
an effect on the Netware people if your Suns are paging over the net).

You could use the BYU Netware if 1) you were willing to boot your workstations
from the floppy, instead of over the net, and 2) if there were a Packet Driver
for the NE1000 (I don't know of one), but it would require that the Netware
cable be bridged onto the backbone cable. 

If your Netware vendor was willing to build a Packet Driver into IPX.COM
(like Interlan, Schneider & Koch, Hughes LAN Systems, IMC Networks and
others have), you could continue to boot the workstations over the net.
In either case, the Packet Driver gives you a fairly wide choice of p-d
and commercial TCP/IP packages.

James B. VanBokkelen		26 Princess St., Wakefield, MA  01880
FTP Software Inc.		voice: (617) 246-0900  fax: (617) 246-0901