Path: utzoo!attcan!uunet!aplcen!samsung!cs.utexas.edu!yale!cmcl2!adm!lhc!ncifcrf!oberste
From: oberste@ncifcrf.gov (Oberste)
Newsgroups: comp.dcom.lans
Subject: Netware 386-TCP/IP coexistence
Keywords: netware 386 tcp/ip clarkson packet drivers
Message-ID: <1875@fcs280s.ncifcrf.gov>
Date: 13 Sep 90 12:54:41 GMT
Organization: NCI Supercomputer Center, Frederick, MD
Lines: 32


    Here's the problem: we have a PC LAN running under Novell Netware 386,
v. 3.0 and we also need to access a VAX cluster and Sun (Unix) workstations
using the Clarkson packet drivers and NCSA Telnet.

    Rebooting between Netware and Telnet sessions is out of the question,
releasing and reloading TSR drivers is too kludgy, and using a separate NIC
for each protocol is too expensive.  We have approx. 20 PCs in the LAN (mostly
286s and 386s) with 3Com 3C501 and 3C503 ethernet cards, connected to a
Compaq 386 server with a WD8103 NIC.

    Has anyone succeeded in getting NW 386 3.0 and the Clarkson packet
drivers to peacefully co-reside?  Best I can tell, the BYU system for
running Netware with packet drivers is only for NW 2.x?  It was my 
understanding that in NW 3.0, multiple protocols could co-exist in parallel
protocol stacks, with software determining who got access to the lower levels
of the stack.  True?  Is this done by loading a driver on the server and
binding a protocol to it as for normal IPX use?  What about drivers on the
workstations?

If all this is possible, are the drivers available (via vendor, anonymous FTP,
or otherwise)?  Is there a packet driver available for the WD8103?

My eternal gratitude to anyone who can shed some light on this problem and
offer a (hopefully) simple solution.

--Steve
-- 
Steve Oberste                            Internet: oberste@ncifcrf.gov
LCMS, PRI, NCI-FCRDC
PO Box B                            "Only 2 things are truly universal:   
Frederick, Maryland 21702-1201             Hydrogen and Stupidity"