Choosing a sharing protocol for my NAS/home network.

Fatglow

Reputable
Oct 11, 2015
4
0
4,510
I am planning to build a NAS box to store and access files from computers on my home network, which has a mix of devices- Windows, Linux and Mac. I would like to mount users folders on the NAS on the clients as either folders or drives. I don't really care as long as I can treat the stuff on the server as if it were a local file.
I have had bad experiences with smb sharing between Windows and Linux in the past, so I am hesitant to use it, but it does seem to be the standard. Some people use FTP/SFTP on their LAN others do it over ssh, and then there are other less-discussed options like iSCSI.
I really don't get what the pros and cons are of each transfer protcol are, although it is my understanding that FTP is a bit faster and Samba is more configurable and in theory should be easiest to set up.
I am interested in which protocols people prefer for a NAS on a LAN and why. I'm honestly not sure exactly what my criteria should be, I just know want reasonable speed, good handling of large files, and minimal problems connecting from client devices.
Anyone care to advise?
 
Solution
Any decent NAS OS should support multiple protocols operating at once.

I'm using OMV on an old P4 system. It actually uses very little system resources when streaming and transferring files, so any modern system should be able to handle it with ease. Implementing RAID will require more CPU power and RAM.

Mostly using SMB for an all Windows PC network, and only use FTP when accessing from the WAN. OMV does support other protocols including NFS and SSH.

Using DLNA for streaming to other media devices (game consoles, tablets, TV media devices, mobile phones). I can say that DLNA is hassle-free and all devices will readily see any DLNA shared folders.

kanewolf

Titan
Moderator
Mac and Linux would normally use NFS for sharing. Windows definitely prefers SMB. Commercial NAS units can support both protocols for any shared folder. I guess it will depend on what software you plan on using as the OS for your homemade NAS.
 

Fatglow

Reputable
Oct 11, 2015
4
0
4,510
Well, I was going to choose my NAS OS based primarily on which one will be the easiest to get to talk to my client machines. It sounds like SMB, or try out an NFS extension on Windows. So I guess the real question is "Which NAS OS has the easiest to set up SMB?"
Maybe I should create another topic in a networking forum to discuss that.
 

Fatglow

Reputable
Oct 11, 2015
4
0
4,510
I am considering NAS OS's, although FreeNAS is out because I don't want to spring for server hardware. I am considering OpenMediaVault, unRAID, Amahi, and ClearOS right now.
A commercial NAS with 6 drive bays and enough power for video streaming would probably cost more than building an equivalent PC. If I can choose the right OS for it.
 

kanewolf

Titan
Moderator
You don't have to have server hardware for FreeNAS. You do have to have 8GB RAM. I don't know of any other requirements that a desktop PC can't meet.
The commercial NAS has the benefit of "it just works" out of the box. Plug some disks in and go. No muss no fuss. I am a big proponent of appliance NAS units because of the simplicity. I would rather spend time using my devices than configuring them.
 

BuddhaSkoota

Admirable
Any decent NAS OS should support multiple protocols operating at once.

I'm using OMV on an old P4 system. It actually uses very little system resources when streaming and transferring files, so any modern system should be able to handle it with ease. Implementing RAID will require more CPU power and RAM.

Mostly using SMB for an all Windows PC network, and only use FTP when accessing from the WAN. OMV does support other protocols including NFS and SSH.

Using DLNA for streaming to other media devices (game consoles, tablets, TV media devices, mobile phones). I can say that DLNA is hassle-free and all devices will readily see any DLNA shared folders.
 
Solution