cornell@csl.dl.nec.com (Cornell Kinderknecht) (04/18/91)
Hello. This is probably something that gets asked here quite often
so if you'd like, please respond via e-mail.
About a year ago, I setup NetWare 2.15, econfiged, and ran the Clarkson
packet drivers so that we could use Clarkson's version of NCSA Telnet and
other network goodies. All was quite simple and works very well.
Now, I am working elsewhere and will be setting up a NetWare 3.11 network
and I need the same connectivity plus maybe a few more things like
NetWare NFS. 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?
Any help on this as well as any other niceties, not-so-niceties about
3.11 will be greatly appreciated.
--- Cornell Kinderknecht
cornell@csl.dl.nec.comkeith@ca.excelan.com (Keith Brown) (04/19/91)
The News Manager) Nntp-Posting-Host: ca Reply-To: keith@ca.excelan.com (Keith Brown) Organization: Novell, Inc. San Jose, California References: <cornell.671918471@michigan> 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
Jons@cup.portal.com (Jonathan S Spangler) (04/19/91)
>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. > Yeah Novell! do you know *where* that fork lift was headed? Do you distribute to the big boys first? (Micro-D, Merisel, TechData)? >... The LAN WorkPlace also contains the "client piece" of the tunnel, >allowing the workstation<->server IPX traffic to be encapsulated in >UDP/IP datagrams. > When you say "client piece", are you refering to just to the mechanism that allows both protocol stacks to be loaded simultaneously right? This is not the same as the client piece that comes with PC-NFS that allows me to "mount" a drive from an NFS server and see that drive in my native DOS (If I understand this correctly.) Aloha, Jonathan jons@cup.portal.com
keith@ca.excelan.com (Keith Brown) (04/20/91)
The News Manager) Nntp-Posting-Host: ca Reply-To: keith@ca.excelan.com (Keith Brown) Organization: Novell, Inc. San Jose, California References: <1991Apr18.215705.27939@novell.com> <41441@cup.portal.com> Date: Fri, 19 Apr 1991 19:18:00 GMT In article <41441@cup.portal.com> Jons@cup.portal.com (Jonathan S Spangler) writes: >do you know *where* that fork lift was headed? Do you distribute to the >big boys first? (Micro-D, Merisel, TechData)? > I believe yesterdays fork lift was headed for the residence of the biggest boy on the block. IBM :-) Todays fork lift is for the others. >>... The LAN WorkPlace also contains the "client piece" of the tunnel, >>allowing the workstation<->server IPX traffic to be encapsulated in >>UDP/IP datagrams. >> >When you say "client piece", are you refering to just to the mechanism that >allows both protocol stacks to be loaded simultaneously right? This is not >the same as the client piece that comes with PC-NFS that allows me to >"mount" a drive from an NFS server and see that drive in my native DOS (If >I understand this correctly.) Correct about the fact I'm not referring to an NFS client capability. Thinking about it, the term "client piece of the tunnel" is terrible! It implies the tunnel has a client end and a server end when actually it doesn't. "Workstation piece of the tunnel". Yes.... thats much better! The workstation piece of the tunnel (:-)) allows a DOS workstation to encapsulate it's normal IPX interaction with the server inside UDP/IP. Using NetWare v3.11 in conjunction with LAN WorkPlace it is possible to put together a NetWare LAN that is entirely IP protocols on the wire. In a local area context I doubt many people will want to tunnel IPX in IP from the workstation to the server. Multiple protocols on LANS are a fact of life and, in my opinion, a perfectly acceptable fact of life. However, in the wide area context, where the routing and congestion control issues are more complex, standardisation on a single protocol such as IP makes a great deal of sense and this is where I envisage our tunnel being applied. It will probably also be applied on large internetworked LANS where multiple protocols run on the subnetworks but a single protocol is used on the main backbone. Configurations like this are pretty commonplace too. The workstation piece of the IP tunnel is for the isolated guy who, for one reason or another, finds himself plugged into the uniprotocol portion of the internetwork. Sound reasonable? 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
Jons@cup.portal.com (Jonathan S Spangler) (04/20/91)
I have a simple version of this question. Can I connect a novell network (2.X or 3.X) to a Sun Sparc II so that I can log into the Sun Sparc from my PC and run a text based application? Any clues would be appreciated Thanks much Ron Roetzer rer@genrad.com
rbraun@spdcc.COM (Rich Braun) (04/23/91)
keith@ca.excelan.com (Keith Brown) writes: >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. And SOSS, my "answer" to Novell's NFS product, just went worldwide on 10 April. It's slower and doesn't have security features, but might be good enough for many sites. This posting is an announcement of several new distribution sites which carry it via anonymous ftp and by other means; it will soon be available from one distributor (who is not affiliated with me) through the postal service for something like US$4. System Directory Contact ------------ --------- ------- spdcc.com pub/sos rbraun (MA) sun.soe.clarkson.edu pub/ka9q nelson (MN) iuvax.cs.indiana.edu!sir-alan /u/pubdir/SOS mikes (IN) garbo.uwasa.fi pc/comm hv (Finland) kirk.bu.oz.au pub/PC/soss bambi (Australia) nestroy.wu-wien.ac.at pub/src/PCtcp/soss mah (Austria) For details on how to get SOSS, send e-mail to the nearest site in the form "contact@system" as shown above. I am particularly interested in corresponding with someone who has experience with creating NLM's who could help convert SOSS to run as an NLM. Thanks, -rich