On Wed, 12 Jun 1996, Rick Hawkins wrote: > I can't quite get nfs going for some reason. I had it going quickly > under the 1.2 kernel (i have 2 machines sitting here). > > I uncommented everything in /etc/init.d/netstd_nfs. I added / to > exports. I added ALL: .iastate.edu to hosts.allow. > > ANd the two machines give me different errors . . . > > trying to mount from one, > > # mount -t nfs 129.186.31.38:/ /server/ mount > clntudp_create: RPC: Program not registered
I saw something very much like this on my home network after upgrading all my linux machines to debian 1.1. Even though I had an "ALL: .taz.net.au" in my /etc/hosts.allow, it still didn't work until I fixed it by putting portmap: 192.88.6.32/255.255.255.224 in /etc/hosts.allow (this specifies my class c subnet) This is actually documented in /usr/doc/net/portmapper.doc.gz. Here's the relevant text (but read that file for full details of what's going on!): By default, host access control is enabled. However, the host that runs the portmapper is always considered authorized. The host access control tables are never consulted with requests from the local system itself; they are always consulted with requests from other hosts. In order to avoid deadlocks, the portmap program does not attempt to look up the remote host name or user name, nor will it try to match NIS netgroups. The upshot of all this is that only network number ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ patterns will work for portmap access control. ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ Sample entries for the host access-control files are: /etc/hosts.allow: portmap: your.sub.net.number/your.sub.net.mask portmap: 255.255.255.255 0.0.0.0 /etc/hosts.deny portmap: ALL: (/some/where/safe_finger -l @%h | mail root) & > THe other (the .38 machine) reports during boot that > /etc/init.d/rc: /etc/rc2.d/S25netstd_nfs: permission denied. it's probably not executable. check the permissions on the file (remember that /etc/rc2.d/S25netstd_nfs should be a symlink to /etc/init.d/netstd_nfs ... check the perms on the file, not the link) Craig