Cannot mount via NFS

Greetings,

I am trying to mount a directory using NFS, and I am having a problem with
the portmapper.

First of all, all of the server settings appear to be correct. The
appropriate directory and host IP address are specified in /etc/exports,
and a "service: host" entry exists for all five relevant services
(portmap, lockd, mountd, rquotad, statd) in /etc/hosts.allow. The command
"/usr/sbin/rpcinfo - p" on the server produces the following output:

=========================================
program vers proto port
100000 2 tcp 111 portmapper
100000 2 udp 111 portmapper
100011 1 udp 982 rquotad
100011 2 udp 982 rquotad
100011 1 tcp 985 rquotad
100011 2 tcp 985 rquotad
100003 2 udp 2049 nfs
100003 3 udp 2049 nfs
100005 1 udp 32805 mountd
100005 1 tcp 37842 mountd
100005 2 udp 32805 mountd
100005 2 tcp 37842 mountd
100005 3 udp 32805 mountd
100005 3 tcp 37842 mountd
100024 1 udp 32806 status
100024 1 tcp 37844 status
========================================

On the client machine, the same command produces

========================================
program vers proto port
100000 2 tcp 111 portmapper
100000 2 udp 111 portmapper
100024 1 udp 32768 status
100024 1 tcp 32768 status
100021 1 udp 32769 nlockmgr
100021 3 udp 32769 nlockmgr
100021 4 udp 32769 nlockmgr
391002 2 tcp 32769 sgi_fam
100007 2 udp 912 ypbind
100007 1 udp 912 ypbind
100007 2 tcp 915 ypbind
100007 1 tcp 915 ypbind
100011 1 udp 652 rquotad
100011 2 udp 652 rquotad
100011 1 tcp 655 rquotad
100011 2 tcp 655 rquotad
100003 2 udp 2049 nfs
100003 3 udp 2049 nfs
100005 1 udp 683 mountd
100005 1 tcp 698 mountd
100005 2 udp 683 mountd
100005 2 tcp 698 mountd
100005 3 udp 683 mountd
100005 3 tcp 698 mountd
=======================================

When I try the command "/usr/sbin/rpcinfo -p server" from the client
machine, I get the following error:

================================================== ======================
rpcinfo: can't contact portmapper: RPC: Remote system error - Connection
timed out
================================================== ======================

No firewalls are running on either machine. The server can
"/usr/sbin/rpcinfo -p client" just fine. The server and client can ping
back and forth just fine. The server is a RedHat 7.3 system with the
2.4.18 kernel, and the client is a RedHat 9.0 system with the 2.4.20
kernel.

How can both machines be running portmapper, neither machine be using a
firewall, yet the client is having problems connecting to the server?

Thanks for the help,

Jeff

--
Add an underscore between 'd' and 's' and remove the first three
letters of the alphabet for email.

On Thu, 24 Jun 2004 01:37:00 -0700, Jeff Krimmel wrote:
> I am trying to mount a directory using NFS, and I am having a problem with
> the portmapper....
[snippage]
> How can both machines be running portmapper, neither machine be using a
> firewall, yet the client is having problems connecting to the server?

Hmm, I find the "showmount -e <server>" command to be useful. It will show
what/if is currently being shared by the server. With rpcinfo you might
get into other issues, and I find the information to be confusing.

If your server has NFS files exported. Then doing the showmount on the
server should confirm that. If not, maybe your NFS deamon is not running?

If you see the export list on the server, try the command on the client.

Might give you some info. At least another data point (this works! that?)
Oh, and you can use IP address, or hostname (checks name resolution, too).

--
Juhan Leemet
Logicognosis, Inc.

On Thu, 24 Jun 2004 21:06:38 -0200, Juhan Leemet wrote:

> On Thu, 24 Jun 2004 01:37:00 -0700, Jeff Krimmel wrote:
>> I am trying to mount a directory using NFS, and I am having a problem with
>> the portmapper....
> [snippage]
>> How can both machines be running portmapper, neither machine be using a
>> firewall, yet the client is having problems connecting to the server?
>
> Hmm, I find the "showmount -e <server>" command to be useful. It will show
> what/if is currently being shared by the server. With rpcinfo you might
> get into other issues, and I find the information to be confusing.

When used from the client, the command "showmount -e <server>" yields

================================================== =============
mount clntudp_create: RPC: Port mapper failure - RPC: Timed out
================================================== =============

When used from the server, the command "showmount -e" lists the
appropriate exported directories and the proper hosts. So, it looks like
the problem is definitely in the connection of the client to the server's
portmap service, but the portmap service is running on both the client and
the host, and it is the same version on both (as seen in the original post).

Any other ideas?

Thanks,

Jeff

--
Add an underscore between 'd' and 's' and remove the first three
letters of the alphabet for email.

