Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!uwm.edu!uakari.primate.wisc.edu!brutus.cs.uiuc.edu!psuvax1!psuvm!XLNVAX!RONC From: ronc@XLNVAX.EXCELAN.COM (Ron Cully) Newsgroups: bit.listserv.novell Subject: Re: Questions Message-ID: <9001112132.AA14921@la.excelan.com> Date: 11 Jan 90 21:32:01 GMT Sender: Novell LAN Interest Group Reply-To: Novell LAN Interest Group Lines: 31 Approved: NETNEWS@PSUVM Gateway X-To: NOVELL%SUVM@pucc.PRINCETON.EDU > I have a few questions, well mixed: > > 3. Why isnt it possible to run both, Novell and TCP/IP at the same > time? When I begin with NCSA/Telnet (3C523/MC) no problems to run > the Netware but the other way round I cant get any connection. Our > Network admin. told me that the problem comes from Novell, but really, > I do not believe him. > > Thanks in advance > Robert > You can run Novell and TCP/IP at the same time depending upon who's implementation of TCP/IP you use. Novell has an implementation (from the former Excelan) called LAN WorkPlace for DOS that runs concurrently with the NetWare shell. It also includes a NetBios interface that is compatible with MS-NET stuff so you can conceivably have concurrent MS-NET and NetWare connections from the same PC. LWP does require a Novell card called the 205 (for XT/AT busses) or the 215 (for MC). The TCP/IP is run on the NIC directly so it is higher performance for slower XT and AT machines. The IPX stack uses a link level interface on the 2x5 card (so it uses the PC CPU to do the protocol work). Other implementations with concurrent TCP/IP and IPX are available from Wollongong and (I believe) FTP Software. These implementations use a dumb controller and the TCP/IP stacks are host resident. As for NCSA/Telnet, I can't say. I don't think the problem is with the IPX stack though because other commercial packages can do it. Ron Cully Prod Mktg Engr