Jump to content

Samsung Tv not seeing the dlna server


mihaiaka
 Share

Recommended Posts

Hello,
I saw multiple topics about similar issues, but no solution.
So, recapping, I have a Samsung TV UE46ES6100 which does not discover the DLNA server. It does see all the other ones like plex/serviio/bubbleupnp/etc. But with each other, i have other/different issues. (plex doesn't transcode, guess the profiles are not correct, serviio fails to work if the burn-in subtitle is enabled)
VLC or other dlna clients apps(from my android phone or from the windows store) do see it.

Any idea? I attached the debug log, which shows that the tv is found on the network (the tv has 192.168.1.104)
I tried both the ubuntu and windows versions, same outcome.

Any planned updates for the dlna plugin? or a list of older versions that we could try out?

 

emby.txt

Edited by mihaiaka
Link to comment
Share on other sites

Quote

Any planned updates for the dlna plugin?

Hi, yes, it is always being updated (as it was just last night)...but this is a 2012 device so I'm sure it's possible there are issues with much older devices such as this. We'll have to get our hands on an older model in order to test this ourselves.

Link to comment
Share on other sites

Hello It is quite an old model, but as I do not feel ready to upgrade to 4k just yet, it gets the job done (full hd, 3d,  200 Hz rate, etc). I do not make use much of it's OS/smart capabilities, but my end goal was to access the dlna server from the remote via the input button, similar to the attached picture. That would be "comfortable" to play content.
I am using the latest 4.4.3.0 which has dlna plugin version 1.0.39.0, so I assume it has the last night's update you mentioned. Guess that didn't help much.
Any other advice I might try? Port 1900 is not conflicting with anything, that I checked already. 

input.jpg

Link to comment
Share on other sites

MrBeatrixKiddo

Hi...

I had a similar issue with my smartTV DLNA client.

Try this: 

check your emby-server DLNA settings:

enable 'Blast Alive Messages'   ... AND

adjust the 'Alive Message Interval' setting.  Try using  shorter interval.

 

Link to comment
Share on other sites

43 minutes ago, mihaiaka said:

Hello It is quite an old model, but as I do not feel ready to upgrade to 4k just yet, it gets the job done (full hd, 3d,  200 Hz rate, etc). I do not make use much of it's OS/smart capabilities, but my end goal was to access the dlna server from the remote via the input button, similar to the attached picture. That would be "comfortable" to play content.
I am using the latest 4.4.3.0 which has dlna plugin version 1.0.39.0, so I assume it has the last night's update you mentioned. Guess that didn't help much.
Any other advice I might try? Port 1900 is not conflicting with anything, that I checked already. 

input.jpg

Hi,

My basement TV is an older Samsung but just a bit bigger but from the same time era.  I can DLNA to mine which is connected via Ethernet so I'd ask if it's using Ethernet or Wifi?

If Wifi see if you can try it via Ethernet which may change things for you.

But the main reason I posted was to ask if you have any device hooked to the TV?  Connecting a $60 MiBox-S to that TV will make it seem like a new TV from a "smart TV" perspective.  You could then easily cast to the MiBox-S or use the ATV Emby client directly with a remote for additional functionality.

That combo for the price would be really hard to top.

Link to comment
Share on other sites

@MrBeatrixKiddo Thank you for the advice. Already tried to lower the values for Client discovery interval and Blast alive messages. This did not help in any way.

@Luke Maybe you do not need an old tv to troubleshoot this. During my trial-and-error test, I've been also using a program from the Microsoft Store, called DLNA Browser. Please see the attachment, as emby server is running but not being shown. It did not work with Emby/Jellyfin, but worked with plex/serviio/etc. So it sounds like the same to me.

Could you please consider reproducing the issue from your end?

2nd picture is to show that both the DLNA browser app and the TV does see other dlna servers.

 

Very nice and active community here. Thank you.

Capture.JPG

PXL_20200919_225959291.jpg

Link to comment
Share on other sites

@cayars thank you for the idea. It's currently connected via UTP cable. Should I consider for testing purposes to try WIFI? Or it was only the other way around? But in the end, regardless of the connection type, it will be in the same subnet with the emby server, the 192.168.1.x network. UDP 1900 doesn't care about wifi/copper connection.
My last resort/alternative will be to hook an RPI3 that I have laying around (no extra costs) and do a LibreELEC/Kodi/OS+VLC or whatever other player options I might have.
But that will imply the use of at least another input device (remote, mini keyboard, mouse, etc) for the PI. My end goal was to have just the TV's remote.

Link to comment
Share on other sites

Happy2Play

Have you tried with Emby being the only active DLNA server?

OT: Why is Emby programdata being monitored by Real Time Monitoring?  Only \programdata\data\playlists, \programdata\data\collections and \programdata\data\camerauploads should be monitored from that location that i am aware of.

2020-09-19 22:55:33.963 Info LibraryMonitor: programdata (D:\Download\programdata) will be refreshed.
2020-09-19 22:55:33.963 Info LibraryMonitor: devices (D:\Download\programdata\data\devices) will be refreshed.
2020-09-19 22:55:33.963 Info LibraryMonitor: data (D:\Download\programdata\data) will be refreshed.

 

Link to comment
Share on other sites

@Happy2Play yes, I've tested with only emby running, then with multiple ones running, checking the usage of port 1900, etc. I spent some time doing different scenarios. I tried Ubuntu, I tried Windows installer, and current using the portable version, that's why is running from downloads folder. No clue about the program data monitor part.

Link to comment
Share on other sites

@cayars Thank you for double-checking. This makes my problem-solving even harder.

If I do not ask too much, can someone else also try? Best two out of three, so we could conclude if DLNA Browser is working or not.

 I used "CurrPorts v2.62" to kill every process that used 1900, leaving only emby, followed by a emby restart, searching again, etc.

Same results: 

VLC from pc and DMS Explorer from android works.

DLNA browser from the same PC and Samsung TV doesn't work.

Link to comment
Share on other sites

MrBeatrixKiddo

HI! sorry to hear you still having troubles ....

have you tried updating your TV's firmware?

here is link to samsung support firmware update for your TV....

https://www.samsung.com/us/support/owners/product/2012-led-smart-tv-es6100-series?redir=UE46ES6100

I  was browsing my samsung tv's settings, (i have UN32J5500 model, almost as old as yours!), i noticed there is a security section.  apps network services

can be blocked here.

Menu->System->Smart Security. 

maybe it's blocking you?

 

  • Thanks 1
Link to comment
Share on other sites

MrBeatrixKiddo

Question: what's the deal with using port 1900?

vlc and my samsung tv and my sharp tv, when using DLNA seem to be using port 8096 (the emby server default port) see log excerpts below.

also,  i just noticed on prev. post, on your samsung tv, looked like you were using the tv's 'Source' menu to find emby DNLA server?

OK, try this:  open  'SmartHub', then look for an item called  'My Content'. try that.  that's how i access DLNA on my samsung tv . 

also, in 'Smart Hub' if you select the 'Apps' option you can download and add the samsung emby client app. 

--------

log excerpts: emby dnla not using port 1900...

VLC running on desktop pc with linux os.

2020-09-20 17:04:08.719 Info HttpServer: HTTP GET http://192.168.1.110:8096/Items/74095/Images/Primary/0/f4beab5b7f4d130ffaf5bfa9b7d2a779/jpg/480/480/0/0. UserAgent: VLC/3.0.11.1 LibVLC/3.0.11.1
2020-09-20 17:04:08.840 Info HttpServer: HTTP Response 206 to 192.168.1.110. Time: 121ms. http://192.168.1.110:8096/Items/74095/Images/Primary/0/f4beab5b7f4d130ffaf5bfa9b7d2a779/jpg/480/480/0/0
2020-09-20 17:04:08.857 Info HttpServer: HTTP GET http://192.168.1.110:8096/Items/80602/Images/Primary/0/97d0dab7588ebcae6ae28278634e0a3e/jpg/480/480/0/0. UserAgent: VLC/3.0.11.1 LibVLC/3.0.11.1
2020-09-20 17:04:08.972 Info HttpServer: HTTP Response 206 to 192.168.1.110. Time: 115ms. http://192.168.1.110:8096/Items/80602/Images/Primary/0/97d0dab7588ebcae6ae28278634e0a3e/jpg/480/480/0/0
2020-09-20 17:04:09.010 Info HttpServer: HTTP GET http://192.168.1.110:8096/Items/88677/Images/Primary/0/bd0c05f0747ab7f410cb0041e35b5b1d/jpg/480/480/0/0. UserAgent: VLC/3.0.11.1 LibVLC/3.0.11.1
samsung tv
020-09-20 17:07:50.174 Info HttpServer: HTTP GET http://192.168.1.110:8096/Items/85853/Images/Primary/0/ca816ec6f29c22bc1fa0dc69c63b1ea9/jpg/160/160/0/0. UserAgent: 
2020-09-20 17:07:50.175 Info HttpServer: HTTP GET http://192.168.1.110:8096/Items/80605/Images/Primary/0/b9af423d5e47b6fbc963078c32e9e9f2/jpg/160/160/0/0. UserAgent: 
2020-09-20 17:07:50.176 Info HttpServer: HTTP GET http://192.168.1.110:8096/Items/86218/Images/Primary/0/9cc75627c6657830ddd5e4029b761cf3/jpg/160/160/0/0. UserAgent: 
2020-09-20 17:07:50.223 Info HttpServer: HTTP GET http://192.168.1.110:8096/Items/80606/Images/Primary/0/aec9506650db5a2c742212949b43d70f/jpg/160/160/0/0. UserAgent: 
2020-09-20 17:07:50.224 Info HttpServer: HTTP GET http://192.168.1.110:8096/Items/80607/Images/Primary/0/7ef44626b33035f279a2baed23e1450d/jpg/160/160/0/0. UserAgent: 
2020-09-20 17:07:50.269 Info HttpServer: HTTP GET http://192.168.1.110:8096/Items/80608/Images/Primary/0/240045159e6198a6332c5d14dc146cf7/jpg/160/160/0/0. UserAgent: 
2020-09-20 17:07:50.311 Info HttpServer: HTTP Response 200 to 192.168.1.100. Time: 88ms. http://192.168.1.110:8096/Items/80606/Images/Primary/0/aec9506650db5a2c742212949b43d70f/jpg/160/160/0/0
2020-09-20 17:07:50.322 Info HttpServer: HTTP Response 200 to 192.168.1.100. Time: 98ms. http://192.168.1.110:8096/Items/80607/Images/Primary/0/7ef44626b33035f279a2baed23e1450d/jpg/160/160/0/0
2020-09-20 17:07:50.323 Info HttpServer: HTTP Response 200 to 192.168.1.100. Time: 150ms. http://192.168.1.110:8096/Items/85853/Images/Primary/0/ca816ec6f29c22bc1fa0dc69c63b1ea9/jpg/160/160/0/0
2020-09-20 17:07:50.333 Info HttpServer: HTTP Response 200 to 192.168.1.100. Time: 158ms. http://192.168.1.110:8096/Items/80605/Images/Primary/0/b9af423d5e47b6fbc963078c32e9e9f2/jpg/160/160/0/0
2020-09-20 17:07:50.345 Info HttpServer: HTTP Response 200 to 192.168.1.100. Time: 170ms. http://192.168.1.110:8096/Items/86218/Images/Primary/0/9cc75627c6657830ddd5e4029b761cf3/jpg/160/160/0/0
2020-09-20 17:07:50.382 Info HttpServer: HTTP Response 200 to 192.168.1.100. Time: 113ms. http://192.168.1.110:8096/Items/80608/Images/Primary/0/240045159e6198a6332c5d14dc146cf7/jpg/160/160/0/0
2020-09-20 17:07:50.555 Info HttpServer: HTTP GET http://192.168.1.110:8096/Items/80604/Images/Primary/0/e5a8cdf151293bdc9fb14652953127d1/jpg/160/160/0/0. UserAgent: 
2020-09-20 17:07:50.594 Info HttpServer: HTTP Response 200 to 192.168.1.100. Time: 39ms. http://192.168.1.110:8096/Items/80604/Images/Primary/0/e5a8cdf151293bdc9fb14652953127d1/jpg/160/160/0/0

sharp tv (roku) media player app

020-09-20 17:02:56.392 Info HttpServer: HTTP GET http://192.168.1.110:8096/Items/85317/Images/Primary/0/d9e59222c5e3669965f4918687028ca7/jpg/480/480/0/0. UserAgent: Roku/DVP-9.30 (389.30E04194A)
2020-09-20 17:02:56.947 Info HttpServer: HTTP Response 200 to 192.168.1.104. Time: 554ms. http://192.168.1.110:8096/Items/85317/Images/Primary/0/d9e59222c5e3669965f4918687028ca7/jpg/480/480/0/0
2020-09-20 17:02:56.947 Info HttpServer: HTTP Response 200 to 192.168.1.104. Time: 572ms. http://192.168.1.110:8096/Items/85324/Images/Primary/0/4f0086cba587544e446ece5f77b24ddc/jpg/480/480/0/0
2020-09-20 17:02:56.952 Info HttpServer: HTTP Response 200 to 192.168.1.104. Time: 586ms. http://192.168.1.110:8096/Items/85315/Images/Primary/0/62ec64395a854ada5381aab2d631b728/jpg/480/480/0/0
2020-09-20 17:02:56.954 Info HttpServer: HTTP Response 200 to 192.168.1.104. Time: 569ms. http://192.168.1.110:8096/Items/85316/Images/Primary/0/178b9ea9188f6774763ac129b0f1ab29/jpg/480/480/0/0
2020-09-20 17:02:56.967 Info HttpServer: HTTP GET http://192.168.1.110:8096/Items/85309/Images/Primary/0/68171b2e47df6339f1bb907a25e520c7/jpg/480/480/0/0. UserAgent: Roku/DVP-9.30 (389.30E04194A)

 

 

Link to comment
Share on other sites

This UDP port is opened and used by Universal Plug N' Play (UPnP) devices to receive broadcasted messages from other UPnP devices.

Think of port 1900 as the "Hey I'm here port" so devices and computer can find them.  This is only broadcast on the local LAN and not remotely.

Link to comment
Share on other sites

MrBeatrixKiddo

 

input.jpg

the emby dnla server cannot be accessed from the tv's source menu. 

on your samsung tv UE46ES6100, to access emby dnla use  'AllShare Play' app. 

configure: AllShare Settings:  Menu->Network->AllShare Settings

Use: SmartHub->AllShare Play select the content type: video, audio or photo.  then on right hand side of screen select 'DNLA'.

then tv will display list of allowed devices. select your emby server.

on my samsung tv, they call it 'My Content' app. sorry for any confusion :)

