Xref: utzoo comp.dcom.lans:8017 comp.sys.novell:1439
Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!swrinde!elroy.jpl.nasa.gov!usc!apple!netcomsv!jbreeden
From: jbreeden@netcom.COM (John Breeden)
Newsgroups: comp.dcom.lans,comp.sys.novell
Subject: Re: IPX Encapsulation over Ethernet
Message-ID: <1991May8.030725.3387@netcom.COM>
Date: 8 May 91 03:07:25 GMT
References: <6843@s3.ireq.hydro.qc.ca> <1991May7.233920.7888@engin.umich.edu>
Sender: netnews@netcom.COM (USENET Administration)
Organization: Netcom - Somewhere in the S.F. Bay Area
Lines: 26

In article <1991May7.233920.7888@engin.umich.edu> jal@acc.flint.umich.edu (John Lauro) writes:
>In article <6843@s3.ireq.hydro.qc.ca> cayer@ireq.hydro.qc.ca () writes:
>>Can this cause problems inside a multi-protocols network 
>>(ipx, decnet, tcp/ip, ...) ?
>Generally not, for the following reasons:
>   - Most packets are filtered out by destination address.  So what
>     ever is on the destination will be able to decode it.  This leaves
>     only broadcasts.
>   - The broadcasts are ignored by other protocols becasue they don't
>     pass all the tests.  (Such as checksums, etc.)

Netware running "Novell IEEE" DOESN'T ignore other IEEE broadcast traffic 
on the same wire (they don't "test" the packet - no checksum and invalid 
802.2 SAPS). I've seen this hang Netware servers.

You don't see it alot - there's still very little real IEEE/CLNS around.

The solution is to run Netware as a DIX protocol (econfig it).

-- 
 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."