I have installed NFSserver on a test Netware 6, SP3 server. I have
exported a volume using nfsadmin. When I try to mount the volume (116 Mb)
on my RedHat 8 WS, it takes 5 minutes to mount. Also, no authenication is
required. Since I have several hundred unix workstations of various
flavors, I don't want to have to grant different volume rights to each
different WS.
I did install ncp and ipx tools on my RedHat WS. I could ncpmount any
volume on any server running ipx, almost instantaneously, and I was
required to enter my eDir authenication. However, I am trying to get away
from ipx and I don't want to have to install ipx tools on each of my
workstations.
I downloaded nfs30sp5, but it looks like it is only for use on Netware 5?
Does anyone have any ideas on how I decrease my mount time to something
usable? How can I configure my NFS to use the eDir authenication?
Thanks,
John Curran
Apart from the 5-minute hang, it's working as designed. NFS is a
server-to-server mount protocol, so once a remote filesystem is mounted,
the server trusts that the client has not been compromised and simply
accepts whatever uids it uses.
Assuming all your users have unique Unix uids, then make sure their NDS
users have the right uid/gid settings so that they have matching access.
NW6 only supports Indepentant mode, so any trustee rights set on
directories on the Netware side will have to be manually applied by root
via chmod/chgrp on the Unix side.
> Does anyone have any ideas on how I decrease my mount time to something
> usable? How can I configure my NFS to use the eDir authenication?
If you manually mount the Netware server via its IP, does it still take
a long time? How about if you force a TCP/UDP, or NFSv2/NFSv3 mount?
--
Dan Nelson
dne...@allantgroup.com
Although you should continue this thread here to avoid creating confusion,
there is a separate NFAP forum: support.os.server.native-file-access, which
you should use for future NFA issues.
Also, ncptools can be used to mount NW volumes over IP -- you have to use
the -A parameter as I recall, which specifies the DNS name or IP address of
the NCP server.
Re: the NFS issues, it looks like Dan has you headed on the right track.
bd
NSC Volunteer SysOp
www.InsightNetSolutions.net