Path: utzoo!attcan!uunet!cs.utexas.edu!hellgate.utah.edu!fcom.cc.utah.edu!cc.utah.edu!cc.usu.edu!jrd
From: jrd@cc.usu.edu
Newsgroups: comp.dcom.lans
Subject: Re: 802.3 for NetWare for VMS
Message-ID: <1991Feb25.191228.46940@cc.usu.edu>
Date: 26 Feb 91 01:12:28 GMT
References: <755@hwsw.gedas.de>
Followup-To: comp.dcom.lans
Lines: 30

In article <755@hwsw.gedas.de>, rainer@hwsw.gedas.de (Rainer Raupach) writes:
> Hi Netlanders,
> 
> I'm looking for a NW-VMS guru, who can tell me if it is possible 
> to change NW-VMS from Ethernet II to 802.3, so that all 'normal'
> NW-servers and workstations can see the VAX.
> In the file 'NW_LOAD_DRV.COM' is a parameter for one driver which
> says something like '/e_type=3781', which stands for the Novell
> assigned type field value of 8137.
> Is there a chance to change this value, so that 802.3 packets are
> sent?
> 
> Thanks, Rainer
> -- 
> /\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\
> Rainer Raupach		Internet: rainer@hwsw.gedas.de
> Network Coordinator	X.400:	S=RAUPACH C=DE A=DBP P=VW-GEDAS
> VW-GEDAS Berlin, GER 	Phone:	+49 30 39007-629  / FAX : ext -999

Rainer,
	I don't think it can be done. The TYPE field in Ethernet II packets
is used for LENGTH in IEEE 802.3 packets. What's more, Novell style 802.3
packets are not even properly formed 802.3 packets. Decoding 802.3 requires
extra software to recover the source and destination access points etc and
that is likely not present in the VMS Ethernet drivers.
	The approach taken by many sites is to abandon Novell style 802.3
as rapidly as possible, as even Novell is doing. Converting NW servers to
Ethernet II TYPE 8137 is very easy (ECONFIG) and has other benefits to all
network users.
	Joe D.