Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!swrinde!zaphod.mps.ohio-state.edu!magnus.acs.ohio-state.edu!usenet.ins.cwru.edu!cwlim!trier From: trier@cwlim.INS.CWRU.Edu (Stephen C. Trier) Newsgroups: comp.protocols.tcp-ip.ibmpc Subject: Re: Problem configuring Novell Server to ethernet protocol Keywords: Novell Message-ID: <1991Jun18.160426.22688@usenet.ins.cwru.edu> Date: 18 Jun 91 16:04:26 GMT References: <1991Jun18.012029.309@qualcomm.com> Sender: news@usenet.ins.cwru.edu Reply-To: trier@po.CWRU.Edu Distribution: na Organization: Case Western Reserve Univ. Cleveland, Ohio, (USA) Lines: 32 Nntp-Posting-Host: cwlim.ins.cwru.edu Edit your AUTOEXEC.NCF file (in SYS:SYSTEM) and add the option "frame=ethernet_ii" to the command line where you load your network card driver. (If there is already a frame= command, remove it.) That will econfig the server. If you would like to run supporting both protocols, duplicate your current load line, add the frame=ethernet_ii command to the second, use "name=" to rename one of them, and bind IPX to both. For example: ... load 3c503 memory=c8000 port=300 int=3 name=ETH_802.3 load 3c503 memory=c8000 port=300 int=3 frame=ethernet_ii name=ETH_II bind ipx to ETH_802.3 bind ipx to ETH_II ... This example loads the 3c503 driver once for each frame type, using a single network card for both. It then tells the server to use the IPX protocol for both. This lets you use both packet driver and non- packet driver computers to speak to the server at once. For your other question, you don't need to econfig the packet driver version of IPX. The econfigging is implicit. You only need to econfig the IPX file if it is a non-packet driver IPX. With what I describe above, you don't even need to do that. -- Stephen Trier "48 61 70 70 69 6e 65 73 73 20 69 73 20 61 Small Systems Guy 20 77 61 72 6d 20 68 65 78 20 64 75 6d 70 Information Network Services 21 20 20 3b 2d 29" - Me Case Western Reserve University Mail: trier@ins.cwru.edu