Jump to content

DLNA and Samsung UN32EH5300 and Marantz SR6008


smokey7722

Recommended Posts

smokey7722

I know theres been a few people posting they have this specific TV model working however for some reason mine won't detect and list my MB server.  According to my dashboard it is listing the TV as connected but if I go to Source it is not listed as it used to be (when I was using Serviio as the DLNA server).  I do have AllShare enabled and as I said, if I restart Serviio it picks it up immediately.  In addition my preliminary testing with the Marantz is similar, it shows up as an active device but the receiver itself does not see my MB server as a potential media server (and just like the Samsung, if I start the Serviio services, it shows up immediately there as well).  I have verified that Serviio is completely shutdown and there are no services running from it.  

 

Looking at a netstat to see what ports are listening for the MB service shows below:

PS C:\Users\adamz> netstat -ano | select-string 3028

  TCP    0.0.0.0:843            0.0.0.0:0              LISTENING       3028
  TCP    0.0.0.0:8945           0.0.0.0:0              LISTENING       3028
  TCP    10.0.0.8:8945          10.0.0.118:50793       ESTABLISHED     3028
  TCP    10.0.0.8:51881         23.23.156.240:80       ESTABLISHED     3028
  TCP    10.0.0.8:51883         108.162.197.196:80     ESTABLISHED     3028
  TCP    10.0.0.8:51884         108.162.197.196:80     ESTABLISHED     3028
  TCP    10.0.0.8:51885         108.162.197.196:80     ESTABLISHED     3028
  TCP    10.0.0.8:51889         66.147.244.231:80      CLOSE_WAIT      3028
  TCP    10.0.0.8:51892         10.0.0.124:8080        ESTABLISHED     3028
  UDP    0.0.0.0:7359           *:*                                    3028
  UDP    10.0.0.8:57251         *:*                                    3028
  UDP    127.0.0.1:57252        *:*                                    3028                

When I turn the TV on, or hit the refresh (A) button while on the Sources screen the MB log shows:

2014-03-22 13:27:04.5905 Error - PlayTo: Error updating device info
	The operation has timed out
	System.Net.WebException
	   at System.Net.HttpWebRequest.GetRequestStream(TransportContext& context)
	   at System.Net.HttpWebRequest.GetRequestStream()
	   at MediaBrowser.Common.Implementations.HttpClientManager.HttpClientManager.<SendAsync>d__7.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__65.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__48.MoveNext()
	
2014-03-22 13:27:11.0048 Debug - PlayTo: Controller disposed
2014-03-22 13:27:17.4865 Error - PlayTo: Error updating device info
	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.<SendAsync>d__7.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__65.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__48.MoveNext()
	InnerException: System.Net.Sockets.SocketException
	No connection could be made because the target machine actively refused it 10.0.0.196: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)

In addition, the Dashboard shows the TV as connected:

532df3fcaf005_ScreenShot20140322at13431P

 

Link to comment
Share on other sites

AgileHumor

I've had no issues with this TV (not receiver).   I'm assuming the problem is more with your server then the TV.  

 

Note - You are prompted the TV the first time the MB server plays to your tv (security feature).  Make sure you click "allow".

Link to comment
Share on other sites

7illusions

Just as @@AgileHumor pointed out, the security in the Samsung could very well be the issue. Just clear the list of allowed connections in the tv and retry.

Link to comment
Share on other sites

smokey7722

I went through and didn't see any options for clearing allowed connections.  To confirm I am not looking in the wrong location, would someone be able to give me a quick direction on where to confirm this?

 

A DLNA server on my network usually just showed up as a new option in the Source menu of the TV listed under AllShare devices.  I've never had to go through any security changes or settings on the television.

 

The concern is that my receiver doesn't see the DLNA server in MB either so I am really thinking its not the device but something in my installation.

 

