Jump to content

Samsung smart TVs no longer finding media over DLNA


Bazzz
 Share

Recommended Posts

* Yesterday I posted the same issue in the DLNA subforums. If x-posting is not ok, please remove the other post as I believe it is better suited here.

 

Since a few days ago my Samsung Smart TVs (2 in total) are no longer able to find any media on Emby. They do find the Emby server fine but claim that there are no videos/photos/etc. stored on it. I also have a Sony Smart TV which is working fine. I have checked the log files and found the info below. I believe this might be relevant because the TV is called '[TV]Vesta' so it seems to fail at updating something.

 

What can I do to make my Samsung TVs find the media on Emby again? 

 

Just for the record, both TVs have worked with Emby for months. They stopped working a few days ago.

 

Attached is a log file from today, there is a curious line in it:

2016-02-28 17:32:45.0657 Error UpnpContentDirectory: Error parsing item Id: V. Returning user root folder.

Extract from a log file from yesterday

2016-02-27 14:46:30.4169 Info HttpServer: HTTP GET http://192.168.178.37:8096/dlna/c3935fd57afa3f2d582f256e21d0cbd3/icons/logo120.png. UserAgent: 
2016-02-27 14:46:30.4325 Info HttpServer: HTTP Response 200 to 192.168.178.22. Time: 16ms. http://192.168.178.37:8096/dlna/c3935fd57afa3f2d582f256e21d0cbd3/icons/logo120.png
2016-02-27 14:46:31.8365 Error Dlna: Error updating device info for [TV]Vesta
    *** Error Report ***
    Version: 3.0.5871.0
    Command line: C:\Users\User\AppData\Roaming\Emby-Server\System\MediaBrowser.ServerApplication.exe
    Operating system: Microsoft Windows NT 6.1.7601 Service Pack 1
    Processor count: 2
    64-Bit OS: False
    64-Bit Process: False
    Program data path: C:\Users\User\AppData\Roaming\Emby-Server
    Application Path: C:\Users\User\AppData\Roaming\Emby-Server\System\MediaBrowser.ServerApplication.exe
    Unable to connect to the remote server
    System.Net.WebException
     at System.Net.HttpWebRequest.GetRequestStream(TransportContext& context)
     at System.Net.HttpWebRequest.GetRequestStream()
     at MediaBrowser.Common.Implementations.HttpClientManager.HttpClientManager.<SendAsyncInternal>d__1b.MoveNext()
    --- End of stack trace from previous location where exception was thrown ---
     at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
     at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
     at MediaBrowser.Common.Implementations.HttpClientManager.HttpClientManager.<SendAsync>d__5.MoveNext()
    --- End of stack trace from previous location where exception was thrown ---
     at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
     at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
     at MediaBrowser.Dlna.PlayTo.SsdpHttpClient.<SendCommandAsync>d__0.MoveNext()
    --- End of stack trace from previous location where exception was thrown ---
     at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
     at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
     at MediaBrowser.Dlna.PlayTo.Device.<GetTransportInfo>d__84.MoveNext()
    --- End of stack trace from previous location where exception was thrown ---
     at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
     at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
     at MediaBrowser.Dlna.PlayTo.Device.<TimerCallback>d__54.MoveNext()
    InnerException: System.Net.Sockets.SocketException
    No connection could be made because the target machine actively refused it 192.168.178.28:7676
     at System.Net.Sockets.Socket.DoConnect(EndPoint endPointSnapshot, SocketAddress socketAddress)
     at System.Net.ServicePoint.ConnectSocketInternal(Boolean connectFailure, Socket s4, Socket s6, Socket& socket, IPAddress& address, ConnectSocketState state, IAsyncResult asyncResult, Exception& exception)

Note that my Samsung TV are named '[TV]Vesta' and '[TV]Ceres', I have tried both and get a variety of different errors.

server-63592246803.txt

Edited by Bazzz
Link to comment
Share on other sites

I am using the app now and that works fine. I actually quite like the app, shame I didn't know about it earlier. :)

I still find it odd that DNLA stopped working from one day to another though.

Link to comment
Share on other sites

Dlna has to be tested individually on every single device. You make a change to improve one device, it can negatively impact another. That's just the way it's always going to be unfortunately.

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
 Share

×
×
  • Create New...