Re: nfs troubles

Freddy Freeloader wrote:

Freddy Freeloader wrote:

Hi All,

I'm having trouble getting NFS set up. Both the client and the server are running Sid. I have nfs-common and nfs-kernel-server installed on the server and nfs-common installed on the client.
uname -a on the server returns:

Linux Job 2.6.15-1-k7 #2 Mon Mar 6 15:42:39 UTC 2006 i686 GNU/Linux

uname -a on the client returns:

Linux Solomon 2.6.16-1-k7 #2 Mon Mar 6 15:42:39 UTC 2006 i686 GNU/Linux

rpcinfo -p on the server returns the following:

program vers proto port
100000 2 tcp 111 portmapper
100000 2 udp 111 portmapper
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 32770 nlockmgr
100021 3 udp 32770 nlockmgr
100021 4 udp 32770 nlockmgr
100021 1 tcp 44649 nlockmgr
100021 3 tcp 44649 nlockmgr
100021 4 tcp 44649 nlockmgr
100005 1 udp 614 mountd
100005 1 tcp 617 mountd
100005 2 udp 614 mountd
100005 2 tcp 617 mountd
100005 3 udp 614 mountd
100005 3 tcp 617 mountd
100024 1 udp 32772 status
100024 1 tcp 41554 status

rpcinfo -p client_name when run on the server returns the following:

program vers proto port
100000 2 tcp 111 portmapper
100000 2 udp 111 portmapper
391002 2 tcp 786 sgi_fam
100024 1 udp 32770 status
100024 1 tcp 43674 status

ps -A | grep rpc on the server returns the following:

6794 ? 00:00:00 rpciod/0
6798 ? 00:00:00 rpc.mountd
7015 ? 00:00:00 rpc.statd
7023 ? 00:00:00 rpc.idmapd

Portmap, nfsd, and lockd also show up using ps. rquotad/quotad shows up nowhere.
If I run rpcinfo -p server_name from the client I get the following error:

No Remote Programs registered

netstat -tlp run on the server returns the following:

tcp 0 0 *:nfs *:* LISTEN -
tcp 0 0 localhost.localdo:37826 *:* LISTEN 6559/python
tcp 0 0 *:printer *:* LISTEN 6760/inetd
tcp 0 0 *:617 *:* LISTEN 6798/rpc.mountd
tcp 0 0 *:44649 *:* LISTEN -
tcp 0 0 localhost.localdo:54506 *:* LISTEN 6556/hpiod
tcp 0 0 *:5900 *:* LISTEN 7322/vino-server
tcp 0 0 *:bacula-dir *:* LISTEN 7150/bacula-dir
tcp 0 0 *:bacula-fd *:* LISTEN 7139/bacula-fd
tcp 0 0 *:bacula-sd *:* LISTEN 7115/bacula-sd
tcp 0 0 localhost.localdo:spamd *:* LISTEN 6596/spamd.pid
tcp 0 0 *:sunrpc *:* LISTEN 6101/portmap
tcp 0 0 *:auth *:* LISTEN 6760/inetd
tcp 0 0 *:41554 *:* LISTEN 7015/rpc.statd
tcp 0 0 *:ftp *:* LISTEN 7085/proftpd: (acce
tcp 0 0 localhost.localdoma:ipp *:* LISTEN 6616/cupsd
tcp 0 0 192.168.1.5:ipp *:* LISTEN 6616/cupsd
tcp 0 0 *:postgresql *:* LISTEN 6860/postmaster
tcp 0 0 *:smtp *:* LISTEN 6750/exim4
tcp6 0 0 *:ssh *:* LISTEN 6882/sshd
tcp6 0 0 *:postgresql *:* LISTEN 6860/postmaster
tcp6 0 0 *:smtp *:* LISTEN 6750/exim4

Here is my /etc/exports file:

/home/ffreeloader solomon(rw,sync)

The above client is in my /etc/hosts.allow file.

I have read the NFS HOWTo on sourceforge. I have read the Debian wiki. It looks to me that the problem is most likely that rquotad/quotad not running is the problem, but why isn't it being started? I have Googled this quite a bit and can find nothing that seems to fit my situation.

One more thing I just found. Running a packet capture with wireshark (ethereal) I find the following:

The client's request to portmap is: V2 PORTMAP GETPORT call NFS (100003) V:3 TCP. The server's reply is: V2 GETPORT Reply PROGRAM_NOT_AVAILABLE

I do not understand where this reply comes from as rpcinfo clearly shows version 3 is running on tcp.

OK. I figured it out. There was a typo in my /etc/hosts.allow that was keeping the host out.


--
To UNSUBSCRIBE, email to debian-user-REQUEST@xxxxxxxxxxxxxxxx with a subject of "unsubscribe". Trouble? Contact listmaster@xxxxxxxxxxxxxxxx

Relevant Pages

  • SuSE 10.0 NFS vs. Firewall
    ... I am attempting to get NFS working; both client and server are running ... 3/min burst 5 LOG level warning tcp-options ip-options prefix ... 3/min burst 5 state NEW udp dpt:sunrpc LOG level warning tcp-options ... 3/min burst 5 state NEW tcp dpt:sunrpc LOG level warning tcp-options ...
    (alt.os.linux.suse)
  • Re: Firewall problems with NFS
    ... It seems to only allow use as an NFS client, since that worked fine when I tested it. ... U was surprised to see that TCP with tcp_adv_win_size=5 and rsize=8192 was as fast as UDP, ... 100005 1 udp 841 mountd ...
    (Fedora)
  • Re: mount.nfs internal error
    ... Whenever I try to mount from a server on my LAN, ... Adding a -o udp to the mount still fails ... Linux does not yet support nfs over IPv6, although rpcbind does support IPv6 queries.) ... 100000 4 tcp 111 portmapper ...
    (comp.os.linux.networking)
  • Trying to get NFS working with FreeBSD & OS X
    ... NFS client on a Mac OS X box. ... 100000 4 tcp 111 portmapper ... 100000 4 udp 111 portmapper ... 100021 0 udp 617 nlockmgr ...
    (comp.unix.bsd.freebsd.misc)
  • Trouble making NFS work with Mac OS X
    ... NFS client on a Mac OS X box. ... 100000 4 tcp 111 portmapper ... 100000 4 udp 111 portmapper ... 100021 0 udp 617 nlockmgr ...
    (freebsd-net)
Loading