Comments on: Set up NFS server on Fedora Core 5, OS X NFS Client

By: Josh

Josh — Fri, 02 May 2008 04:52:40 +0000

Hi, I'm trying to get this working and I keep getting told by finder that "the name or password is not correct".

My export file is this:

/media/Josh 192.168.1.101(rw,insecure,sync)

I then do an export -ra and restart nfs. I don;t get any errors on the server, just finder won't connect.

Running FC8 and OSX 10.5

By: di Lampedusa

di Lampedusa — Sat, 21 Oct 2006 22:43:58 +0000

It was the firewall! I had activated it during Fedora installation, so long ago that I did not remember it anymore… I found that just by deactivating it the connection went pretty OK, but then I also succeeded in opening just the necessary ports. For that I followed the instructions in http://www.linuxquestions.org/questions/showthread.php?t=294069. (Some ports need to be configured to become fixed, otherwise they will change after each nsf server restart).

By: di Lampedusa

di Lampedusa — Wed, 18 Oct 2006 22:32:43 +0000

Thanks for your quick reaction!

All your suggested tests passed.

My /etc/exports is simple:

/media/KAST 192.168.2.100(rw,sync,insecure)

Then I “exportfs -ra” and restart the nsf service.

I’ve also allowed 192.168.2.100 in /etc/hosts.allow

Still, when I do Go/Connect to server: nfs://192.168.2.110/media/KAST it keeps trying forever.

If I try it from a shell with

sudo mount -o -P 192.168.2.110:/media/KAST /mnt/KAST/

I get “NFS Portmap: RPC: Port mapper failure – RPC: Timed out”.

In my Fedora 5 laptop I check for rpcinfo -p and get, among others,

program vers proto port
100003 2 udp 2049 nfs
100003 3 udp 2049 nfs
100003 4 udp 2049 nfs
100003 2 tcp 2049 nfs
100003 3 tcp 2049 nfs
100003 4 tcp 2049 nfs

(Thus it is indeed running in an insecure port >1024).

I also tried sharing other directories, but that also fails.

Both computers are connected through a SMC7904BRA router in a local network, but the IP’s are always the same: ping, ssh and scp work fine in both directions!

By: Jon Todd

Jon Todd — Wed, 18 Oct 2006 20:25:56 +0000

Hey guys, I ran into this very problem too. Click connect on the mac and it just hangs there. There are a few things your should check:

Verify the client's IP. Despite using static IP assigning on my DHCP server, I would very often get a different IP on mac then what was in my exports file.
Ensure that the directory you are exporting exists and is at least readable by all
Make sure you're client can see the server. ping nfs.server.ip

If you still don't have luck throw your exports file up here and I'll take a look. The freezing is not an issue with your mac, it's either the connection or the NFS setup.

By: di Lampedusa

di Lampedusa — Wed, 18 Oct 2006 20:09:16 +0000

I have exactly the same problem as Matthieu, and I don’t have any clue. Also Fedora 5 – Mac OS X 10.4.7. I tested all the obvious things, restarted the nfs server, matched the users IDs, changed permissions as far as possible (I can’t chmod 777 my external USB HD, the one I want to share, mounted under /media. It remains 755 all the time, maybe that’s the thing, but don’t know how to solve that…)

By: Matthieu Chardon

Matthieu Chardon — Sat, 14 Oct 2006 23:23:40 +0000

Jon thank you for the help. This is exactly what I was looking for. I have a small problem however. I followed your instructions but when i try to connect to the nfs server from my macbook it just sits there idle.
I think that my error might come from the creation of the exports file. I used gedit to view it and it was empty. I added the line that you said, saved and closed it and followed the rest of the instructions/troubleshooting.

Let me know if you think of any other things.

Sincerely,

Matt

PS: I am using a linux machine that has fedora core 4 on it but I feel it should not matter.