[vox-tech] NFS mount "RPC: Timed out" error
Bill Kendrick
vox-tech@lists.lugod.org
Mon, 14 Jul 2003 13:35:20 -0700
On Mon, Jul 14, 2003 at 06:25:39AM -0700, Ken Herron wrote:
> --On Monday, July 14, 2003 03:53:20 AM -0700 Bill Kendrick
> <nbs@sonic.net> wrote:
>
> >The LAN IP of the mountING system is listed in the mountED system's
> >/etc/hosts.allow, with access to:
> >
> > portmap
> > lockd
> > rquotad
> > mountd
> > statd
>
> Shouldn't nfsd be in there?
*shrug* Sure?! Why not? ;) Like I said, it worked previously, and I know I didn't
mess with hosts.allow between the time it /was/ working and now, but I'll try it anyway...
[ tries it ]
Hrm... I added it, and then restarted both "nfs-user-server" and "inetd"
(in /etc/init.d/ under Debian). Still getting the timeout...
> If necessary, use rpcinfo to make sure the server bits are actually
> functioning properly. "rpcinfo -p host" will query the portmapper for the
> registered services;
For the host in question, I get back:
program vers proto port
100000 2 tcp 111 portmapper
100000 2 udp 111 portmapper
100003 2 udp 2049 nfs
100003 2 tcp 2049 nfs
100005 1 udp 630 mountd
100005 2 udp 630 mountd
100005 1 tcp 633 mountd
100005 2 tcp 633 mountd
> "rpcinfo -u host progname" will send a null query to
> a particular service.
$ rpcinfo -u the_host nfs
program 100003 version 2 ready and waiting
("nfsd" was reported as an "unknown service"; looking at that, I tried guessing that maybe
hosts.allow should have "nfs", not "nfsd". So, I tried it; still no luck.)
Before I go much further... is there any chance at all that this could be a kernel
issue on mountING system? (The one trying to make the NFS connection to the mountED server)
Thx for your help!
-bill!
--
bill@newbreedsoftware.com Got kids? Get Tux Paint!
http://newbreedsoftware.com/bill/ http://newbreedsoftware.com/tuxpaint/