The only setting for DLNA is the option for "Enable DLNA Play To".  Does this setting actually turn the DLNA server on and off?  If so, it doesn't seem to be doing much on my installation.  For the hell of it I did a netstat before and a netstat after enabling DLNA via this setting and the only difference is one additional UDP port of 57311 is listening.  Thats the only difference.  Is there a list of ports for the DLNA server that I could compare this to?  

 

 

WIth it disabled:

PS C:\Users\adamz> netstat -ano  | findstr 2340
  TCP    0.0.0.0:843            0.0.0.0:0              LISTENING       2340
  TCP    0.0.0.0:8945           0.0.0.0:0              LISTENING       2340
  TCP    10.0.0.8:8945          10.0.0.114:55837       ESTABLISHED     2340
  TCP    10.0.0.8:8945          10.0.0.118:56359       CLOSE_WAIT      2340
  TCP    10.0.0.8:8945          10.0.0.118:56631       ESTABLISHED     2340
  TCP    10.0.0.8:51661         10.0.0.114:2869        ESTABLISHED     2340
  TCP    10.0.0.8:51704         10.0.0.124:8080        ESTABLISHED     2340
  UDP    0.0.0.0:7359           *:*                                    2340
  UDP    10.0.0.8:50050         *:*                                    2340
  UDP    10.0.0.8:57309         *:*                                    2340
  UDP    127.0.0.1:50051        *:*                                    2340
  UDP    127.0.0.1:57310        *:*                                    2340

With the setting enabled:

PS C:\Users\adamz> netstat -ano  | findstr 2340
  TCP    0.0.0.0:843            0.0.0.0:0              LISTENING       2340
  TCP    0.0.0.0:8945           0.0.0.0:0              LISTENING       2340
  TCP    10.0.0.8:8945          10.0.0.114:55837       ESTABLISHED     2340
  TCP    10.0.0.8:8945          10.0.0.118:56359       CLOSE_WAIT      2340
  TCP    10.0.0.8:8945          10.0.0.118:56631       ESTABLISHED     2340
  TCP    10.0.0.8:51661         10.0.0.114:2869        ESTABLISHED     2340
  TCP    10.0.0.8:51704         10.0.0.124:8080        ESTABLISHED     2340
  UDP    0.0.0.0:7359           *:*                                    2340
  UDP    10.0.0.8:50050         *:*                                    2340
  UDP    10.0.0.8:57309         *:*                                    2340
  UDP    10.0.0.8:57311         *:*                                    2340
  UDP    127.0.0.1:50051        *:*                                    2340
  UDP    127.0.0.1:57310        *:*                                    2340
  UDP    127.0.0.1:57312        *:*                                    2340
Edited by smokey7722
Link to comment
Share on other sites

AgileHumor

Menu

Network

AllShare Settings

 

You should see the IP of you MB3 server.

 

You go from MB3 to Samsung TV...using the web browser or mobile app.

 

You don't browse anything from the Samsung TV.

Edited by AgileHumor
  • Like 1
Link to comment
Share on other sites

smokey7722

Menu

Network

AllShare Settings

 

You should see the IP of you MB3 server.

 

You go from MB3 to Samsung TV...using the web browser or mobile app.

 

You don't browse anything from the Samsung TV.

 

AllShare Settings just says "No equipment stored".  I had looked their earlier but saw nothing.

 

AHHH, your last comment of "You go from MB3 to Samsung TV...using the web browser or mobile app." got it.  I was expecting this to work like all other DLNA servers I have used, which advertise and allow the client to browse the media, not have to send the command to the device for playback.  I was just able to push a music album to the television and its working fine.

Edited by smokey7722
Link to comment
Share on other sites

smokey7722

So the one issue I just noticed with this is that if I send an album to the TV, it will send each track one at a time.  I can't skip or choose a specific track on the TV when its playing.  At the same time, if I press stop on the TV (playing track 2 for example), expecting to leave this function and go back to the regular TV functions/use it will stop playing track 2, but it will then start track 3, and then 4 when I hit stop on 3.  This continues until the entire album has been sent.  Is there a way to have a playlist sent instead of just a single piece of media?

 

