Path: utzoo!censor!geac!torsqnt!news-server.csri.toronto.edu!bonnie.concordia.ca!uunet!munnari.oz.au!bruce!monu1!vaxc.cc.monash.edu.au!johnm
From: johnm@vaxc.cc.monash.edu.au
Newsgroups: comp.dcom.lans
Subject: Re: Novell and TCP/IP concurrently?
Message-ID: <1991Jan23.163037.86182@vaxc.cc.monash.edu.au>
Date: 23 Jan 91 05:30:36 GMT
References: <1TPZV4w164w@mudos.ann-arbor.mi.us>
Lines: 27

In article <1TPZV4w164w@mudos.ann-arbor.mi.us>, (Marc Unangst) writes:
> I'm trying to set something up on our Novell network so that the
> MS-DOS workstations, which are on the same Ethernet as the TCP/IP Unix
> machine, will be able to access the Unix machine and the Novell
> network at the same time.  ... 
 
> I recently obtained the Clarkson packet drivers and the package from
> BYU that allows you to build a packet-driver-aware IPX.COM, because
> they seemed to be the answer.  Everything looks fairly interesting,
> but there seems to be one hitch -- the BYU package requires that you
> reconfigure your Novell server to use Ethernet II packets, rather than
> the 802.3-style packets that we're using now.  ...

The answer is to use the -n option on the Packet Driver.  
This is "mentioned" in DRIVERS.DOC and PROMBOOT.NOT.

When using the -n option, the Packet Driver will convert IPX packets
between the Ethernet II type 8137 encapsulation used by BYU's PDSHELL
IPX interface code and the 802.3-style encapsulation normally used on
Ethernet by Netware servers, shells and boot ROMs.  Doing this removes
the need to ECONFIG your Netware servers and shells.

	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