HOWTO: NFS Server/Client

[ozzyprv]

In post #406:
..................
And you have...
..................
Does this mean client "mark" can already write to the folder above or do you still have issues?

I still have the issue. I guess that @ post #406 I spoke too soon, I assumed that having read access was having rw access. I was wrong.

did you change their ID's via the GUI or the terminal?

Via terminal. Note that the users do not have the same UID. Both "sshare" groups (server and client) do have the same GID.

Thanks for trying to help!

[secure]

thanks.It's easy to understand and work

[confusion_music]

Does anyone know if it is possible for a share exported using NFS can also be exported using Samba? The reason for asking is I'm in the process of setting up my home folder as a share for a second linux box, but I would also like the share to be accessible by my wifes vista laptop and possibly another xp laptop.

Thanks for all the tips and advice in the thread so far.

[^_Pepe_^]

Does anyone know if it is possible for a share exported using NFS can also be exported using Samba? The reason for asking is I'm in the process of setting up my home folder as a share for a second linux box, but I would also like the share to be accessible by my wifes vista laptop and possibly another xp laptop.

Thanks for all the tips and advice in the thread so far.

Sure! I do it, in fact!

You should have NTFS formatted unit, to be easily detected by Windows.

[PaulHuffman]

Does anyone know if it is possible for a share exported using NFS can also be exported using Samba? The reason for asking is I'm in the process of setting up my home folder as a share for a second linux box, but I would also like the share to be accessible by my wifes vista laptop and possibly another xp laptop.

I thought I had tried this before but ran into permission problems. But today it worked and this will help me a lot. There's a old Solaris server in another department that stores some big sets of air photos. The airphotos are shared to other departments only through NFS shares that were made years ago by people brighter than those working there now. In order to get these NFS resources, they use expensive PC-NFS software. I've shown them how I use Samba on my Solaris server, but their eyes glaze over, and they nod vacantly. On my Ubuntu 9.10 PC, I just used the line "sudo mount 161.217.7.51:/vol/vol0/home ~/photoserver" where the IP is that the air photo server, and photoserver is a folder on my Ubuntu PC made for a mount point and it hooked right up. Then I went over to a Windows PC and went to Start>run>\\161.217.20.27, the IP of my Ubuntu PC, and photoserver appeared in the list of shares on Ubuntu. I clicked on it and it hooked right up after I gave windows my Ubuntu authentication. So now I can assign this mount a drive letter and finally be able to use these air photos directly on my windows PC.

[frenchn00b]

I had an issue and solved this this way. it works now! thanks

//***SOLVED: //***SOLVED: 

mount: RPC: Timed out
or 
mount.nfs: access denied by server while mounting 


So, first: 
Install NFS Server Support
at the terminal type
sudo apt-get install nfs-kernel-server nfs-common portmap
When configuring portmap do =not= bind loopback. If you do you can either edit /etc/default/portmap by hand or run:
sudo dpkg-reconfigure portmap
sudo /etc/init.d/portmap restart

the most important is : do =not= bind loopback.

a# dpkg-reconfigure portmap
Stopping portmap daemon....
update-rc.d: warning: portmap start runlevel arguments (S) do not match LSB Default-Start values (S 2 3 4 5)
Starting portmap daemon....
Restoring old RPC service information....
There are RPC services which were registered with the portmapper
before the configuration was changed.
You need to manually restart them in order for the changes to take effect.
Current registered services:
------------------------------------------------
    100024    1   udp  51647  status
    100024    1   tcp  43086  status
    100021    1   udp  48101  nlockmgr
    100021    3   udp  48101  nlockmgr
    100021    4   udp  48101  nlockmgr
    100021    1   tcp  47109  nlockmgr
    100021    3   tcp  47109  nlockmgr
    100021    4   tcp  47109  nlockmgr
    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
    100005    1   udp  60568  mountd
    100005    1   tcp  33252  mountd
    100005    2   udp  60568  mountd
    100005    2   tcp  33252  mountd
    100005    3   udp  60568  mountd
    100005    3   tcp  33252  mountd
------------------------------------------------





