Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!hellgate.utah.edu!fcom.cc.utah.edu!npd.novell.com!excelan!donp From: donp@na.excelan.com (don provan) Newsgroups: comp.dcom.lans Subject: Re: Running TCP/IP and Novell concurrently under DOS (SUMMARY) Message-ID: <2652@excelan.COM> Date: 28 Jan 91 19:15:21 GMT References: <21947@netcom.UUCP> Sender: news@excelan.COM Reply-To: donp@novell.com (don provan) Organization: Novell, Inc., San Jose, California Lines: 39 In article <21947@netcom.UUCP> jbreeden@netcom.UUCP (John Breeden) writes: >In article mju@mudos.ann-arbor.mi.us (Marc Unangst) writes: >>1. Load the appropriate packet driver, using the -n switch to force >>Ethernet II<->802.3 translation mode. > >This works as long as there are no REAL 802.3 traffic on the wire along with >the Novell 802.3 traffic. First of all, let's make clear that Mr. Unangst is providing a mechanism for continuing to run 802.3/IPX via packet drivers. That is, he is discussing the problem from a point in time *after* the 802.3/IPX network has already been installed and, therefore, a priori, it's already known to work. In this case, Mr. Breeden's advice might be taken as a warning not to run real 802.3 traffic on your IPX network, although i believe he intended the advice the other way around. >If you mix the two on the same wire (re: ISO and IPX), Netware can't figure >out who's packet is who, and in step with The Wonderful World of Netware >grabs all packets, sooner or later your Netware server dies with an abend >error (at least w/ 2.15, have no idea how 3.X behaves - thought I'd put odds >it's the same). Although i don't personally deal with NetWare 2.15, this is the first i've heard of NetWare itself having a serious problem with 802.2/802.3 packets. I have heard rare reports of the reverse: 802.2/802.3 implementations having trouble with IPX/802.3 packets. In any case, there are many 802.2/802.3 implementations that don't have any problem with nor cause any problem for IPX/802.3, so things aren't quite as bad as Mr. Breeden's post implies. >The solution (besides replacing Netware) is run it as Ethernet 2. Personally, i agree that using IPX/Ethernet rather IPX/802.3 is a good idea. Unfortunately, it can take quite a bit of effort to migrate an existing IPX/802.2 network to an IPX/Ethernet network. Since 802.2 applications are still uncommon and not all interact badly with IPX/802.3, the effort is not always warranted. don provan donp@novell.com