SuSE 8 NFS problem

[mistafeesh]

My brain is now boiled. :confused: I'm using SuSE pro 8.1, and trying to export a particular directory with NFS. I'm pretty sure the server is in the wrong here, cause two clients (one SuSE 9.1 and one Mac OSX 10.3.4) can't connect to it...

Using the YaST2 NFS server config thingy, I have two exports:

/home/dan/Websites/
and
/

both have the settings:
Hosts wildcard: *
options: rw

It all says it's going fine, but I can't mount it on the other two machines. I've tried all sorts of different settings, but no banana...

There is a file in /etc which I guess relates to all this stuff called "exports"
its contents are just:
/home/dan/Websites/ *(rw)
/ *(rw)

Any ideas?

[serz]

How are you trying to mount them? Any errors?

[happybunny]

right, how are you mounting them from remote machines?

mount -t nfs server:/share /localdirectory

and what is the error?

[mistafeesh]

If I try the command happybunny suggests, I get this on the Mac (can't get to the other linux box at the mo as its booted into windoze):

"mount_nfs: bad MNT RPC: RPC: Timed out" repeated over and over.

previously I was trying to mount using yast on the linux box and NFSmanager on the Mac

[mistafeesh]

I just tried making an export from another SuSE 8.1 system (plugged in an old HDD to that machine), and could mount that fine, so it's definitely something wrong with the serving machine...

[mistafeesh]

sorted it - I think it was something to do with permissions. I put the option map_identities in, and chmodded the shared directory to 777

[thread_killer]

Yeah, directory permissions are a little different than actual file directories. (Yeah I know, a directory is also a file).

But-- where as with a text document or a script you would think of read as the "lowest" permission, followed by write, followed by execute (a script for example) when it comes to directories, you have to have execute before read or write. A directory with 666 permisions is unusable for a user to browse to or mount. Strange but true.