From: Chris Penney <cpenney@gmail.com>
Subject: NAT & lockd
Date: Fri, 8 Apr 2005 09:25:08 -0400
Message-ID: <111aefd050408062546161db8@mail.gmail.com>
Reply-To: penney@msu.edu
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
To: nfs@lists.sourceforge.net
Sender: nfs-admin@lists.sourceforge.net
Errors-To: nfs-admin@lists.sourceforge.net

I have an new NFS server (2.6.11.5 w/ NFS-ALL) that serves some
clients that sit behind a NAT box (linux clusters).  It replaced a
SLES 8 file server.   The NAT box is a old RH8 box (soone to be
upgraded to SLES 9).  On the new NFS server I'm getting the following
messages from lockd:

nsm_mon_unmon: rpc failed, status=-13
lockd: cannot monitor x.x.x.x

With our old NFS server I never got any messages.  The IP address
x.x.x.x is that of the NAT box.  I'm curious if this means locking
does not work behind nat or if it means something else.  Is there
anything I can do here?  Would a 2.6.x based NAT box have a more up to
date iptables that supports lockd?  This is non-critical, I'm just
trying to understand.

   Chris


-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
NFS maillist  -  NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs