2011-09-09, 15:05
_-Sky-_ Wrote:@canadave : are you sharing something without necessary login/password on your NAS ?
Sorry, I don't understand what exactly you're asking.
_-Sky-_ Wrote:@canadave : are you sharing something without necessary login/password on your NAS ?
canadave Wrote:Sorry, I don't understand what exactly you're asking.I mean do you have a public sharing, which does not require providing a login and password ?
_-Sky-_ Wrote:This behavior is on "Lion compatible" sharing (OS Lion, recently upgraded NAS) only or with every kind of share ?
canadave Wrote:OK, it sort of works for me. It's something on my side, with my NAS, that's not working; it works fine on my Mac Pro and my laptop.
http://pastebin.com/a5pKAPKh
It looks to me like it's trying to connect to port 548 on my NAS...not sure if my Synology is listening on port 548 for AFP?
I'll do some more investigating.
*** EDIT ***: the Synology DOES use port 548 for AFP. And it is enabled (have been using it for my own computer LAN connections to the NAS for some time now). But not working in this case with the ATV2. That's strange....hmmmm.........
*** EDIT 2 ***: Duhhrrr...let me try davilla's manual connect and see if that's the issue. I bet it is.
*** EDIT 3 ***: Yep, it works when I manually type in the username : password@IP/sharedfolder to access the share rather than browsing. It's too bad it doesn't "just work", but, oh well It works, bottom line! I'm playing TRON:Legacy 1080p .mkv file from my NAS to the ATV2 via wireless LAN, working great, no buffering/stuttering.
Memphiz Wrote:Yeah i don't know how to fix. It tries to cconect with out username/pass when using zeroconf - and the lib doesn't return a "auth required" or something like that. So this ZeroConf only works if you share public (without username and password).
Memphiz Wrote:Yeah i don't know how to fix. It tries to cconect with out username/pass when using zeroconf - and the lib doesn't return a "auth required" or something like that. So this ZeroConf only works if you share public (without username and password).I'm not sure if it can help, but the lib provides, for each share, flags telling, among other things, if the share is password protected
canadave Wrote:Fair enough.I didn't make the tests myself, but I read that AFP is faster and uses less CPU when using OSX machine as server.
Do you, Memphiz, or anyone else, offhand know...which is the more efficient network transport protocol in general, in terms of overhead etc...AFP or NFS?
turbinez Wrote:I have my media stored on my OS X 10.5.8 G5 PPC machine using SMB at the moment, would it benefit me from switching over to AFP instead? I mean will things be faster and smoother when it comes to streaming?Do you have streaming issues currently ?
turbinez Wrote:I have my media stored on my OS X 10.5.8 G5 PPC machine using SMB at the moment, would it benefit me from switching over to AFP instead? I mean will things be faster and smoother when it comes to streaming?There's an easy way to find out
turbinez Wrote:Sky, yes I am having stuttering or buffering issues. Seems to be happen randomly and I'm on a wired ethernet connection. Doesn't happen all the time though.You can try AFP, but don't forget your problem is not necessarily a network protocol issue. It can be a lot of other things : slow network, too heavy file, slow cpu, etc...
_-Sky-_ Wrote:I didn't make the tests myself, but I read that AFP is faster and uses less CPU when using OSX machine as server.
I simply tend to think that each protocol is the best in its native environment (SMB for Windows, AFP for OSX and NFS for Linux/UNIX/BSD)