Cannot mount NFS

Hi,

I have a strange problem on my laptop when trying to mount NFS filesystems.

The NFS server I try to connect to is not the problem: other Linux boxes
can mount the NFS-drives without any problem. Nor is a firewall running on
the laptop.

The only difference between the laptop and the other machines is that the
laptop switches regularly... but that can hardly be the problem...

I have narrowed it down to tpc/portmapper on the laptop:

# rpcinfo -t localhost nfs
program 100003 version 2 ready and waiting
program 100003 version 3 ready and waiting
program 100003 version 4 ready and waiting
# rpcinfo -u localhost nfs
program 100003 version 2 ready and waiting
program 100003 version 3 ready and waiting
program 100003 version 4 ready and waiting
# rpcinfo -p localhost
rpcinfo: can't contact portmapper: rpcinfo: RPC: Timed out

And that's as far as I get.

Can anyone tell me what I need to check next?

--
gr,
maxx
:wq!

maxx wrote:
> Hi,
>
> I have a strange problem on my laptop when trying to mount NFS filesystems.
>
> The NFS server I try to connect to is not the problem: other Linux boxes
> can mount the NFS-drives without any problem. Nor is a firewall running on
> the laptop.
>
> The only difference between the laptop and the other machines is that the
> laptop switches regularly... but that can hardly be the problem...
>
> I have narrowed it down to tpc/portmapper on the laptop:
>
> # rpcinfo -t localhost nfs
> program 100003 version 2 ready and waiting
> program 100003 version 3 ready and waiting
> program 100003 version 4 ready and waiting
> # rpcinfo -u localhost nfs
> program 100003 version 2 ready and waiting
> program 100003 version 3 ready and waiting
> program 100003 version 4 ready and waiting
> # rpcinfo -p localhost
> rpcinfo: can't contact portmapper: rpcinfo: RPC: Timed out
>
> And that's as far as I get.
>
> Can anyone tell me what I need to check next?

It looks as if you need to install portmap on your laptop.

Robert

On Sat, 18 Feb 2006 14:36:15 +0000, Robert Harris wrote:

> It looks as if you need to install portmap on your laptop.
>
> Robert

I had already checked that:
# which portmap
/sbin/portmap
# rpm -qf /sbin/portmap
portmap-4.0-24mdk

So... that's not the problem.

Also:

# pmap_dump
100000 2 tcp 111 portmapper
100000 2 udp 111 portmapper
100024 1 udp 774 status
100024 1 tcp 777 status
100003 2 udp 2049 nfs
100003 3 udp 2049 nfs
100003 4 udp 2049 nfs
100003 2 tcp 2049 nfs
100003 3 tcp 2049 nfs
100003 4 tcp 2049 nfs
100021 1 udp 32768 nlockmgr
100021 3 udp 32768 nlockmgr
100021 4 udp 32768 nlockmgr
100021 1 tcp 32769 nlockmgr
100021 3 tcp 32769 nlockmgr
100021 4 tcp 32769 nlockmgr
100005 1 udp 754 mountd
100005 1 tcp 757 mountd
100005 2 udp 754 mountd
100005 2 tcp 757 mountd
100005 3 udp 754 mountd
100005 3 tcp 757 mountd

--
gr,
maxx
:wq!

maxx wrote:
> On Sat, 18 Feb 2006 14:36:15 +0000, Robert Harris wrote:
>
>> It looks as if you need to install portmap on your laptop.
>>
>> Robert
>
> I had already checked that:
> # which portmap
> /sbin/portmap
> # rpm -qf /sbin/portmap
> portmap-4.0-24mdk
>
> So... that's not the problem.

Well, if

rpcinfo -p localhost

can't talk to the portmapper, something is wrong with it.

1. What is the output of "netstat -a" which will tell you if your
portmapper is listening (on port 111, TCP and/or UDP)

2. What is the output of "iptables -L" which will tell you what packets
you might be filtering out from your system?

Robert

On Sat, 18 Feb 2006 18:27:55 +0000, Robert Harris wrote:

> 1. What is the output of "netstat -a" which will tell you if your
> portmapper is listening (on port 111, TCP and/or UDP)

$ netstat -an | grep 111
tcp 0 0 0.0.0.0:111 0.0.0.0:* LISTEN
udp 0 0 0.0.0.0:111 0.0.0.0:*
unix 3 [ ] STREAM CONNECTED 13111

So... portmapper is listening.

> 2. What is the output of "iptables -L" which will tell you what packets
> you might be filtering out from your system?

# iptables -L
Chain INPUT (policy ACCEPT)
target prot opt source destination

Chain FORWARD (policy ACCEPT)
target prot opt source destination

Chain OUTPUT (policy ACCEPT)
target prot opt source destination

So... no packets filtered.

I'm figuring out how to start the portmapper in verbose mode.

--
gr,
maxx
:wq!

On Sat, 18 Feb 2006 18:27:55 +0000, Robert Harris wrote:

A bit more investigation show the portmapper is 'responsive' immediately
after booting up the system.

Only after running a script I made to setup the network-settings for the
various networks I connect to does the portmapper refuse to work.

Ergo: I have to debug the script...

At the moment (after setting up the network manually) I can mount the NFS
shares.

--
gr,
maxx
:wq!