Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!wuarchive!sdd.hp.com!elroy.jpl.nasa.gov!ames!excelan!donp
From: donp@na.excelan.com (don provan)
Newsgroups: comp.dcom.lans
Subject: Re: Novell: fear and loathing...
Message-ID: <2374@excelan.COM>
Date: 9 Nov 90 18:09:32 GMT
References: <16197@netcom.UUCP> <3396@uakari.primate.wisc.edu>
Sender: news@excelan.COM
Reply-To: donp@novell.com (don provan)
Organization: Novell, Inc., San Jose, California
Lines: 26

In article <3396@uakari.primate.wisc.edu> bin@primate.wisc.edu writes:
>From article <16197@netcom.UUCP>, by jbreeden@netcom.UUCP (John Breeden):
>> I've seen Netware's quasi/semi/802.3 servers die with abend errors when 
>> confronted by other real 802.3 protocols (ISO/TP4) running on the same wire. 
>> The "problem" isn't just how other (non)Netware servers "behave" but how 
>> Netware servers themselves "behave".
>
>That might be an advantage: George can then point to the Novell servers and
>say what wretched network citizens they are, and kick MIS out the door. :-)

It does sound like you should kick MIS a little, but because of their
abilities, not because of the Novell servers.  It doesn't take that
much talent to ECONFIG older NetWare servers and clients to send
standard Ethernet packets instead of "raw" 802.3.  Newer software can
be configured even more easily.

Well, that's not really fair to the MIS folks.  George's MIS people
probably aren't reconfiguring their NetWare network to send ethernet
packets because their many NetWare users would be inconvenienced a
little by the switch over.  Those users would probably be even more
inconvenienced if MIS removed NetWare altogether.

Why, yes, now that you ask, i do happen to work for Novell. :-)

						don provan
						donp@novell.com