- slide 1 of 3
Samba vs. NFS
First of all, what are the main features of the two?
- Windows can connect to it natively without installing third-party software.
- Assists in network browsing. With or without NetBIOS.
- Acts as a Windows NT®-style Primary Domain Controller (PDC).
- Acts as a Backup Domain Controller (BDC) for a Samba-based PDC.
- Acts as an Active Directory domain member server.
- Joins a Windows NT/2000/2003 PDC.
- Faster then Samba when transferring large files over the network.
- Easy to setup on any Linux system.
- Supports Kerberos for authentication.
- Has the ability to squash root so clients accessing the shares cannot access root files.
- Uses IP-addresses to authenticate the client. And, is thus easier to setup.
- slide 2 of 3
Which One Should I Pick?
Run Any Windows?
If you have some Windows boxes in the network, then it might be better to choose Samba/CIFS. Natively, Windows doesn't support NFS. You would have to get a third party client application to be able to access your NFS shares.
If You're Purely Linux:
However, if your network consists of Linux boxes only, then NFS is the choice you could make. The simple setup will allow you to authenticate clients by IP address. This is secure on smaller networks like at home or small businesses, but you should setup with Kerberos when you have a substantial network of 25 boxes or more. It will provide you with better authentication. This setup will be harder if you have 25 boxes or more, so you may want to get a Linux guru do this for you.
I recently upgraded my Samba client to CIFS. This will have a better integration for your Linux file systems. It's also easier to get the permission rights using CIFS over Samba clients. I find that CIFS is faster than the Samba client.
Transfer speed of files over 1GB are faster on the NFS server. I have Samba and NFS installed on my file server and can access Linux and Windows boxes. NFS is faster than Samba and CIFS clients.
- slide 3 of 3
If you run a small network with only a few boxes, then use NFS server but don't forget to use “root squash" to make sure you don't give anybody root access to directories on the file server.
If you have a larger network and you administer user accounts on the server, then NFS with Kerberos is probably a better choice.
If you have Windows-based boxes that need to access the file server, you could always purchase third-party software. As far as I know, there are no free NFS clients under Windows. So, you can opt for Samba server instead.