Instead it stores that information in a binary database called NetInfo. It's hard to find anything on tcp wrappers, for example, on the Mac.The /etc/exports isn't used in X. They tell you the steps to do something, but they don't really explain what's going on. 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.ĭoes anyone know where Apple documents these things? I find their documentation even sparser that Microsoft's. Since I'm not really sure which service or port to allow, I used 'ALL:IP number of host'. I had to put the host IP number in the hosts.allow file.

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.įor some reason, with Snow Leopard, the host name would not work. I found it necessary to put a line in the hosts.allow file on the client to allow traffic from the NFS server. 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.Īpparently on Snow Leopard, it works differently. When I do this on a Mac OS X Leopard machine, or a (Redhat) linux machine, I set tcp wrappers on the NFS I am using tcp wrappers (hosts.allow, ny files) to restrict access to most services. 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. Sep 30 20:28:14 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:07:54 hostname kernel: lockd: server 128.112.41.91 not responding, timed out Sep 30 20:59:38 hostname sandboxd: portmap(6490) deny mach-per-user-lookup Sep 30 20:59:38 hostname sandboxd: portmap(6490) deny file-read-data /private/etc/rpc Here's what I see in the NFS client, the Snow Leopard Mac Mini: So this is now a major problem, since we have several machines pointing at the same NFS share. 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. The user reported major problems when trying to access the NFS-shared files from the Finder, but no problem in Terminal. 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 NFS server is a Redhat linux box (RHEL5).

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

Mac os nfs server