LAUSSEGG@AWIWUW11.BITNET (01/11/90)
Hi... I have a few questions, well mixed: 1. Did anybody hear about bugs in Maynard 2.4? I heard, that a file that is splitted between two tapes may be corrupted. I am using a 140 MB tape drive with 3M tapes. 2. Does anybody know something about the coexistence of Novell (SFT2.15) and Dataflex? I am using Dataflex 2.03b, nearly 300MB incl. indices. I suppose some of my troubles are caused by the software. 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
ronc@XLNVAX.EXCELAN.COM (Ron Cully) (01/12/90)
> 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
sherk@UMD5.UMD.EDU (Erik Sherk) (01/12/90)
> > 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 While the Novell TCP/IP (and Wollongong, FTP, etc. ) works it has one major problem. It costs money! On the other hand, with a little work, NCSA and Novell can work together just fine. They can work together through packet drivers. I suggest that you anonymous'ly ftp novell.exe and drivers.arc from omnigate.clarkson.edu (128.153.4.2) and give'm a try... Erik ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Erik Sherk sherk@umd5.umd.edu Network Infrastructure (301) 454-0864 Computer Science Center University of Maryland
bdahlen@ZEPHYR.CAIR.DU.EDU (Robert L. Dahlen @ U. of Denver USA=) (01/13/90)
> >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 [stuff deleted] > >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. > > While the Novell TCP/IP (and Wollongong, FTP, etc. ) works > it has one major problem. It costs money! On the other hand, with > a little work, NCSA and Novell can work together just fine. They can > work together through packet drivers. I suggest that you anonymous'ly > ftp novell.exe and drivers.arc from omnigate.clarkson.edu (128.153.4.2) > and give'm a try... > The NCSA solution only works if you have ETHERNET cabling though...
sherk@UMD5.UMD.EDU (Erik Sherk) (01/16/90)
>> >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 > [stuff deleted] >> >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. >> >> While the Novell TCP/IP (and Wollongong, FTP, etc. ) works >> it has one major problem. It costs money! On the other hand, with >> a little work, NCSA and Novell can work together just fine. They can >> work together through packet drivers. I suggest that you anonymous'ly >> ftp novell.exe and drivers.arc from omnigate.clarkson.edu (128.153.4.2) >> and give'm a try... >> > >The NCSA solution only works if you have ETHERNET cabling though... Or Token-Ring... Erik