Yeah, I have the same problem here. I ended up making new mountpoints and assigning them explicitly as you did. I don't believe there's a fix for this.Quote:
Originally Posted by jabb
Other than that it's a great HOWTO, thank you malco2001! O:)
Printable View
Yeah, I have the same problem here. I ended up making new mountpoints and assigning them explicitly as you did. I don't believe there's a fix for this.Quote:
Originally Posted by jabb
Other than that it's a great HOWTO, thank you malco2001! O:)
This worked great until I rebooted. Once I rebooted my client, I lost my mount point to my server. I do have the fstab modified to contain this:
server.ip.address:/data /mnt/parolee nfs rsize=8192,wsize=8192,timeo=14,intr
any idea why it won't stay mounted when I log in?
I found a workaround for this. I have the mountpoints on the server under /media and I just did anQuote:
Originally Posted by george_apan
ln -s /media/example ~/example
Now I can see my mounted drives through the network under the home dir that I'm sharing using their symbolic links. No need to have multiple shares anymore.
EDIT: No, sorry, I thought it worked but it didn't. As soon as I added another drive that I was not sharing, the link wouldn't work. Sorry again... :-&
worked great first time around. one minor nuisance. when i boot up the client (my laptop) it seems to take a while for the files from the server to be mounted on the mount point. i'm thinking this could be because a) wireless networking and/or b) the server is an older machine and/or c) the share being mounted is 10+ gigs in size
is that probably the cause or is there something else that can be done? if not, oh well, it still works and that's great!
Help a Noob out. I get this error
wayne@asus:~$ sudo mount 192.168.0.2:/home/winninshare /home/winninshare
mount: 192.168.0.2:/home/winninshare failed, reason given by server: Permission denied
I did exactly as you said.I have 2 computers with static IPs with the following in my other computer's exports file
/home/winninshare 192.168.1.1/24(rw,no_root_squash,async)
Sooo, i should be able to mount the winninshare folder on my computer in /home/winninshare? or am i mistaken.
Thanks for the setup. This was exactly what I needed to get some hefty files off two Ubuntu machines with USB 1.1 ports. :shock: Cheers! ;)
After editing the /etc/exports file run
sudo exportfs -a
then
sudo /etc/init.d/nfs-kernel-server restart
should work then
Okay so heres the problem with me on this...
The server is working fine because from the machine that's running NFS Server, I can mount NFS mounts as a clinet (using either loopback or internal lan IP).
But if I use a laptop thats on the same lan and do something to the effect of :
'sudo mount 192.168.11.5:/media /test'
(the same exact line I use on the server machine to mount the NFS share)
it says 'mount to NFS server '192.168.11.5' failed: server is down.'
NFS runs on port 2049 if Im not mistaken and I even opened that up on my router directly to this machine (the server) and it still doesnt work. Can anyone help with this?
Chalk one up to stupidity.
One should always make sure the proper files are installed on the client computer before making any posts that shows that one is an idiot :)
okay ... i'm completely confused.
i have a very small network. my server only leases 10 dhcp addresses.
how the heck does this:
work out to be a range from 192.168.1.1 - 192.168.1.255 ??Quote:
192.168.1.1/24
if i edited it incorrectly, it told me that what came after the "/" was the netmask. so i changed the line to this:
which seemed to have no ill effect.Code:192.168.1.1/255.255.255.0
edit: despite my continued confusion as stated above, i still managed to make a working automatic nfs client and server connection on boot. so, i humbly offer my thanks to malco2001.