I've just been fighting the same issue on a SL 4.7 system (kernel
2.6.9-78.0.17) and found the same solution. If you look inside
/etc/init.d/nfs you will see that sysctl is called to update
the appropriate parameters. However this does not work, and I did
discover that the parameters do not exist when the "sysctl -w" is
done.

John

Eve V. E. Kovacs wrote:
> Yes, I tore my hair out on this one last year. The solution is:
> In modprobe.conf on the nfs server add the following line:
> 
> options lockd nlm_udpport=6667 nlm_tcpport=6667
> 
> (here 6667 is the port number to which lockd is fixed)
> 
> The reboot your server.
> 
> Eve
> 
> On Tue, 21 Apr 2009, Ken Teh wrote:
> 
>> Date: Tue, 21 Apr 2009 17:02:04 -0500
>> From: Ken Teh <[log in to unmask]>
>> To: scientific-linux-users <[log in to unmask]>
>> Subject: kernel lockd does not honor requested lockd ports
>>
>> I've fixed the various nfs ports in my firewall config and have 
>> propagated these ports to /etc/sysconfig/nfs.  All the ports are 
>> honored except for the lockd ports.  I've even tried setting the ports 
>> in sysctl.conf and appending them to the kernel boot in grub.conf.  
>> rpcinfo -p shows that the kernel (2.6.18-128.1.6.el5) basically 
>> ignores me.  NFS clients are mounting via NFSv3.  Ignoring the lockd 
>> numbers creates apparently creates problems for some applications, 
>> presumably because the application is requesting file locks.  For 
>> example, firefox won't run when launched in a user's home directory 
>> that is mounted remotely from the server.
>>
>> Has anyone seen this problem?  What's the fix?
>>
>> Ken
>>
> 
> ***************************************************************
> Eve Kovacs
> Argonne National Laboratory,
> Room F149, Bldg. 362, HEP
> 9700 S. Cass Ave.
> Argonne, IL 60439 USA
> Phone: (630)-252-6208
> Fax:   (630)-252-5047
> email: [log in to unmask]
> ***************************************************************