cant nfs mount a mac to my linux nfs server machine

[Tom H]

On Wed, Jul 13, 2011 at 5:18 PM, Ralph Blach <rcblach at gmail.com> wrote:
>
> I cannot mount a mac to my nfs fedora 13 linux machine
>
> Here is my exports file
>
> cat /etc/exports
> /home/colette                  *(rw,insecure)
>
> Here are the messages I get from the /var/log/messages
>
> Jul 12 18:32:18 chipblach kernel: statd: server rpc.statd not responding, timed out
> Jul 12 18:32:18 chipblach kernel: lockd: cannot monitor Colette-Blachs-MacBook-Pro.local
> Jul 12 18:32:48 chipblach kernel: statd: server rpc.statd not responding, timed out
> Jul 12 18:32:48 chipblach kernel: lockd: cannot monitor Colette-Blachs-MacBook-Pro.local
> Jul 12 18:32:48 chipblach kernel: lockd: server Colette-Blachs-MacBook-Pro.local not responding, timed out
> Jul 12 18:33:18 chipblach kernel: statd: server rpc.statd not responding, timed out
> Jul 12 18:33:18 chipblach kernel: lockd: cannot monitor Colette-Blachs-MacBook-Pro.local
> Jul 12 18:33:19 chipblach kernel: lockd: server Colette-Blachs-MacBook-Pro.local not responding, timed out
> Jul 12 18:33:49 chipblach kernel: lockd: server Colette-Blachs-MacBook-Pro.local not responding, timed out
> Jul 12 18:34:19 chipblach kernel: lockd: server Colette-Blachs-MacBook-Pro.local not responding, timed out

Does the OS X firewall allow incoming NFS connections?

The format of "/etc/exports" is different in OS X. You need
"/home/colette -network ... -mask ...". Exports are "rw" by default. I
have no idea whether there's an equivalent of "insecure"; it's needed
for an OS X box to access a Linux nfs export but is it needed in the
other direction?

Do you really have "/home/colette" existing and populated on the OS X
box? Or do you mean "/Users/colette"?