Issues with WD TV live, Linkstation Live running Twonky

[hpeyton]

I don't know if anyone else is having this issue but I just got a WD TV Live and was planning on using the Linkstation running Twonky to stream content. I can access my shares on the NAS through the WD TV, I can access Twonky on my laptop, I can access WMP server from another laptop but when I connect my WD TV to the Linkstation Nas running Twonky 4.4.18 it connects for about 1-3 sec then says that the network is unreachable or some nonsense. It is on a wired network and like I said it connects to everything else even the laptop over wifi. Has anyone else run into this issue. I even tried using a different version of Twonky and it didn't work either.

Any help would be appreciated.

[PeeBee]

Has the WD TV Live been recognised correctly on the Twonky Clients/Security config page?

PB

[hpeyton]

PeeBee,

Yes it shows up in the client list. I grabbed this from the log.
Twonky server .13
WDTV .18

09:48:28:511 LOG_HTTP:HTTP_send_receive GET /ContentDirectory.xml HTTP/1.1
Host: 192.168.0.13:9000
User-Agent: INTEL_NMPR/2.1 DLNADOC/1.50 Intel MicroStack/1.0.1423


09:48:28:512 LOG_HTTP:HTTP_send_header HTTP/1.1 200 OK
Content-Type: text/xml; charset="utf-8"
Content-Length: 10248
Date: Sat, 02 Jan 2010 15:48:28 GMT
Accept-Ranges: bytes
Connection: keep-alive
EXT:
Server: Linux/2.x.x, UPnP/1.0, pvConnect UPnP SDK/1.0


09:48:28:525 LOG_CLIENT_DB:The entry found in known clients list is already validated (ip=192.168.0.18)
09:48:28:525 LOG_CLIENT_DB:checking http header for entry ip=192.168.0.18, mac=
09:48:28:526 LOG_CLIENT_DB:Checking http header to find a matching client.db entry (ip=192.168.0.18)
09:48:28:526 LOG_CLIENT_DB:Found matching candidate for client using the http header (ip=192.168.0.18) id=49
09:48:28:527 LOG_CLIENT_DB:already using matched client id (ip=192.168.0.18) id=49
09:48:28:527 LOG_CLIENT_DB:HH:Setting client adaptation to 49 (ip=192.168.0.18)
09:48:28:527 LOG_CLIENT_DB:UPDATE:hh updated client: ip=192.168.0.18,mac=00:90:A9:73:09:3B,id=49,src=1,ip upd=1,id upd=1,dd chk=1,fix=0,fn=WDTVLIVE,udn=uuid:22b9bad2-0090-a973-093b-b3a710e1a576

09:48:28:535 LOG_HTTP:HTTP_send_receive GET /ConnectionManager.xml HTTP/1.1
Host: 192.168.0.13:9000
User-Agent: INTEL_NMPR/2.1 DLNADOC/1.50 Intel MicroStack/1.0.1423


09:48:28:536 LOG_HTTP:HTTP_send_header HTTP/1.1 200 OK
Content-Type: text/xml; charset="utf-8"
Content-Length: 4852
Date: Sat, 02 Jan 2010 15:48:28 GMT
Accept-Ranges: bytes
Connection: keep-alive
EXT:
Server: Linux/2.x.x, UPnP/1.0, pvConnect UPnP SDK/1.0


09:48:28:544 [Error] - LOG_HTTP:HTTP_get_header Cannot receive header, clientSocket=35, nBytesReceived=0
09:48:28:544 LOG_HTTP:HTTP_send_receive received no header in HTTP_send_receive, propably client closed socket, URL=http://192.168.0.13:9000/
09:48:29:415 LOG_CLIENT_DB:The entry found in known clients list is already validated (ip=192.168.0.18)
09:48:29:415 LOG_CLIENT_DB:checking http header for entry ip=192.168.0.18, mac=
09:48:29:415 LOG_CLIENT_DB:Checking http header to find a matching client.db entry (ip=192.168.0.18)
09:48:29:416 LOG_CLIENT_DB:Found matching candidate for client using the http header (ip=192.168.0.18) id=49
09:48:29:416 LOG_CLIENT_DB:already using matched client id (ip=192.168.0.18) id=49
09:48:29:417 LOG_CLIENT_DB:HH:Setting client adaptation to 49 (ip=192.168.0.18)
09:48:29:417 LOG_CLIENT_DB:UPDATE:hh updated client: ip=192.168.0.18,mac=00:90:A9:73:09:3B,id=49,src=1,ip upd=1,id upd=1,dd chk=1,fix=0,fn=WDTVLIVE,udn=uuid:22b9bad2-0090-a973-093b-b3a710e1a576

