On Wed, Mar 9, 2011 at 1:19 PM, Tom H <tomh0...@gmail.com> wrote:

> On Wed, Mar 9, 2011 at 2:28 AM, Scott Ferguson
> <prettyfly.producti...@gmail.com> wrote:
> > On 09/03/11 17:45, Liam Cassidey wrote:
> >>
> >> I've removed all entries from /etc/exports, have portmap and nfs-common
> >> running, the firewall down, have an empty /etc/hosts.deny and a single
> >> entry in hosts.allow (taken from the portmap man page):
> >
> > perhaps you could try something like this for hosts.allow
> >
> > nfsd: 192.168.x.y/255.255.255.255
> > rpcbind: 192.168.x.y/255.255.255.255
> > mountd: 192.168.x.y/255.255.255.255
>
> Or test first with an empty "/etc/hosts.allow".
>
>
So I've tested it with an empty /etc/hosts.allow, one with ALL: ALL and I
feel like every incarnation involving nfsd, rpcbind, mountd, portmap and
various ip's and masks. None seem to make any difference to the results I'm
seeing so far -- still the same old "svc: failed to register lockdv1 RPC
service (errno 13)." error.

Also, iptables has been completely disabled so there shouldn't be anything
at the network layer blocking it.

It's been suggested that their may be a bug in the version of nfs-common I'm
using. I have version 1:1.2.2-4 installed and it appears, at least according
to http://packages.debian.org/search?keywords=nfs-common, that this same
version is also in stable. So I guess my next question is: has anyone had
luck running an nfs server on any system since lenny? If so, what versions
of the 3 (portmap, nfs-common, and nfs-kernel-server) are you running and
with what kind of configuration?

Thanks for all the support so far.

Reply via email to