Path: utzoo!utgpu!news-server.csri.toronto.edu!rutgers!usc!elroy.jpl.nasa.gov!aero!aero.org
From: ctw@aero.org (Charles T. Wolverton)
Newsgroups: comp.protocols.tcp-ip.ibmpc
Subject: NCSA + Novell
Keywords: NCSA, Novell, IPX, packet driver
Message-ID: <96246@aerospace.AERO.ORG>
Date: 8 Jan 91 00:19:06 GMT
Sender: ctw@aerospace.aero.org
Distribution: usa
Organization: The Aerospace Corporation, El Segundo, CA
Lines: 28

Here's a variation on the FAQ "How can I get TCP/IP and Novell to work
at the same time" - viz., "How ARE we getting them to work??"

We are using a native (i.e., non-CMU/PD) IPX module talking
directly to a 3C501. We are also using NCSA Telnet with the
direct-to-the-card config (i.e., again, no PD). After carefully
explaining to a colleague why, due to contention for the H/W IRQ used
by the network card, he wouldn't be able to get Novell and NCSA Telnet 
to work simultaneously without a PD and the appropriate IPX-for-the-PD
module, he proceeded to ignore this "wisdom" and load the Novell stack
followed by the NCSA Telnet - works like a charm, apparently.
(Specifically, he can log  onto the Novell server, do some Telnet
stuff, close the Telnet session, and the network drives are still there.)
My assumption was that NCSA Telnet would grab the interrupt so that
the IPX would be history.

Hence, the question "Why does this work?? Does the NCSA Telnet do
its own IRQ mux'ing?? or some other cleverness?? Or am I just way off
base in my concept of what's going on??

(We also tried FTP'ing to the network drive - that DID bomb the
machine as I would have expected.)

-ctw

***  Charles T. Wolverton    *****  Aerospace Corporation  ***
***  ctw@aero.org            *****  P.O. Box 92957  M1-023 ***
***  (213) 336-5204          *****  Los Angeles, CA 90009  ***