Re: nfs client does not find nfs server

Hello,
I see.

rpcinfo -p on the server
rpcinfo -p <server> on the client

They look the same.
I can find the server now using YAST after deactivating the firewalls
of both computers.

Nontheless I still have a problem:

server:/etc # mount -t nfs linuxserver.site:/ /linuxserver/
mount server reported tcp not available, falling back to udp
mount: RPC: Fehler des entfernten Systems - Keine Route zum
Zielrechner

Well last words are in German meaning:
mount: RPC: Mistake of the remote system - no route to the computer of
destination

server:/etc # rpcinfo -p
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
100024 1 udp 32770 status
100021 1 udp 32770 nlockmgr
100021 3 udp 32770 nlockmgr
100021 4 udp 32770 nlockmgr
100024 1 tcp 45631 status
100021 1 tcp 45631 nlockmgr
100021 3 tcp 45631 nlockmgr
100021 4 tcp 45631 nlockmgr
100005 1 udp 675 mountd
100005 1 tcp 676 mountd
100005 2 udp 675 mountd
100005 2 tcp 676 mountd
100005 3 udp 675 mountd
100005 3 tcp 676 mountd

I have doubts about the nlockmgr and I wonder whether this is good or
bad?

This is my hosts

# mappings for the TCP/IP subsystem. It is mostly
# used at boot time, when no name servers are running.
# On small systems, this file can be used instead of a
# "named" name server.
# Syntax:
#
# IP-Address Full-Qualified-Hostname Short-Hostname
#

127.0.0.1 localhost

# special IPv6 addresses
::1 localhost ipv6-localhost ipv6-loopback

fe00::0 ipv6-localnet

ff00::0 ipv6-mcastprefix
ff02::1 ipv6-allnodes
ff02::2 ipv6-allrouters
ff02::3 ipv6-allhosts
127.0.0.2 server.site server
192.168.0.126 server.site server
192.168.0.134 linuxserver.site linuxserver

And hosts.allow is:

portmap: 192.168.0.134

Bastian


They should look the same.

Normally you wouldn't have a firewall between an NFS server and its
client(s). While NFS itself uses a predictable port number (2049), as
does RPC (111), some other components do not, so you don't know in advance
what ports to open. NFS isn't secure anyway (there are enhancements in V4
but it's still not that good). NFS is designed to be used within a LAN
type environment where the other machines are reasonably trustworthy and
no firewall is required between them.

I suggest that you open your firewalls on both client and
server so that all traffic between them is permitted. If this is not
acceptable, you should consider whether NFS is the correct solution to
your data sharing requirement.

Regards, Ian


.

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)