Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!mips!pacbell.com!ucsd!ucbvax!dog.ee.lbl.gov!hellgate.utah.edu!fcom.cc.utah.edu!cc.utah.edu!cc.usu.edu!jrd
From: jrd@cc.usu.edu
Newsgroups: comp.sys.novell
Subject: Re: Econfig or not Econfig, That is the Question.
Message-ID: <1991Apr1.193011.47218@cc.usu.edu>
Date: 2 Apr 91 01:30:11 GMT
References: <1991Mar27.141423.25863@qut.edu.au> <1991Mar31.005452.10463@netcom.COM>
Lines: 37

In article <1991Mar31.005452.10463@netcom.COM>, jbreeden@netcom.COM (John Breeden) writes:
> In article <1991Mar27.141423.25863@qut.edu.au> lynam@qut.edu.au writes:
>>Gidday,
>>       I was wondering if there is any real reason to change to the 8137 type
>>of packets on a fileserver? I don't need too, to use NSCA Telnet,
>>because the -n option on packet drivers, lets me see ordinary fileservers.
>>       Someone told me that if an ordinary Novell server is attached to a
>>heavily used backbone with heaps of different types of protocols, that the
>>server can mistake certain types of packets and as a result can hang.
>>Is this true?  All I really want is to know, is if the above info is true.
> 
> If you are running Netware 2.15 and sharing a wire that is running *real*
> ieee traffic (CLNS/TP4 in my case), then the Netware server will die with
> an abend error.
> 
> When you make ipx talk DIX - the problem goes away.
> 
> IEEE CLNS/TP4 is the only protocol that I've seen Netware 2.15 choke on, and
> I've only seen 2.15 servers die (never had 3.X to test).
> 
> So I'd guess that if you're NOT running *real* ieee on the same wire - you're
> safe.
> -- 
>  John Robert Breeden, 
>     jbreeden@netcom.com, apple!netcom!jbreeden, ATTMAIL:!jbreeden
>  -------------------------------------------------------------------
>  "The nice thing about standards is that you have so many to choose 
>   from. If you don't like any of them, you just wait for next year's 
>   model."

	I second this. My observations and conclusions a couple years ago
were very similar, and the NW 286 crashes were real enough and often when
the server was on the campus backbone. Changing to TYPE 8137 stopped the
crashes, and so today the campus standard is no Novell flavored 802.3 on
the backbone. I can't say if NW 3.x systems suffer the same problem because
all of ours are set to Ethernet_II (TYPE'd stuff).
	Joe D.