Xref: utzoo comp.protocols.tcp-ip:16149 comp.protocols.tcp-ip.ibmpc:5876
Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!usc!samsung!munnari.oz.au!bruce!monu0.cc.monash.edu.au!vaxc.cc.monash.edu.au!johnm
From: johnm@vaxc.cc.monash.edu.au
Newsgroups: comp.protocols.tcp-ip,comp.protocols.tcp-ip.ibmpc
Subject: Re: Running TCP/IP on Novell workstations(Netware 3.1)
Message-ID: <1991May18.181228.86739@vaxc.cc.monash.edu.au>
Date: 18 May 91 08:12:28 GMT
References: <1991May13.171033.8038@sactoh0.sac.ca.us> <1991May17.181235.14139@ux1.cso.uiuc.edu>
Organization: Computer Centre, Monash University, Australia
Lines: 59

jaj@sactoh0.sac.ca.us (Jelle A. Jorritsma) writes:

>... We are able to bring up just the TCP/IP on the
>stations or just Netware but not both(which is our goal). The
>ethernet cards we are using are ne2000 and we have ne2000 packet
>driver. We also have gone thru the SHGEN to generate a new IPX
>shell. Listed below is what's in the autoexec.bat:
>REM NE2000 using IRQ=5, I/O=320h 0h320h
>ne2000 -n 0x60 0x05 0x320h
>ipx
>NET3
>Everything loaded fine, until net3 which returns File Server not
>found.

Hopefully you have Version 9 of the Clarkson Packet Driver collection.
Version 8 had a small omission which broke the -n functionality.

Make sure you did SHGEN using BYU's PDSHELL.OBJ, and not a NE2000
driver.  You can't have the NE2000 packet driver trying to control the
Ethernet card, and a NE2000 driver in IPX trying to control the Ethernet
card at the same time.  The PDSHELL code will make IPX use the packet
driver for I/O.

>Supposedly, the ne2000 packet driver's -n option would allow it to
>deal with the 802.3/Ethernet II(used by TCP/IP) without
>reconfiguring the server. ...

Yes, the -n option will allow packets with Novell's 802.3 packet
encapsulation to be used, instead of Novell packets with Ethernet II
encapsulation as normally used by BYU's PDSHELL.

>Has anybody out there encountered this problem and found a solution
>without reconfiguring the server???

The code in the -n option was developed to avoid having to reconfigure
servers (and obtain Ethernet II Boot ROMS).

freeman@ux1.cso.uiuc.edu (Jay Freeman) writes:

>Hi, try adding the -d option to the packet driver. This delays (-d, getit?)
>execution of the packet driver until after NET3 has completed its business.
>We use this successfully here with wd8003 cards. Good luck, Jay

Not quite.  The -d option delays the packet driver's initialization of
the Ethernet card until the packet driver is actually used (by NET3) for
the first time.  This allows a PC to boot from a Novell server using the
Ethernet driver in the Novell Boot ROM and load the packet driver,
IPX_PD and NET3 and close the boot image file before the packet driver
takes over control of the Ethernet board.  (More gory details available
on request.)

If you aren't remote booting, I can't see any reason to use -d, and it
may suppress some error reporting information.

        John
--
John Mann, Leader - Networking Section  | johnm@vaxc.cc.monash.edu.au
Computer Centre, Monash University      | phone: +61 3 565 4774
Clayton, Vic 3168, Australia            | fax:   +61 3 565 4746