Date: Tue, 30 Dec 2003 06:40:06 +0300 From: Igor Pokrovsky <tiamat@comset.net> To: Rob <nospam@users.sourceforge.net> Cc: freebsd-stable@freebsd.org Subject: Re: NFS problem: "RPC: Port mapper failure" Message-ID: <20031230034006.GA518@doom.homeunix.org> In-Reply-To: <3FEFB9F4.7060500@users.sourceforge.net> References: <3FEECA99.4030603@users.sourceforge.net> <20031229034221.GA671@doom.homeunix.org> <3FEFB9F4.7060500@users.sourceforge.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, Dec 29, 2003 at 02:21:56PM +0900, Rob wrote: > This is what I get. > > The NFS server is 147.46.44.183 with gateway 147.46.44.1 > The NFS client is 147.47.254.184 with gateway 147.47.254.1 > > On the NFS server: > $ sockstat | grep portmap > daemon portmap 79693 3 udp4 *:111 *:* > daemon portmap 79693 4 tcp4 *:111 *:* > $ sockstat | grep nfsd > root nfsd 87 3 tcp4 *:2049 *:* > $ sockstat | grep mount > root mountd 84 3 udp4 *:1023 *:* > root mountd 84 4 tcp4 *:1023 *:* > > On the client: > $ rpcinfo -p 147.46.44.183 > rpcinfo: can't contact portmapper: RPC: Remote system error - > Operation timed out > > > On another computer with the same gateway as the server: > $ rpcinfo -p 147.46.44.183 > program vers proto port > 100000 2 tcp 111 portmapper > 100000 2 udp 111 portmapper > > > Any idea what could block the contact to the portmapper? > Could a network setup at one of the gateways cause these trouble, such > as a firewall (though I don't know anything about firewalls!) ? Probably this is the cause, as I don't see any other probable reason for your trouble. Try asking firewall admin, maybe connections to some ports are blocked. Or you can always try to specify different port to use by nfsd. -ip -- Reality is just a convenient measure of complexity. -- Alvy Ray Smith
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20031230034006.GA518>