mcginnis@kuhub.cc.ukans.edu (06/07/91)
Anybody out there know how to configure a PC to use Novell NetWare with NDIS controlling the network card? The network support people at Western Digital assure me that this is possible but I haven't had much luck. E-mail or post a reply. If I get a solution I will post it in detail. Please include copies of CONFIG.SYS, PROTOCOL.INI, and any clues you can give. The successful poster will help many of us much and undoubtedly earn much good karma. BTW: There is a good article about NDIS in the winter 1991 3Tech Journal published by 3Com. This is a very interesting magazine for low-level networking nerds. $35/year. 3Tech Journal 3Com P.O.Box 58145 Santa Clara, CA 95052-9953
P85025@BARILVM.BITNET (Doron Shikmoni) (06/19/91)
In article <1991Jun7.153644.31310@kuhub.cc.ukans.edu>, mcginnis@kuhub.cc.ukans.edu says: > >Anybody out there know how to configure a PC to use Novell NetWare >with NDIS controlling the network card? The network support people >at Western Digital assure me that this is possible but I haven't had >much luck. Let's start with the bottom line: it can be done. We do it. But it takes some configuration effort and some software collection. First of all, as far as I know, true to the moment of writing this, Novell can't talk directly to NDIS - a fact which I find less than pleasing (Novell people, are you listening?). I would expect a vendor like Novell to support NDIS directly. However, there is a way out. It is comprised of three parts: 1. Packet Driver support for IPX, from Brigham-Young University (BYU). 2. NDIS to Packet Driver converter. 3. NDIS-supporting layer (probably Lan Support Program V1.2 from IBM). The BYU code can be obtained from countless anonymous FTP sites over the net (I think omnigate.clarkson.edu is one of them - check it out). To run it, you should follow the install instructions that come with it. There's a configuration issue there - you should ECONFIG your server to use Ethernet V2 packet types, rather than the 802.3 packet type. You *must* use the ECONFIG option, since the packet driver you are going to use does not have the -n option (if you are familiar with that option). Next is the NDIS -> Packet converter. You will need the DIS_PKT program. This one has been originally written by FTP Software, but as supplied, it cannot be used with the BYU code. Good news here too: Joe R. Doupnik from Utah State U has modified this driver considerably (bravo!), so it can work with BYU IPX (and many other things, like Netwatch and Netcapt). You can get this driver (V1.07 now, works *great*) from netlab.usu.edu (via anonymous FTP). Joe has added good documentation as per configuration requirements (CONFIG.SYS and PROTOCOL.INI). Last but not least, you should, obviously, have the NDIS driver for your board and the NDIS-based Lan Support. From your question, I would assume you have these in place already. I think this should be enough to get you started. The best news for you, is that I can tell you this can actually work... I wasn't so lucky when I spent a lot of time on making some things (Novell included) work with NDIS... Good luck Doron