Ken Foskey <[EMAIL PROTECTED]> writes: > The exports file was:
The exports file is pretty sensitive to errors, a space in the wrong place will ruin your case. (I don't even have to try to be lame) > /home/teachers/ 192.168.0.*(rw,no-rootsquash) I haven't seen no-rootsquash before, its no_root_squash over here. > server:/home/teachers /home/teachers nfs rw 0 0 The mount man page says you probably want hard,intr as options. But that isn't the cause of your problems. > The mount was being tried and I got a message that the mount was failing > but not authorised. The last part I got an RPC message from the client, > I think the firewall settings stopped the connection altogether. No idea about the RPC message, but the export file grants access to file systems to clients, and I think you get permission errors if a client tries to mount a file system it doesn't have access to (perhaps because of typos in the exports file). -- SLUG - Sydney Linux User's Group - http://slug.org.au/ More Info: http://lists.slug.org.au/listinfo/slug
