Article View: comp.os.netware.connectivity
Article #104Re: Should new server be 802.2 or Ethernet II?
From: David De Rosier
Date: Wed, 21 Aug 1996 00:00
Date: Wed, 21 Aug 1996 00:00
54 lines
2946 bytes
2946 bytes
Most drivers pre mid 89 were 802.3 by default, most post mid 89 are 802.2 by default. Some today will still default to 802.3. Why should we care is the real question. Novell did not request the change of default just for the "heck of it", 802.2 is a standard. David De Rosier CNI, MCT, Master CNE etc. Roger Kresge <rkresge@web.iis-centpa.com> wrote in article <4usai9$vbn@lily.redrose.net>... > gary@scisysgw.sci.com (Gary Heston) wrote: > > >In article <4ud5f1$55o@mtinsc01-mgt.ops.worldnet.att.net> bdhuskey@postoffice.worldnet.att.net (Brian Huskey) writes: > >>I thought the default frame type for 3.x was 802.3 and that it was not > >>until 4.x that the default became 802.2. > > [ ... ] > > >No, the change was made with 3.12. I remember the fuss that was caused > >by that...numerous "I can't see my new server!" articles. > > > OK, now I'll step into this fray. > > The change to the default of ETHERNET_802.2 actually took place > *BEFORE* the release of both NetWare v3.12 and any version of NetWare > 4.x. Novell had released the updated ODI spec to developers, > manufacturers, etc., long before they released either NetWare 4.0 or > 3.12 (and yes, 4.0 was released *before* 3.12). They required that in > order to gain Novell certification, all new drivers must use the new > ODI spec and default ETHERNET_802.2 frame while NW v3.11 was still the > latest and greatest version of NetWare. > > For about a year before the release of NW 4.0 we got client software > and server driver releases with warnings all over the place about the > new default of Ethernet_802.2 frame type. > > Sorry to burst anyone's bubble on this one, but that's the way it was. > > -- > ========================================================================== > Roger Kresge, Master CNE/CNI, MCP Internet: rkresge@web.iis-centpa.com > Consulting Engineer CompuServe: 71023,447 > Inacom Information Systems > Lancaster, PA Corporate Email: rkresge@inacom.com > ========================================================================== > >
Technical Details
Message-ID:
<01bb8ef7$effe3020$2fc5bfcc@dd>Path:
arc1-ca.pugleaf.net!unknown!not-for-mailReferences:
<4uasq3$s0m@caladan.restena.lu> <839539320snx@hwcces.demon.co.uk> <4ud5f1$55o@mtinsc01-mgt.ops.worldnet.att.net> <Dw02EG.F1B@scisysgw.sci.com> <4usai9$vbn@lily.redrose.net>Show Full Headers
Complete Article Headers
X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: fe659,cdfb6a439be90d1d X-Google-Attributes: gidfe659,public X-Google-Thread: fa939,cdfb6a439be90d1d X-Google-Attributes: gidfa939,public X-Google-Thread: f8bf7,cdfb6a439be90d1d X-Google-Attributes: gidf8bf7,public From: "David De Rosier" <dderosie@uniserve.com> Subject: Re: Should new server be 802.2 or Ethernet II? Date: 1996/08/21 Message-ID: <01bb8ef7$effe3020$2fc5bfcc@dd> X-Deja-AN: 175396833 distribution: world references: <4uasq3$s0m@caladan.restena.lu> <839539320snx@hwcces.demon.co.uk> <4ud5f1$55o@mtinsc01-mgt.ops.worldnet.att.net> <Dw02EG.F1B@scisysgw.sci.com> <4usai9$vbn@lily.redrose.net> organization: ICNI newsgroups: comp.os.netware.connectivity,bit.listserv.novell,comp.os.netware.misc