Personally, I'd never hard mount them. This can cause all sorts of timeout errors if the share goes awol.
Here's an example from my main server, Ubuntu Edgy /etc/exports: /home/mm *.greengecko.co.nz(rw,no_root_squash) 10.0.0.0/24(rw,no_root_squash) 192.168.10.0/24(ro) 192.168.12.0/24(ro) Which allows access to all of the machines in the greengecko.co.nz domain, and anyone on the 10.0.0.0/24, 192.168.10.0/24 and 192.168.12.0/24 subnets, with varying access rights ( rw and ro ). ( no_root_squash allows root to have root access on the share, so don't worry about that. Then run exportfs -a to enable any changes. On the client, Ubnuntu Feisty, I have the following in my /etc/fstab: 10.0.0.xxx:/home/mm /mm nfs rsize=8192,wsize=8192,timeo=14,soft,intr 0 0 All works ok here. Steve On Mon, 09 Jul 2007 19:16:35 +1200 Kerry Mayes <[EMAIL PROTECTED]> wrote: > Cool, I'll try that in the morning. > > On 09/07/07, Matthew Gregan <[EMAIL PROTECTED]> wrote: > > Failing that, run rpcinfo on the client to make sure it can talk to the > > server's portmapper: > > > > % /usr/sbin/rpcinfo -p server > > ... > > 100003 2 udp 2049 nfs > > 100003 3 udp 2049 nfs > > 100003 4 udp 2049 nfs > > ... > > > > If rpcinfo doesn't work, make sure the appropriate services are running and > > there are no firewalls blocking portmapper and NFS traffic. > > > > Cheers, > > -mjg > > -- > > Matthew Gregan |/ > > /| [EMAIL PROTECTED] > >
