Date: Thu, 20 Jul 2006 19:43:16 +0200 From: David Landgren <david@landgren.net> To: David Kelly <dkelly@hiwaay.net> Cc: freebsd-questions@freebsd.org Subject: Re: Connection refusal for an NFS mount Message-ID: <44BFC0B4.5000108@landgren.net> In-Reply-To: <20060720164601.GA71581@Grumpy.DynDNS.org> References: <44BF9E40.7090104@landgren.net> <20060720164601.GA71581@Grumpy.DynDNS.org>
next in thread | previous in thread | raw e-mail | index | archive | help
David Kelly wrote: > On Thu, Jul 20, 2006 at 05:16:16PM +0200, David Landgren wrote: >> List, >> >> On an old Redhat box (address 172.17.0.18), I'm trying to mount an NFS= =20 >> export from a FreeBSD (5.2.1-RELEASE) box. Both machines are on the sa= me=20 >> network segment, and neither have any onboard firewalling rules. >=20 > [...] >=20 >> (I understand, from reading the handbook, that I should be using rpcbi= nd=20 >> rather than portmap). This server has been an NFS server in the past, = so=20 >> I know it worked at some point. I'm not sure if I'm missing a daemon i= n=20 >> the mix, or if there's something else I've overlooked. >> >> Any clues will be most graciously received :) >=20 > For starters try "showmount -e the.freebsd.ip.address" on the Linux box= > to see if the Linux box sees the NFS daemons on the FreeBSD machine. Hrm. # showmount -e 172.17.0.21 mount clntudp_create: RPC: Port mapper failure - RPC: Unable to receive > mountd needs to be running on the FreeBSD host (apparently yours is > running). When /etc/exports changes mountd needs to be informed: > kill -s HUP `cat /var/run/mountd.pid` Yup, know about that. > Also at least in the past Linux distributions defaulted NFS to > non-reserved ports. Your Linux may not be talking to the same ports as > the FreeBSD machine is listening. Let's have a look... # nmap 172.17.0.21 Starting nmap V. 3.00 ( www.insecure.org/nmap/ ) Interesting ports on bechet.bpinet.com (172.17.0.21): (The 1584 ports scanned but not shown below are in state: closed) Port State Service 21/tcp open ftp 22/tcp open ssh 25/tcp open smtp 37/tcp open time 80/tcp open http 199/tcp open smux 443/tcp open https 801/tcp open device 901/tcp open samba-swat 1011/tcp open unknown 1020/tcp open unknown 2049/tcp open nfs 3306/tcp open mysql 5308/tcp open cfengine 5432/tcp open postgres 5999/tcp open ncd-conf 8080/tcp open http-proxy My god there's a lot of crap on that box! Still, looks like NFS is=20 running. And according to the man page of the linux box: port=3Dn The numeric value of the port to connect to the NFS server on. If the port number is 0 (the default) then query the remote host's portmapper for the port number to use. If the remote host=E2s NFS daemon is not regis- tered with its portmapper, the standard NFS port number 2049 is used instead. So that sounds about right. I tried adding port=3D2049 explictly to the=20 mount command, but same error: "Connection refused" Well, thanks for your help. Beats me what I've done wrong. Thanks, David --=20 Much of the propaganda that passes for news in our own society is given=20 to immobilising and pacifying people and diverting them from the idea=20 that they can confront power. -- John Pilger
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?44BFC0B4.5000108>