News:

RAID is not a replacement for a backup! Here's why.

Main Menu

Linkstation Live CHL Problems

Started by psyker, August 17, 2009, 04:08:11 AM

Previous topic - Next topic

psyker

   
Hi everyone,
 
I have just recently purchased  a Linkstation Live for the sole reason of sharing media between two Macs and a Sony Bravia TV (KDLW5500), however I am experiencing a couple of problems with getting the unit to work as I would expect it to:
 
1.  I have installed the latest version of  NAS Navigator for Mac (2.19) and it does not find the NAS drive.  I can however connect to the NAS by mapping the drive as a shared drive and can even access the admin control by typing in the IP address as normal.
 
I primarily have the drive connected to an Airport Extreme, however I have even tried connecting the drive to a network port on my Mac directly, and NAS Navigator still fails to pick it up.
 
I installed the software on a Windows partition and had no problems with this whatsoever.
 
Is this a problem with the software, or should I be enabling/disabling an option within MacOSX to allow NAS Navigator to connect to it?
 
 
2.  I am also having problems with streaming media to my TV.  Before I continue, just to let you I have connected the drive directly to my TV and via the Airport Extreme, which have given the exact same results.
 
The TV manages to view the NAS in its menu and I can actually navigate to and play my videos and music, however I am presented with a message along the lines of "Playback Not Available" after around 30 seconds into playing the media.  The connection seems to be there all the time, as I can then go back and play the same or a different media file, but doing so gives the same result as before regardless of what I select.
 
Before anyone says "contact Sony about this", I am 100% confident that my TV is not at fault here, and I can prove it:
 
a) The TV comes built in with a USB port.  I have copied some media files to my flash drive and managed to play these through the TV flawlessly.
 
b) I have done some research into a piece of software called Twonky Media Server, which I setup on my Mac to test things out of curiosity (check out their site at www.twonkyvision.de for more info).
 
Upon installing the software, I selected the media directories to share and managed to view these through my TV flawlessly without any connection interruptions.  To clarify, this is how I had this setup:
 
Computer/File Host > Airport Extreme via wireless connection > TV via wired connection
 
 
I am seriously considering returning the item, however I'd like to think I'm missing something really simple.  Can anyone offer any advice?  Is there yet again another button I forgot to press in setup somewhere?  Before anyone queries, I have set the ethernet frame size from default to 9,694 bytes and still have the same problems.
 

Many thanks in advance,
Matt 

Jotin

You should try a force flash of the firmware on the unit and also keep the units power swtich to on and not auto.

psyker

   

Thanks for your suggestion.  I have followed the steps on the sticky thread for forcing flashed firmware, however this has not fixed the problem.  I am still not able to connect using NAS Navigator via OSX (can still do it via Windows) and the media is still interrupted around 30 seconds in maximum and stops playing when I connect via my TV.

 

I can still access files on the drive via shared folders on OSX successfully. 

 

Could the unit I have be defective?  Can anyone else suggest anything? 


Browser ID: smf (is_webkit)
Templates: 4: index (default), Display (default), GenericControls (default), GenericControls (default).
Sub templates: 6: init, html_above, body_above, main, body_below, html_below.
Language files: 5: index+Modifications.english (default), Post.english (default), Editor.english (default), Drafts.english (default), StopForumSpam.english (default).
Style sheets: 4: index.css, attachments.css, jquery.sceditor.css, responsive.css.
Hooks called: 147 (show)
Files included: 35 - 1354KB. (show)
Memory used: 1005KB.
Tokens: post-login.
Queries used: 16.

[Show Queries]