NFS lock problem

[Dean Allen Provins <provinsd@telusplanet.net>]

Hello:

I clobbered my client system accidently after discovering I could no
longer boot due to a bad master boot record.  When I got it back up, the
NFS system began to act strangely.

I can read/write the mounted file systems on the server (a 'sarge'
system), but cannot run mutt, openoffice or iceweasel as they try to
set up a lock on the server.  They hang until I kill them.  The only
message that results is:

	lockd:  couldn't create RPC handle for 192.168.1.2

The server is 192.168.1.2 and has not changed its OS or NFS
configuration for months.  The client (192.168.1.3) is from the testing
distribution and has NFS configured (and successfully mounts the remote
file systems).  The client kernel is 2.6.20.2; the server is a stock
kernel: 2.4.27-2-386.

For 'iceweasel' (firefox), the file that the system is trying to lock
is:
	~/.mozilla/firefox/h7y7nif1.default/.parentlock

For 'mutt', it is '/var/mail/provinsd' (/var/mail is mounted from the
server).

Any ideas for a solution?

Regards from Calgary,

Dean

-- 
			   Dean Provins, P. Geoph.
			    50.95033N, 114.03791E
			   provinsd@telusplanet.net
		         dprovins@alumni.ucalgary.ca
		  KeyID at at pgpkeys.mit.edu:11371: 0x9643AE65
	  Fingerprint: 9B79 75FB 5C2B 22D0 6C8C 5A87 D579 9BE5 9643 AE65