09:48:29:427 LOG_HTTP:HTTP_send_receive GET /DeviceDescription.xml HTTP/1.1
Host: 192.168.0.13:9000
User-Agent: INTEL_NMPR/2.1 DLNADOC/1.50 Intel MicroStack/1.0.1423


09:48:29:428 LOG_HTTP:HTTP_send_header HTTP/1.1 200 OK
Content-Type: text/xml; charset="utf-8"
Content-Length: 2195
Date: Sat, 02 Jan 2010 15:48:29 GMT
Accept-Ranges: bytes
Connection: keep-alive
EXT:
Server: Linux/2.x.x, UPnP/1.0, pvConnect UPnP SDK/1.0


09:48:29:435 LOG_CLIENT_DB:The entry found in known clients list is already validated (ip=192.168.0.18)
09:48:29:435 LOG_CLIENT_DB:checking http header for entry ip=192.168.0.18, mac=
09:48:29:436 LOG_CLIENT_DB:Checking http header to find a matching client.db entry (ip=192.168.0.18)
09:48:29:436 LOG_CLIENT_DB:Found matching candidate for client using the http header (ip=192.168.0.18) id=49
09:48:29:437 LOG_CLIENT_DB:already using matched client id (ip=192.168.0.18) id=49
09:48:29:437 LOG_CLIENT_DB:HH:Setting client adaptation to 49 (ip=192.168.0.18)
09:48:29:437 LOG_CLIENT_DB:UPDATE:hh updated client: ip=192.168.0.18,mac=00:90:A9:73:09:3B,id=49,src=1,ip upd=1,id upd=1,dd chk=1,fix=0,fn=WDTVLIVE,udn=uuid:22b9bad2-0090-a973-093b-b3a710e1a576

Thanks for the help.

[MikeTNT]

Same problem here with TMS 4.4.18 on my Fritz!Box 7270 (twonkymedia-mipsel-uclibc-0.9.28-4.4.18) and WD TV Live.
I also tested 4.4.17 and an old 4.3 without success..

The server works without problems. I can connect with PS3 and my DBox2 (neutrino), but as soon as I use the WD TV Live, the connection interupts after 2 - 3 seconds.
To see, if there is a problem with this version at all, I installed the windows version of TMS 4.4.18 on my Win7-System.
Result: 4.4.18 under windows works perfect together with WD TV Live

So I hope someone is able to find out, why the linux version is not connectable by wd tv live although other client have no problems.

Has the WD TV Live been recognised correctly on the Twonky Clients/Security config page?

PB

It is recognised as Generic DLNA 1.5 on my FB7270 (and working under Windows with 4.4.4 as Generic Media Receiver, with 4.4.18 as Generic DLNA 1.5 and with 5.2 as WDTV). I have tried to change the settings on my FB 77270, but new settings has been ignored.

[schiggi]

+1

Another one with the same problem. Any help?

[MikeTNT]

Now I have installed 5.1.2 on my FB7270 (twonkymedia-mipsel-uclibc-0.9.28-5.1.2). With this version I can use WD TV Live 30 - 60 seconds and the WD TV is recognized as WD TV. Which log-information could be interesting? The log is huge...

Nethertheless here is the download to the my log file (38,8 MB): http://84.38.67.209/downloads/twonky.log

To understand the log:
WD TV has been activated. I connected to the twonky media server 5.1.2 with WD TV Live, I choosed a Webcast and could hear radio, after 30 - 60 seconds WD TV has been disconnected (a problem with the server occured) and I copied the log.
So I hope all needed information are in this log to find out the disconnect reason.

cu Mike