then : 
put this into: 
/etc/exports
/home   192.168.10.100:/24(rw,no_subtree_check,no_root_squash)



sudo /etc/init.d/portmap start
sudo /etc/init.d/nfs-common start
sudo /etc/init.d/nfs-kernel-server start 

rpcinfo -p localhost



mkdir /mnt/nfstest/ 
mount 192.168.10.100:/home/ -t nfs

//***SOLVED// 

mount: RPC: Timed out
or 
mount.nfs: access denied by server while mounting 


So, first: 
Install NFS Server Support
at the terminal type
sudo apt-get install nfs-kernel-server nfs-common portmap
When configuring portmap do =not= bind loopback. If you do you can either edit /etc/default/portmap by hand or run:
sudo dpkg-reconfigure portmap
sudo /etc/init.d/portmap restart

the most important is : do =not= bind loopback.

a# dpkg-reconfigure portmap
Stopping portmap daemon....
update-rc.d: warning: portmap start runlevel arguments (S) do not match LSB Default-Start values (S 2 3 4 5)
Starting portmap daemon....
Restoring old RPC service information....
There are RPC services which were registered with the portmapper
before the configuration was changed.
You need to manually restart them in order for the changes to take effect.
Current registered services:
------------------------------------------------
    100024    1   udp  51647  status
    100024    1   tcp  43086  status
    100021    1   udp  48101  nlockmgr
    100021    3   udp  48101  nlockmgr
    100021    4   udp  48101  nlockmgr
    100021    1   tcp  47109  nlockmgr
    100021    3   tcp  47109  nlockmgr
    100021    4   tcp  47109  nlockmgr
    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
    100005    1   udp  60568  mountd
    100005    1   tcp  33252  mountd
    100005    2   udp  60568  mountd
    100005    2   tcp  33252  mountd
    100005    3   udp  60568  mountd
    100005    3   tcp  33252  mountd
------------------------------------------------





then : 
put this into: 
/etc/exports
/home   192.168.10.100:/24(rw,no_subtree_check,no_root_squash)



sudo /etc/init.d/portmap start
sudo /etc/init.d/nfs-common start
sudo /etc/init.d/nfs-kernel-server start 

rpcinfo -p localhost



mkdir /mnt/nfstest/ 
mount 192.168.10.100:/home/ -t nfs

//***SOLVED//

[yens]

Does anyone know if it is possible for a share exported using NFS can also be exported using Samba? The reason for asking is I'm in the process of setting up my home folder as a share for a second linux box, but I would also like the share to be accessible by my wifes vista laptop and possibly another xp laptop.

Thanks for all the tips and advice in the thread so far.

I've been doing this for almost half an year but there were some permission problems. I have public folder what has write permission to all PCs. The issue was that if some creates folder via samba (no matter form linux or windows) the new folder was with only read permission to nfs users.
I solved this by adding this to the share definition in smb.conf:

create mode = 0777
force create mode = 0777
force directory mode = 0777

[ozzyprv]

I had an issue and solved this this way. it works now! thanks

frenchn00b,
I am having problems reading your post. Could you please tell me what were the "extra" or "particular" commands you used to solve the problem?

Thank you.

[Jose Catre-Vandis]

frenchn00b,
I am having problems reading your post. Could you please tell me what were the "extra" or "particular" commands you used to solve the problem?

Thank you.

frenchnoob is simply reiterating the original howto

[red71]

Hello,
I tried commands from this topic to mount my NAS (Qnap TS-210).
Those commandes worked perfectly
sudo mount -t nfs 192.168.71.1:/Qmultimedia /mnt/qnap210/Qmultimedia
OR
sudo /sbin/mount.nfs 192.168.71.1:/Qmultimedia /mnt/qnap210/Qmultimedia

but I can't make it in /etc/fstab/
I tried:
192.168.71.1:/Qmultimedia /mnt/qnap210/Qmultimedia nfs rw,rsize=8192,soft,wsize=8192,timeo=14,intr 0 0
OR
192.168.71.1:/Qmultimedia /mnt/qnap210/Qmultimedia nfs user 0 0

None works. Could anybody help me ?
Thanks in advance.