+- Kodi Community Forum (https://forum.kodi.tv)
+-- Forum: Support (https://forum.kodi.tv/forumdisplay.php?fid=33)
+--- Forum: General Support (https://forum.kodi.tv/forumdisplay.php?fid=111)
+---- Forum: OS independent / Other (https://forum.kodi.tv/forumdisplay.php?fid=228)
+---- Thread: Win Sharing Using DLNA to Sony Bravia KDL 46HX701 (/showthread.php?tid=132142)
Sharing Using DLNA to Sony Bravia KDL 46HX701 - coolguyojas - 2012-05-23
Hello Friends,
I am a complete newbie with Xbmc. I have a PC in my basement and my TV is in the living room upstairs. At present I am streaming movies, music and pictures by using Windows Media Player (WMP). the quality isn't that great so I thought of trying new software. While doing search on the internet, I came across XBMC. I installed in on my pc and added videos to the library.
Now when I try to access XBMC through my DLNA enabled TV (there is no direct connection between my TV and PC), it doesn't successfully establish a connection with XBMC. Am I missing something or this product was never designed/developed to stream to a DLNA certified device over LAN.
Thanks a lot for your support.
Regards
-OJ
RE: Sharing Using DLNA to Sony Bravia KDL 46HX701 - jmarshall - 2012-05-23
Can you detect XBMC using any other client? You've enabled the sharing of the library over UPnP etc?
Cheers,
Jonathan
RE: Sharing Using DLNA to Sony Bravia KDL 46HX701 - sialivi - 2012-05-23
Is it an "unauthorized access" error?
Certain hardware fails to access XBMC with that error. For example, my Pioneer reciever can't access XBMC even though my Panasonic TV can. The same reciever also works fine with other UPnP servers, such as WMP and MediaMonkey.
RE: Sharing Using DLNA to Sony Bravia KDL 46HX701 - coolguyojas - 2012-06-09
@jmarshall - The only other device I have is a Sony BD system. That doesn't even show XBMC during media server troubleshooting.
The result of the Media Server Troubleshooting is "Unsuccessful"
The error message displayed while doing Media Server Troubleshooting is "Compatible files could not be found"
@sialivi - Did you find any fix for your issue?