Path: utzoo!utgpu!jarvis.csri.toronto.edu!rutgers!usc!gem.mps.ohio-state.edu!uakari.primate.wisc.edu!aplcen!haven!umd5!sherk From: sherk@umd5.umd.edu (Erik Sherk) Newsgroups: comp.dcom.lans Subject: Re: Novell and TCP/IP Message-ID: <5412@umd5.umd.edu> Date: 3 Oct 89 20:23:04 GMT References:<365@cscnj.csc.COM> Reply-To: sherk@umd5.umd.edu (Erik Sherk) Distribution: comp Organization: University of Maryland, College Park Lines: 30 In article <365@cscnj.csc.COM> paul@cscnj.csc.COM (Paul Moody) writes: >In article , nesel@drynix.dfrf.nasa.gov (Mike Nesel) writes: >> Would anyone care to comment on the advisability (or not) of >> attaching a Novell network of PC's to a TCP/IP network of >> workstations and mainframes? >> > >We run a Novell network bridged into a TCP/IP network, and run >TCP/IP over Novell to talk to mainframes and minis. > >Using Excelan EXOS 205T cards, a MS-DOS based pc can run >Novell and TCP/IP simultainiously. The only big problem is with >dumb ethernet cards using NCSA Telnet. They cannot do both >simultainously. I just pulled down the novell drivers for the FTP packet driver from omnigate.clarkson.edu. This allows you to share your network inerface (3c501, 3c503, 3c523, some WD cards and Novell cards) with other applications that support the FTP Packet Driver Spec. i.e. NCSA Telnet. I can now load telnet from a network drive and telnet anywhere on the internet. I think that this solution is superior to "gatewaying" (i.e. protocol translation) through the server because the server adds another point of failure. In addition, heavy ftp traffic through the server really bog it down. ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Erik Sherk sherk@umd5.umd.edu Network Infrastructure Group (301) 454-0864 Computer Science Center University of Maryland