Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!swrinde!elroy.jpl.nasa.gov!ncar!gatech!hubcap!ncrcae!secola!tsloman
From: tsloman@secola.Columbia.NCR.COM (Todd Sloman (t.sloman@secola))
Newsgroups: comp.sys.novell
Subject: Does IPXODI work in ECONFIG (Ethernet_II) mode?
Message-ID: <342@secola.Columbia.NCR.COM>
Date: 3 May 91 07:40:14 GMT
Reply-To: tsloman@secola.Columbia.NCR.COM ()
Organization: NCR NPD Columbia
Lines: 28

HELP!!!!

We have NetWare 3.0 servers running in both standard NetWare (Novell's
802.3) and ECONFIG (Ethernet_II) mode.  My problem is with the IPXODI.COM
for ODI workstations.  

In standard NetWare mode (NOT Econfigged), I load LSL.COM, 3C503.COM,
IPXODI.COM, and NET4.COM and connect to my file server.  However, running
the ECONFIG utility on any combination of these .COM files AND including
"FRAME=ETHERNET_II" in my NET.CFG file will not allow me to connect to 
my ECONFIGGED server.

Running the ECONFIG command to let normal IPX.COM files (i.e. those actually
generated with the SHGEN-1 diskette) works fine.  Regardless of how I use
ECONFIG with the ODI files, I cannot connect to my server.  In addition, 
normally when ECONFIG is executed, it echoes the mode of the driver after
completion of the ECONFIG command.  This does not happen when I ECONFIG the 
the ODI files.

Finally, when you load the 3C503.COM file, it echoes out "FRAME=IEEE 802.3".
It almost seems as if Novell is not supplying a 3C503.COM for Ethernet_II
mode.  

Can anyone out there help?  Thanks in advance.

Todd Sloman
(803) 739-7670
tsloman@secola.NCR.COM