RICKM@OREGON.BITNET (Rick Millhollin) (01/11/90)
Path: oregon!rickm From: Rick Millhollin <rickm@oregon.uoregon.edu>@oregon.uoregon.edu (Rick Millho llin) Newsgroups: mailing-list.novell Subject: RE: Mac VAP and Packet Drivers Message-ID: <13894@oregon.uoregon.edu> Date: 10 Jan 90 14:00:26 PST References: <13735@oregon.uoregon.edu> Distribution: usa Organization: University of Oregon Lines: 19 In article <13735@oregon.uoregon.edu>, Howard Rollins <PSYHAR@EMUVM1.BITNET> wri tes: > I have a novell network 2.15c with pcs and macs connected to it via > ethernet. For a variety of reasons, I would like to use packet drivers to > allow the pcs to communicate with various tcp/ip products. My question is > can the macs still function correctly both within the novell network and > on the university tcp/ip network when the novell system is econfiged to > 8137 format? Must I econfig the mac ethernet cards also? Or are the mac's > ethertalk packets sent to NOvell handled entirely differently from the pcs > ethernet packets? I have a server with a 3C505 running the Mac VAPs, which has been ECONFIGed so it can talk to packet drivers, and it works fine. I have another with an NE2000, and ECONFIGing it broke the Mac VAPs. So whether what you want to do will work appears to be a function of the ethernet board/drivers, and whether the latter are correctly implemented (3C505) or not (NE2000). I have posted this several times here, on NEWS group comp.dcom.lans, and on NETWIRE. I have yet to see any indication that Novell has a newer NE2000 driver that fixes the problem.