Path: utzoo!utgpu!watserv1!watmath!att!att!rutgers!uwm.edu!zaphod.mps.ohio-state.edu!mips!apple!netcom!jbreeden From: jbreeden@netcom.UUCP (John Breeden) Newsgroups: comp.dcom.lans Subject: Re: Novell: fear and loathing... Keywords: novell ethernet Message-ID: <16197@netcom.UUCP> Date: 4 Nov 90 19:54:25 GMT References: <15581@cbmvax.commodore.com> Organization: Netcom- The Bay Area's Public Access Unix System {408 241-9760 guest} Lines: 23 In article hedrick@athos.rutgers.edu (Charles Hedrick) writes: >I don't know of any major misbehaviors that would affect other >protocols. Novell uses a couple of routing protocols that behave more >or less like RIP, and they use broadcasts in reasonably sensible ways. >The only problem I've heard is that the default setup uses a packet >format that looks like it is IEEE 802.2 (i.e. a length code instead of >a packet type), but isn't. If a system that understands IEEE 802.2 >sees the packet, it finds all ones where it would expect an NSAP. >This is supposed to mean "all destinations". Some other protocol >stacks apparently get confused. One solution is to run a utility 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". -- John Robert Breeden, netcom!jbreeden@apple.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."