In comp.os.linux.networking Jeff Krimmel <(E-Mail Removed)> wrote:
> When used from the client, the command "showmount -e <server>" yields
>
> mount clntudp_create: RPC: Port mapper failure - RPC: Timed out
> [...]
> Any other ideas?

Before running showmount/rpcinfo on the client host, start "tcpdump -n udp"
on both client and server. If you won't see inbound RPC (111/udp) packets
on server, then check iptables/ipchains (both with "-L -n" options) on
both sides to check whether there is something relevant in there.

--
andrei

On Fri, 25 Jun 2004 02:04:31 +0000, Andrei Ivanov wrote:

> In comp.os.linux.networking Jeff Krimmel <(E-Mail Removed)>
> wrote:
>> When used from the client, the command "showmount -e <server>" yields
>>
>> mount clntudp_create: RPC: Port mapper failure - RPC: Timed out [...]
>> Any other ideas?
>
> Before running showmount/rpcinfo on the client host, start "tcpdump -n
> udp" on both client and server. If you won't see inbound RPC (111/udp)
> packets on server, then check iptables/ipchains (both with "-L -n"
> options) on both sides to check whether there is something relevant in
> there.

I don't think I understand what you're asking me to do. I opened two
terminals on the client, and I first did the "tcpdump -n udp" command on
the first terminal, and then I tried "rpcinfo -p <server>" on the second
terminal, and I did not notice any RPC packets pass through the tcpdump
outupt. I did the same thing on the server (but with "rpcinfo -p
<client>"), and I still saw no RPC packets pass through the tcpdump
output.

The "rpcinfo -p <client>" works when performed from the server, but the
"rpcinfo -p <server>" does not work when performed from the client. No
iptables or ipchains rules are set up on either one (as seen from
"iptables -L" and "ipchains -L", respectively).

Jeff

--
Add an underscore between 'd' and 's' and remove the first three
letters of the alphabet for email.

In comp.os.linux.networking Jeff Krimmel <(E-Mail Removed)> wrote:
> On Fri, 25 Jun 2004 02:04:31 +0000, Andrei Ivanov wrote:
>>> mount clntudp_create: RPC: Port mapper failure - RPC: Timed out [...]
>>
>> Before running showmount/rpcinfo on the client host, start "tcpdump -n
>> udp" on both client and server. If you won't see inbound RPC (111/udp)
>> packets on server, then check iptables/ipchains (both with "-L -n"
>> options) on both sides to check whether there is something relevant in
>> there.

I'm sory for mis-guiding you :-( It should have been 'tcp' instead
of 'udp', or just 'port sunrpc'.

Open two terminals on client and one on server.

client1# rpcinfo -p server
client2# tcpdump -n port sunrpc
server1# tcpdump -n port sunrpc

On client you should see smth similar to the following (and rather similar
picture on server as well):

11:56:36.068049 client.978 > server.sunrpc: S 4099609454:4099609454(0)
win 5840 <mss 1460,sackOK,timestamp 26468710 0,nop,wscale 0> (DF)
11:56:36.068265 server.sunrpc > client.978: S 275121978:275121978(0)
ack 4099609455 win 32120 <mss 1460> (DF)
11:56:36.068368 client.978 > server.sunrpc: . ack 1 win 5840 (DF)
11:56:36.068566 client.978 > server.sunrpc: P 1:45(44) ack 1 win 5840 (DF)
11:56:36.068747 server.sunrpc > client.978: . ack 45 win 32120 (DF)
11:56:36.069303 server.sunrpc > client.978: P 1:373(372) ack 45 win 32120 (DF)
11:56:36.069364 client.978 > server.sunrpc: . ack 373 win 6432 (DF)
11:56:36.075280 client.978 > server.sunrpc: F 45:45(0) ack 373 win 6432 (DF)
11:56:36.075458 server.sunrpc > client.978: . ack 46 win 32120 (DF)
11:56:36.075604 server.sunrpc > client.978: F 373:373(0) ack 46 win 32120 (DF)
11:56:36.075667 client.978 > server.sunrpc: . ack 374 win 6432 (DF)

You should be 'root' on both computers.

There are portmapper's running on both client and server, right?
Also, on client you should have lock/stat daemons running (started
by /etc/rc.d/init.d/nfslock script), and on server - lockd/statd,
as well as nfs/mount daemons (/etc/rc.d/init.d/nfs).

--
andrei

On Fri, 25 Jun 2004 19:09:49 +0000, Andrei Ivanov wrote:

> In comp.os.linux.networking Jeff Krimmel <(E-Mail Removed)>
> wrote:
>> On Fri, 25 Jun 2004 02:04:31 +0000, Andrei Ivanov wrote:
>>>> mount clntudp_create: RPC: Port mapper failure - RPC: Timed out [...]
>>>
>>> Before running showmount/rpcinfo on the client host, start "tcpdump -n
>>> udp" on both client and server. If you won't see inbound RPC (111/udp)
>>> packets on server, then check iptables/ipchains (both with "-L -n"
>>> options) on both sides to check whether there is something relevant in
>>> there.
>
> I'm sory for mis-guiding you :-( It should have been 'tcp' instead of
> 'udp', or just 'port sunrpc'.
>
> Open two terminals on client and one on server.
>
> client1# rpcinfo -p server
> client2# tcpdump -n port sunrpc
> server1# tcpdump -n port sunrpc

[snip expected output]

I did the three commands you listed above, and I see the expected output
on the client, but I see nothing on the server. If I reverse the two, I
can see everything on both systems (i.e., when I "rpcinfo -p client" from
the server and tcpdump on both).

The client can ping the server and vice versa, but for some reason the
client cannot see the server via RPC. The server can, however, see the
client via RPC. I have been looking a lot at this problem, and it seems as
though somehow the "route" command may be involved. Do you think this is
somehow a problem of the client not having the correct route to the
server? I know so very little about this that any help would be
appreciated.

Thanks,

Jeff

--
Add an underscore between 'd' and 's' and remove the first three
letters of the alphabet for email.

On Fri, 25 Jun 2004 13:42:59 -0700, Jeff Krimmel wrote:

> On Fri, 25 Jun 2004 19:09:49 +0000, Andrei Ivanov wrote:
>
>> In comp.os.linux.networking Jeff Krimmel <(E-Mail Removed)>
>> wrote:
>>> On Fri, 25 Jun 2004 02:04:31 +0000, Andrei Ivanov wrote:
>>>>> mount clntudp_create: RPC: Port mapper failure - RPC: Timed out [...]
>>>>
>>>> Before running showmount/rpcinfo on the client host, start "tcpdump -n
>>>> udp" on both client and server. If you won't see inbound RPC (111/udp)
>>>> packets on server, then check iptables/ipchains (both with "-L -n"
>>>> options) on both sides to check whether there is something relevant in
>>>> there.
>>
>> I'm sory for mis-guiding you :-( It should have been 'tcp' instead of
>> 'udp', or just 'port sunrpc'.
>>
>> Open two terminals on client and one on server.
>>
>> client1# rpcinfo -p server
>> client2# tcpdump -n port sunrpc
>> server1# tcpdump -n port sunrpc
>
> [snip expected output]
>
> I did the three commands you listed above, and I see the expected output
> on the client, but I see nothing on the server. If I reverse the two, I
> can see everything on both systems (i.e., when I "rpcinfo -p client" from
> the server and tcpdump on both).
>
> The client can ping the server and vice versa, but for some reason the
> client cannot see the server via RPC. The server can, however, see the
> client via RPC. I have been looking a lot at this problem, and it seems as
> though somehow the "route" command may be involved. Do you think this is
> somehow a problem of the client not having the correct route to the
> server? I know so very little about this that any help would be
> appreciated.

And I suppose I should mention that the client in this case already has an
existing NFS connection to a different server, and the server in this case
is already successfully acting as an NFS server to different clients. So,
the proper NFS services are definitely running from both sides.

Jeff

--
Add an underscore between 'd' and 's' and remove the first three
letters of the alphabet for email.

In comp.os.linux.networking Jeff Krimmel <(E-Mail Removed)> wrote:
> I did the three commands you listed above, and I see the expected output
> on the client, but I see nothing on the server.

Do you mean that you see both packets going *from* client to server,
and packets going in opposite direction, from server *to* client?
If so, check MAC addresses on the server (ifconfig) and on the
client (arp -a). I guess you'll see different MACs for server's
IP address.

--
andrei

On Fri, 25 Jun 2004 21:35:51 +0000, Andrei Ivanov wrote:

> In comp.os.linux.networking Jeff Krimmel <(E-Mail Removed)>
> wrote:
>> I did the three commands you listed above, and I see the expected
>> output on the client, but I see nothing on the server.
>
> Do you mean that you see both packets going *from* client to server, and
> packets going in opposite direction, from server *to* client? If so,
> check MAC addresses on the server (ifconfig) and on the client (arp -a).
> I guess you'll see different MACs for server's IP address.

I can see the client sending packets toward the server, but I see nothing
on the server.

I have done some more reading, and it looks like my problem might be
related to the two network interfaces I have set up on the server. The
server is an NFS server already but only on a second network interface. I
am trying to mount an NFS partition via the server's first network
interface. Is it possible for an NFS server to be set up on only one of
the two interfaces? If so, how can I get the server to act as an NFS
server on _both_ of its network interfaces?

Thanks,

Jeff

--
Add an underscore between 'd' and 's' and remove the first three
letters of the alphabet for email.