NFS, Finder and Interrupted Server Connection problem

Anything interesting logged in either of these files:

/var/log/kernel.log
/var/log/system.log

when you are having these problems?

Thanks
--macko

I'm having similar problems, or rather, the user I support is having similar problems.

The NFS server is a Redhat linux box (RHEL5).

I upgraded a Mac Mini to Snow Leopard, and set up an NFS share, using the same flags that I had used under Leopard: -i net -s -P -b

The user reported major problems when trying to access the NFS-shared files from the Finder, but no problem in Terminal.

What's more, when he tried to work from another machine, an iMac still running Leopard, that had the same NFS export mounted, it also froze up. So this is now a major problem, since we have several machines pointing at the same NFS share.

Here's what I see in the NFS client, the Snow Leopard Mac Mini:
Sep 30 20:59:38 hostname sandboxd[3989]: portmap(6490) deny file-read-data /private/etc/rpc
Sep 30 20:59:38 hostname sandboxd[3989]: portmap(6490) deny mach-per-user-lookup

On the NFS server (Linux):
Sep 30 20:07:54 hostname kernel: lockd: server 128.112.41.91 not responding, timed out
Sep 30 20:25:14 hostname last message repeated 3 times
Sep 30 20:27:46 hostname mountd[7629]: authenticated mount request from 128.112.201.186:1023 for /usr2 (/usr2)
Sep 30 20:28:14 hostname kernel: lockd: server 128.112.41.91 not responding, timed out

Google doesn't turn up much, but I did find one message saying to use "nolocks,locallocks" - I'm not sure where these get entered, and I'm not really sure what they entail for file integrity, especially since the NFS share is accessed from multiple clients.

Catemaco

Update :

I was able to get NFS working. Here's what happened in my case.

I am using tcp wrappers (hosts.allow, hosts.deny files) to restrict access to most services. When I do this on a Mac OS X Leopard machine, or a (Redhat) linux machine, I set tcp wrappers on the NFS server to accept traffic from the NFS client, but I don't have to specify anything in the hosts.allow file (or firewall) on the client.

Apparently on Snow Leopard, it works differently. I found it necessary to put a line in the hosts.allow file on the client to allow traffic from the NFS server. I did this, using the server host name. The host name has worked for me on other machines, for example, to allow the NFS client to mount a drive from the NFS server, I put the client host name in the hosts.allow file on the server.

For some reason, with Snow Leopard, the host name would not work. I had to put the host IP number in the hosts.allow file. Since I'm not really sure which service or port to allow, I used "ALL:IP number of host".

This got it working for me. I'm not sure why it should be different from Leopard, and I would rather not allow ALL traffic from the server, but at least it's working.

Does anyone know where Apple documents these things? I find their documentation even sparser that Microsoft's. They tell you the steps to do something, but they don't really explain what's going on. It's hard to find anything on tcp wrappers, for example, on the Mac.

Catemaco

I have this problem before. But it is work after I turned off the firewall of the Mac.