Very Computer

Hi,
    I'm getting RPC timeouts when trying to mount a filesystem from a
Slackware Linux machine to a solaris machine.

I have made the UID, GID's of the users match on both systems.

Here is the /etc/exports file from Slackware:

/home/tommy         remhost.compnay.on.ca(ro)

The Slackware machine has nfsd, mountd, and portmap running. It has been
rebooted since the making of the exports file.

I mount on solaris via:

    mount -F nfs -o ro remhost.compnay.on.ca:/home/tommy       /tommy

Has anyone else seen this behaviour. I'm out of ideas!

    Thanks,

    Henry Leparskas
    UWO Astronomy

Hi,
    Just for more information, I can run 'rpcinfo -p'. This yields:

bash# rpcinfo -p
   program vers proto   port
    100000    2   tcp    111  portmapper
    100000    2   udp    111  portmapper
    100005    1   udp   1004  mountd
    100005    2   udp   1004  mountd
    100005    1   tcp   1007  mountd
    100005    2   tcp   1007  mountd
    100003    2   udp   2049  nfs
    100003    2   tcp   2049  nfs

So I don't think that I have a 'hosts.deny' problem, though I do DENY ALL
for ALL:
Does this make sense?

    Henry

I'm no expert, especially on hosts_access (see man 5 hosts_access)
but I would check with no hosts.deny to ensure that is not the
problem.  I would *guess* that the portmapper et al only read this
on startup  (and a quick strace of portmap with rpcinfo indicates that
it does NOT  read it for each request) so would need to reboot the
portmapper etc after changing.

The other thing to watch for is the nfs version ... your rpcinfo
indicates v2 (not sure whether v3 is available for linux yet)
and sun probably expects v3 .. check your clients mount man page
for that option.

I have an nfschecklist at

http://freespace.*.net/steve.houseman/nfschecklist

Hope you fix it soon,

Steve Houseman

--

currently  steve.houseman at * net      

  Hi,

   I dunno, but I have had hosts_deny problems with rpc-based servers
(esp. ypserv) -- although allowed in hosts.allow, my clients were
getting bounced by the ALL line in hosts.deny -- my solution was
to explicitly un-deny access for these hosts (again) in hosts.deny:
     ypserv:                        ALL EXCEPT my.clients

--  
  marmosets,
        Bryan