Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!wuarchive!kuhub.cc.ukans.edu!caen!hellgate.utah.edu!fcom.cc.utah.edu!npd.novell.com!newsun!keith Newsgroups: comp.sys.novell Subject: Re: NW v3.11 and TCP/IP connectivity (Telnet et.al.)?? Message-ID: <1991Apr18.215705.27939@novell.com> From: keith@ca.excelan.com (Keith Brown) Date: 19 Apr 91 01:30:55 CDT Sender: news@novell.com ( Keywords: 3.11 tcp ip netware connect unix telnet NCSA clarkson econfig Lines: 68 The News Manager) Nntp-Posting-Host: ca Reply-To: keith@ca.excelan.com (Keith Brown) Organization: Novell, Inc. San Jose, California References: Date: Thu, 18 Apr 1991 21:57:05 GMT > [NetWare] v3.11 claims to support TCP/IP connections. Does this mean >that the TELNET software and other goodies are compatible without >econfiging now? Is the process for setting up pretty much the same as >before? Yes and no! If you set things up the way you did before then not much has changed. Clarkson is still maintaining the packet driver distribution. BYU are still making their packet driver shell driver available and the "Whether to ECONFIG or not to ECONFIG" issue still serves to confuse a large number of users and administrators. However, things have moved on in the last few months and we, Novell, have now introduced a substantial array of new products supporting TCP/IP standards at both the server and client systems. Starting with the server, the TCP/IP support bundled into 3.11 gives you the following features when used by itself. These are: 1) IP routing and subnet routing between multiple LAN interfaces plugged into the server. 2) The ability to encapsulate the server<->server IPX traffic inside IP datagrams (actually UDP datagrams) for carrying over an IP only backbone or WAN. 3) Network management using the Simple Network Management Protocol. The entire TCP/IP stack is manageable from any SNMP management console supporting the MIB 1 standard. Just in case you don't have such a console, we provide you with one running as an NLM also. 4) Provision of the underlying Internet Protocol support for other NLMs that use TCP/IP to communicate with peers across the network, NetWare NFS being a good example of such an NLM set. In addition, we just broke the champagne bottle over NetWare NFS which is an NLM set that provides NetWare v3.11 with an NFS server capability, an LPD server capability (distributed printing UNIX style) and an FTP server capability. The first fork lift truck laden with pallettes of NetWare NFS went careering out of the warehouse yesterday in fact. Finally, we just released a new media independant version of our TCP/IP client solution for DOS workstations, namely the LAN WorkPlace for DOS. It can be used standalone or in conjunction with NetWare and uses the Open DataLink Interface (ODI) driver architecture at the client in order to support multiple protocols and datalink encapsulations through a single LAN adapter card. You'll find these drivers in the LAN WorkPlace package or, if you already have NetWare v3.X, you'll find them in a subdirectory called "DOSODI" on the SHGEN-1 disk, which is now the WSGEN disk in v3.11. The LAN WorkPlace itself contains lots of good stuff, including support for the usual set of TCP apps (Telnet, FTP, R-Utilities etc....) and a set of these apps specifically designed for the Windows 3.0 environment if your a point and click type. The LAN WorkPlace also contains the "client piece" of the tunnel, allowing the workstation<->server IPX traffic to be encapsulated in UDP/IP datagrams. Now that we have unleashed this little lot onto the world at large, the Novell San Jose group is now cranking on even more goodies for the TCP/IP and standards oriented communities. Watch this space.... Keith - Keith Brown Phone: (408) 473 8308 Novell San Jose Development Centre Fax: (408) 433 0775 2180 Fortune Dr, San Jose, California 95131 Net: keith@novell.COM