Path: utzoo!utgpu!news-server.csri.toronto.edu!mailrus!ames!excelan!keith From: keith@excelan.COM (Keith Brown) Newsgroups: comp.dcom.lans Subject: Re: econfig for netware 386? Message-ID: <1575@excelan.COM> Date: 19 Jul 90 18:45:53 GMT References: <7020001@hpfcso.HP.COM> Sender: news@excelan.COM Reply-To: keith@ca.excelan.com (Keith Brown) Organization: Excelan, A Novell Co., San Jose, CA. Lines: 31 In article <7020001@hpfcso.HP.COM> j_rodin@hpfcso.HP.COM (Jon Rodin) writes: >How does one do econfig (or equivalent) for NetWare 386? It's done when you load your LAN driver. With 386, the LAN driver MLID's support multiple encapsulation methodolodies concurrently (unlike 286 where the the LAN drivers can only support one concurrently). The best way to demonstrate is by example. Suppose you had both "econfig"'d clients and non "econfig"'d clients on the same LAN. Both types of client would be able to see a 386 server with a single NE2000 if you were to fire up your server like this.... : load NE2000 int=2 port=320 frame=ETHERNET_802.3 name=salmon : load NE2000 int=2 port=320 frame=ETHERNET_II name=haddock : bind ipx to salmon net=1234 : bind ipx to haddock net=5678 The "frame=ETHERNET_802.3" parameter isn't actually needed on the first line as it's the default. Note that this DOES NOT load 2 copies of the NE2000 driver in to memory. The second load just adds the additional framing support and uses the existing driver re-entrantly. Other frame types supported are ETHERNET_802.2 and ETHERNET_SNAP. Note that you have set up two logical IPX nets here through the same interface. The IPX network numbers used on each should be unique on your internetwork. Keith ---------------------------------------------------------------------------- Keith Brown Phone: (408) 473 8308 Novell San Jose Development Centre Fax: (408) 433 0775 San Jose, California 95131 Net: keith@novell.COM ----------------------------------------------------------------------------