Link to comment
Share on other sites

MrBeatrixKiddo

HEHE... silly me.... i just realized the DNLA may appear as an item on the tv's source menu......

oooopppssss.....

sorry ...

my apologies

 

Link to comment
Share on other sites

@MrBeatrixKiddo Thank you for the advice. On my model, the app is not called "AllShare Play" or "My Content" but "Samsung Link". Same thing there: BubbleuPnp from Android is discovered (as well the shortcut is shown in the sources menu) but emby is not.

AllShare Settings from the network menu only shows a list with previously connected devices, and giving the options to allow or deny. Nothing else. And I do not have a "smart security" button just "security" which hold the option to enable child lock, block 18+ channels, etc. Nothing related to DLNA.

As per the firmware update, I'm at the latest available v2009, did straight from the TV's menu. The link shared shows a v2004.

For the emby samsung app, I cannot find it, probably not available in The Netherlands

 

@Luke I tried the beta 4.5.0.30 version as well. In this one, DLNA is not discovered at all, where the sable one worked, like VLC and DMS Explorer from android. Swapping back my test environment to the stable version.

Can you give DLNA browser (Microsoft store) a try (best 2 out of 3, as for @cayars worked but for me, it didn't)

Edited by mihaiaka
Link to comment
Share on other sites

5 hours ago, mihaiaka said:

@MrBeatrixKiddo Thank you for the advice. On my model, the app is not called "AllShare Play" or "My Content" but "Samsung Link". Same thing there: BubbleuPnp from Android is discovered (as well the shortcut is shown in the sources menu) but emby is not.

AllShare Settings from the network menu only shows a list with previously connected devices, and giving the options to allow or deny. Nothing else. And I do not have a "smart security" button just "security" which hold the option to enable child lock, block 18+ channels, etc. Nothing related to DLNA.

As per the firmware update, I'm at the latest available v2009, did straight from the TV's menu. The link shared shows a v2004.

For the emby samsung app, I cannot find it, probably not available in The Netherlands

 

@Luke I tried the beta 4.5.0.30 version as well. In this one, DLNA is not discovered at all, where the sable one worked, like VLC and DMS Explorer from android. Swapping back my test environment to the stable version.

Can you give DLNA browser (Microsoft store) a try (best 2 out of 3, as for @cayars worked but for me, it didn't)

But you posted a 4.4.3 log at the beginning of the thread saying the TV doesn't discover the server.

Link to comment
Share on other sites

@Luke that is correct. The initial log and tests were from the stable version. I did said that I tried the beta "as well", for testing purposes. Which proved worse (at least the dlna part, even VLC is not able to find it anymore), so I'm back to the stable version.

Link to comment
Share on other sites

9 minutes ago, mihaiaka said:

VLC is not able to find it anymore), so I'm back to the stable version.

Seems to be working ok from here.

Link to comment
Share on other sites

Been playing around with this a bit.

Emby DLNA doesn't show up the same way as other DLNA services do.  I have several DLNA servers on my network besides Emby and they work on different TVs, utils such as DLNA browser or VLC.  However Emby doesn't show up on my TVs including Samsung.  Emby DLNA doesn't work in DLNA browser but may show up.  When it shows up in DLNA browser it's with a web address which is weird.

I think there is something a bit off in the DLNA server.

Link to comment
Share on other sites

Quote

When it shows up in DLNA browser it's with a web address which is weird.

Not weird at all, dlna is an http (and udp) based protocol.

Link to comment
Share on other sites

On my network Emby does not show up on my TVs as a DLNA device but all other devices do.

Here is also how windows network sees things upon initial load.

dlna1.png.25cce0929468285caa239a00e91ff401.png

I have some other devices on a different subnet so I wouldn't expect to see them here.

No Emby servers show up and I've got 3 running on this subnet.  If I let this set for a while I may get one or two Emby servers showing up but hardly ever see all 3.

The TVs are pretty much in agreement with the above services and everyone of those show up and work on Samsung TV.

As a test on my 3 Emby servers I've changed the Alive message interval (seconds) to 60 to see if this makes any difference and it doesn't appear to.

 

 

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...