EDIT: With further testing it looks like if I power off the TV (I got really frustrated) to stop its playback and then power it back on, the TV goes back to its purpose of displaying whatever its displaying but MB no longer picks up the TV as a destination.  The last entry I see in the server log for PlayTo is:

 

2014-03-23 09:58:04.8813 Debug - PlayTo: Controller disposed
 
It seems there is a timeout I would guess before it picks up the new device again on its power up?  The disposal above was at 9:58:04 while the creation below was at 10:01:57.  The TV was powered off at the disposal time however it was powered on roughly 10 seconds later and network connectivity confirmed on power up so it should have been much faster.
 
2014-03-23 10:01:57.5557 Info - PlayTo: DLNA Session created for [TV]Office - UN32EH5300
 
Edited by smokey7722
Link to comment
Share on other sites

AgileHumor

There should be a remote at the album level vs playing an individual track.

 

This is how you play a Tv season.

 

Never tried music I'm afraid.

Link to comment
Share on other sites

smokey7722

There should be a remote at the album level vs playing an individual track.

 

This is how you play a Tv season.

 

Never tried music I'm afraid.

Right thats what I did, however its not sending an album, it seems like it makes an internal playlist within MB and sends one track at a time.  Not an album playlist to the TV for it to play, but a single track at a time.

Link to comment
Share on other sites

Beardyname

For future reference, the DLNA implementation that currently exists in MB3 is a play-to functionality rather than a server functionality. aka you can't browse your library from the TV but you should be able to play-to from any device. (not sure about MBT or MBC but you get my point :) )

Link to comment
Share on other sites

smokey7722

For future reference, the DLNA implementation that currently exists in MB3 is a play-to functionality rather than a server functionality. aka you can't browse your library from the TV but you should be able to play-to from any device. (not sure about MBT or MBC but you get my point :) )

 

Thanks for the confirmation.  I'm ok with that, the biggest issue right now is sending playlists vs queuing up single items to send one after one.

Link to comment
Share on other sites

Beardyname

Yeah that sounds like something not yet implemented ^^ However I don't dare to speculate if playlist are a thing with DLNA or no, since i avoid it as far as i can :P

 

I'm sure we are gonna get clarification in the upcoming future :)

Link to comment
Share on other sites

smokey7722

Yeah that sounds like something not yet implemented ^^ However I don't dare to speculate if playlist are a thing with DLNA or no, since i avoid it as far as i can :P

 

I'm sure we are gonna get clarification in the upcoming future :)

 

Yea, I generally avoid it for most things but home audio is actually a pretty good use of DLNA.  Its the ONLY thing I generally use it for.  The issue really comes down to if I press STOP on the TV, I want it to stop - not stop playing that track and be sent the next to play.

Link to comment
Share on other sites

Beardyname

Yeah that can't be fun... but i think it's safe to say that this will be improved upon seeing as the music bit overall will get an overhaul sooner or later :)

Link to comment
Share on other sites

pmac

Another way I've found to stop playback once you've queued a bunch of songs (since hitting stop on the TV just plays the next song in the queue), is to send a new song on its own from your mobile device and then stop it. It seems to cancel the existing queued tracks.

 

A bit of a pain, but it works for now. This feature is still new to MB3, and will only improve with time.

Link to comment
Share on other sites

swhitmore

Yea, I generally avoid it for most things but home audio is actually a pretty good use of DLNA.  Its the ONLY thing I generally use it for.  The issue really comes down to if I press STOP on the TV, I want it to stop - not stop playing that track and be sent the next to play.

 

If you hit stop from the MBC remote client (e.g. your phone), does it still try and play the next track?

Link to comment
Share on other sites

smokey7722

If you hit stop from the MBC remote client (e.g. your phone), does it still try and play the next track?

 

I haven't tried yet.  I left earlier and am now traveling for the week so I won't be able to test until I get back Saturday evening though.

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
×
×
  • Create New...