[comp.dcom.lans] Cabletron Ethernet interface and NCSA Telnet

blais@ut-emx.UUCP (Donald Blais) (06/09/90)

Cabletron Systems, Inc. has provided us with two PC Ethernet interface
cards for a period of evaluation: the E2020 for use in a PC AT, and
the E6020 for use in a Mac II.  The available Macintosh versions of
these cards are reviewed in the March 1990 issue of Macworld and the
June 1990 issue of MacUser.

The E2020 has been installed in a PC AT compatible 16 bit slot with
port select switch set to AUI, interrupt request level jumper to 3,
address select jumper to 300, and power select jumper to AUI.  The
diagnostics run without error.  Because our AUI transceiver cable has
studs that fit into a slide lock, the nut screws of the AUI connector
on the card had to be removed.  One pleasant feature is that the card
comes with light indicators for power, transmit, receive, collision.

Software comes on two floppies.  Included is a lowest level driver,
CSIPD_E, which must be run before any other drivers.  An NCSA driver
is not included.  The included NCSA.DOC says, "There is a package in
the public domain call[ed] NCSA Telnet.  This package can be run as
per the public domain instructions...".  Does an NCSA driver exist?

We have two versions of the NCSA package: NCSA Telnet 2.2, and NCSA
Telnet 2.2D/TN.  Both of these versions of NCSA Telnet work with a
WD8003E interface card.  Neither version is working with the E2020.
The NCSA Telnet 2.2D/TN version yields the following message...

   "Packet driver (Cabletron NIC)
    Class 1 Type 51 Version 103 Extended 2
    Requested paket class does not match driver class
    Could not initialize hardware level network driver
    Error intializing network or getting configuration file"

Are we doing something wrong or do we need a not yet available driver?
-- 
Donald E. Blais             Internet: blais@emx.utexas.edu
Computation Center          BITNET:   blais@UTAIVC
University of Texas         UUCP:     uunet!cs.utexas.edu!ut-emx!blais
Austin, TX 78712            Phone:    +1-512-471-3241

nelson@sun.soe.clarkson.edu (Russ Nelson) (06/11/90)

In article <31283@ut-emx.UUCP> blais@ut-emx.UUCP (Donald Blais) writes:

   The NCSA Telnet 2.2D/TN version yields the following message...

      "Packet driver (Cabletron NIC)
       Class 1 Type 51 Version 103 Extended 2
       Requested paket class does not match driver class
       Could not initialize hardware level network driver
       Error intializing network or getting configuration file"

   Are we doing something wrong or do we need a not yet available driver?

Nope, sounds like you've got the packet driver installed correctly.  I
need more information to tell you what's going wrong.  If you fetch
the packet drivers from sun.soe.clarkson.edu:/pub/ka9q/drivers.arc,
and run 'trace' and then 'dump' and send me the output, I can tell you
more about what's going on.

Cabletron has chosen to write their own packet drivers.  That's all very
well and good, but they also should include some of my packet driver
tools to help people use their packet driver.

--
--russ (nelson@clutx [.bitnet | .clarkson.edu])  Russ.Nelson@$315.268.6667
Violence never solves problems, it just changes them into more subtle problems

blais@ut-emx.UUCP (Donald Blais) (06/12/90)

In article <31283@ut-emx.UUCP> blais@ut-emx.UUCP (Donald E. Blais) writes:
>The NCSA Telnet 2.2D/TN version yields the following message...
>
>   "Packet driver (Cabletron NIC)
>    Class 1 Type 51 Version 103 Extended 2
>    Requested paket class does not match driver class
>    Could not initialize hardware level network driver
>    Error intializing network or getting configuration file"
>
>Are we doing something wrong or do we need a not yet available driver?

With some telephone assistance from Cabletron technical support I have
learned that not one but several different variables in the CONFIG.TEL
file of the NCSA package need to be changed as follows...

        hardware=packet
        interrupt=0
        address=0
        ioaddr=0

I had incorrectly assumed that these settings would correspond to the
jumper settings on the E2020 interface card.  That is not true because
the Cabletron card uses the generic packet driver rather than one that
is specific to a particular card.  Works fine now!
-- 
Donald E. Blais             Internet: blais@emx.utexas.edu
Computation Center          BITNET:   blais@UTAIVC
University of Texas         UUCP:     uunet!cs.utexas.edu!ut-emx!blais
Austin, TX 78712            Phone:    +1-512-471-3241