Best network protocol

  Thread Rating:
  • 0 Votes - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Post Reply
Smurff Offline
Junior Member
Posts: 4
Joined: Jul 2011
Reputation: 0
Post: #1
Hi all,

I have just purchased two atv2 and I have a QNAP 419 to share the video files on. Can anyone give me any advice on whats the fastest protocol to use as most of my files will be 1080 or 720 and both the atvs will be watching. I think smb but my friend says ftp.

Thanks
smurff
find quote
Maetrik Offline
Donor
Posts: 417
Joined: Jan 2011
Reputation: 1
Location: Berlin, Germany
Post: #2
I use nfs for my files and smb for pathsubstitution
find quote
a6unx Offline
Junior Member
Posts: 26
Joined: Nov 2011
Reputation: 0
Location: Leeds, United Kingdom
Post: #3
SMB is better in my experience with atV2. Sometime you get rights issues trying to write back into your N/W drive while using FTP
find quote
Benjopa Offline
Junior Member
Posts: 37
Joined: Feb 2011
Reputation: 0
Post: #4
I think SMB protocol is best solution if you don't have any Time Capsule/Airport Extreme.
find quote
bkim Offline
Junior Member
Posts: 20
Joined: Jan 2011
Reputation: 0
Post: #5
NFS>FTP>SMB/AFP

I haven't noticed any differences between smb and afp in terms of buffering. FTP is a noticeable improvement from those two, and NFS is by far the best. I have never had any buffering issues using NFS. The xbmc wiki does a nice job of explaining how to set this up
find quote
michaelstone Offline
Junior Member
Posts: 22
Joined: Jan 2012
Reputation: 0
Post: #6
nfs is what works well for me....smb had constant buffering...
find quote
melsom Offline
Junior Member
Posts: 15
Joined: Dec 2009
Reputation: 0
Post: #7
I've found that HTTP (Web Directory) works best on my ATV2. Never had any buffering issues, and all files, including 1080p starts playing within 1-2 seconds. Smile
find quote
Smurff Offline
Junior Member
Posts: 4
Joined: Jul 2011
Reputation: 0
Post: #8
Thanks guys. I will have a read Smile
find quote
laydojo Offline
Donor
Posts: 6
Joined: Jul 2011
Reputation: 0
Location: Orange County, CA
Post: #9
I find that SMB works best for me. I have used it very reliably from both a Windows PC acting as my file server, and more recently from my NAS when I migrated to it.

My NAS does support AFP and NFS. I have tried just for giggles to use the other protocols and while I was successful in establishing a connection with those, I did not see any performance difference regardless of protocol.
With a stable network connection I don't believe that one protocol will make the difference between buffering vs not.

I would say the protocol best used would be dictated by the device serving the files. Using a Windows PC, I would choose SMB. From a Linux PC, I'd recommend NFS. etc.
Your mileage, of course, may vary.
find quote
g-off Offline
Fan
Posts: 631
Joined: Aug 2011
Reputation: 3
Post: #10
It depends on your skill level and what you are trying to achieve.

If you are trying to push high bitrate over wireless then you should pick the lightest/fastest protocol you can implement. If you are using a wired connection it really shouldn't matter which one you use as long as your server can deliver data quickly enough.

If you are lazy like me and have a solid N-wireless connection and you don't try and run high bitrate content just use the easiest one for you.

Just don't use upnp as is won't work with the library.
find quote
renhack Offline
Junior Member
Posts: 32
Joined: Sep 2011
Reputation: 0
Post: #11
NFS is a faster read protocol. Period. Right now there is a bug in the way NFS is handled on Beta 1 that effects NFS shares on windows, this should be fixed for Beta 2. For linux based NAS like your QNAP, NFS is definitely the way to go.
find quote
Memphiz Offline
Team-Kodi Developer
Posts: 11,219
Joined: Feb 2011
Reputation: 114
Location: germany
Post: #12
renhack Wrote:NFS is a faster read protocol. Period. Right now there is a bug in the way NFS is handled on Beta 1 that effects NFS shares on windows, this should be fixed for Beta 2. For linux based NAS like your QNAP, NFS is definitely the way to go.

Are you revering to the 2gb file limit on windows?

AppleTV2/iPhone/iPod: HowTo find debug logs and everything else which the devs like so much: click here
HowTo setup NFS for XBMC: Wiki NFS
HowTo configure avahi (zeroconf): Wiki Avahi
READ THE IOS FAQ!: iOS FAQ
find quote
renhack Offline
Junior Member
Posts: 32
Joined: Sep 2011
Reputation: 0
Post: #13
There is no 2GB limit on 64bit "Services for Network File Service". I think that 2GB was the limit on "Windows Services for Unix".

I was referencing XBMC's overload of concurrent connections that causes Windows to disconnect the share.
find quote
Memphiz Offline
Team-Kodi Developer
Posts: 11,219
Joined: Feb 2011
Reputation: 114
Location: germany
Post: #14
renhack Wrote:There is no 2GB limit on 64bit "Services for Network File Service". I think that 2GB was the limit on "Windows Services for Unix".

I was referencing XBMC's overload of concurrent connections that causes Windows to disconnect the share.

I was refering to the 2gb limit which was in the XBMC for Windows on beta1. It wasn't server dependend but an XBMC for Windows issue.

And right - both are fixed in b2 Big Grin

AppleTV2/iPhone/iPod: HowTo find debug logs and everything else which the devs like so much: click here
HowTo setup NFS for XBMC: Wiki NFS
HowTo configure avahi (zeroconf): Wiki Avahi
READ THE IOS FAQ!: iOS FAQ
find quote
renhack Offline
Junior Member
Posts: 32
Joined: Sep 2011
Reputation: 0
Post: #15
Thanks for all the work on NFS support. Can't wait for B2.
find quote