On Mon, 2007-04-09 at 22:14 -0500, Ken Gramm wrote:
> Hello Zhang,
> Have you considered that it might actually be a security issue? When
> you installed the MS SFU NFS client how did you answer the Username
> Mapping Server question?
I totally do not understand username mapping server and I am not sure if
I need it. As I am setting up read-only NFS exports applying restriction
only on IP addresses, I just think perhaps I can forget all these
authentication and authorization things. However so far I could not
successfully connect SFU to ANY nfs server in my office, I tried
opensuse, gentoo Linux and FreeBSD. SFU always ends up with a message
from SFU: "Network Path Not Found." I tried these to get around the
error message, all failed:
1. use IP address in /etc/exports rather then hostname or wildcard
2. supply no_auth_nlm to Linux's /etc/exports (FreeBSD I cannot
find this parameter);
3. switch between TCP and UDP on SFU;
The last thing I didn't try is to set up reverse DNS lookup, which is
impossible because the whole campus have been running without reverse
DNS for a lot of years and it will not be changed because I want it to
change.
Everytime I got "network path not found" message from Windows' SFU I try
mount same mount point with Linux and always successful.
I even wonder if Microsoft Intentionally break NFS client because they
know people eventually will turn to SMB and live with it. If they supply
a NFS client, it should be working with at least Linux or FreeBSD or
True64 Unix on normal network. I think perhaps MS NFS client do not work
with any *nix on normal (no reverse DNS) network.
--
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
