I am working with two clients (A and B) mounting a single directory
via nfs from server C.
Client A is RedHat 7.3 using stock RedHat 2.4.18 kernel.
Client B is RedHat 7.2 using stock RedHat 2.4.7 kernel.
Server C is RedHat 7.1 using 2.4.18 kernel with NFS all patches.
Mounting is via tcp. The server uses iptables. A script extracts port
information from rpcinfo -p to determine which nfs ports to permit
into the server from the clients.
Issue #1: Even though I am mounting via tcp, apparently, I must
permit udp access to the portmap daemon on the server via iptables,
otherwise mount on the clients hang. Why is that?
Issue #2: At some point, I noticed that the server C's hostname has
spontaneously changed to that of the client B! All options to the
hostname command at server C's shell misidentify it as client B. What
could possibly cause such weird behavior? The command prompt itself
is affected of course. The uname command is also affected. The host
command, which access external DNS servers, is not affected and I can
seem to access the server via other network services (e.g, netatalk)
on the server under its correct name. ( I don't know for sure that
mounting nfs shares was somehow responsible for this, but it and
iptables were the only things I had modified to get this working).
--
Maurice Volaski, [email protected]
Computing Support, Rose F. Kennedy Center
Albert Einstein College of Medicine of Yeshiva University
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
NFS maillist - [email protected]
https://lists.sourceforge.net/lists/listinfo/nfs