Xref: utzoo comp.sys.novell:1422 comp.dcom.lans:8003
Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!usc!apple!veritas!amdcad!usenet
From: phil@brahms.amd.com (Phil Ngai)
Newsgroups: comp.sys.novell,comp.dcom.lans,amd.sys.pc
Subject: Netware 386 NFS capabilities
Message-ID: <1991May7.170934.18198@amd.com>
Date: 7 May 91 17:09:34 GMT
Sender: usenet@amd.com (NNTP Posting)
Organization: Advanced Micro Devices; Sunnyvale, CA
Lines: 27

I want to describe a feature that I feel would be very useful and see
how others feel about it. Our company network is run by Unix bigots who
will only allow TCP-IP protocols on the backbone, which of course, are
lousy for PC Win3 users.  What I would like to do is run our own
private IPX network but still have the ability to access the
workstation world for telnet, ftp, and NFS.

The best system would seem to be to put two network interfaces in our
Novell fileserver and let it bridge, route, and gateway services
between our private IPX network and the corporate TCP-IP backbone.

What's missing, as I understand the capabilities of Netware 386, is the
ability for the Novell fileserver to act as an NFS *client* and mount a
filesystem from a Unix host. There are many reasons why this is nice,
including the fact that our Unix hosts have a nice backup system in
place. Since we want the file server to isolate our private IPX network
from the corporate backbone anyway, this wouldn't result in a wasteful
doubling of filesystem traffic.

How about it, Novell, would you consider putting this in?

(what is a Unix bigot? Someone who responds by banning Novell if there
is a single incident with it, but blames the users when there are
multiple crashes involving PC-NFS.)

--
	The enemy of my enemy is my friend.