Jump to content

DLNA does not work with Version 3.5.2.0


Recommended Posts

Posted

Hello,

since upgrading to emby server Version 3.5.2.0 my DLNA does not work anymore.

I run a QNAP TS-451+.

Also the QNAP DLNA server is affected.

 

When downgrading to emby Version 3.5.1.0 everything runs smooth again.

 

Anything I can assist in resovling this issue?

 

Best

H.

Posted

With great pleasure :)

 

So, since updating to emby server Version 3.5.2.0 my DLNA does not work anymore.

 

This means that none of my devices (Sony, Samsung) show the emby as an DLNA source. Also the QNAP DLNA server is not shown anymore.

In other words: via DLNA I cannot access any movies on my NAS anymore. There is simply no server on display at the DLNA device.

 

When I downgrade to emby Version 3.5.1.0  the DLNA access works as before (all servers are visible on all devices).

 

Send you the server log as private message.

 

Thanks

H.

Posted

Can you try upgrading back to 3.5.2 and reboot your nas?

Posted

I did - same result as before.

 

Sent you the log file.

Downgraded again.

Posted

Do you have other dlna software running on the NAS?

Posted

The QNAP TS451+ is running a DLNA server.

I always thought that emby requires this core-functionality to provide its own DLNA service.

 

Until the last emby version, everything worked fine and both DLNA services were running without affecting each other.

Posted

Yea I don't know the reason for the conflict yet, but for now shutting down other dlna software should resolve it.

Posted

I can test that on Monday.

Will get back to you

Posted

OK, I stopped the QNAP DLNA services and now the emby DLNA works again.

Weird that this problem started with the new server version. Before that, it was not an issue

 

Best

H.

Posted

Thanks for the info.

  • 4 weeks later...
Posted

I have the same problem after upgrading to 3.5.2.0. But I can't identify the other program that is using port 1900.

I've stopped another service of which I already disabled the dlna service and restarted Emby but still not working.

 

I've attached the logfile.

 

Hope you can solve this.

 

Cheers,

Joost

embyserver_20180913.txt

Posted

Upnp is a very generic protocol. It could be anything on your system that is grabbing the port.

  • 1 month later...
Posted

Thanks for the info !

Posted

I have the same issue with emby-server 3.5.3. Emby dlna/upnp is not visible with dlna clients (TV, android client). The emby-android app and the webapp works just fine though. Interestingly, I can use the "play on" menu to play content on devices (TV for example). 

 

I  do not have any other dlna server running. I double checked with netstat and only emby seems to be using port 1900. Shows up as: 

ArchZen :: ~ » sudo netstat -nap | grep :1900
udp        0      0 0.0.0.0:1900            0.0.0.0:*                           722/dotnet 

I setup kodi dlna to verify that it wasn't a networking issue - it works correctly. 

 

log file: https://ptpb.pw/6yXc

Posted

What port are the others using?

Posted

Kodi definitely uses port 1900 (UDP) for something. It is not explicitly documented - but upnp would be obvious guess.

 

Enabling/disabling the kodi dlna server only changes the status of a tcp listening port 2044. I can see in the logs that "platninum" (upnp sdk used by the kodi project) is listening on that port. This is what the upnp client on my phone establishes connection.

Posted

I have the same problem, my samaung 2014 smart tv does not see Emby dlna server but i can use Play on option Emby server

  • 4 weeks later...
Posted

many thanks to Newbie!

 

I had to stop download station and turn off upnp discovery on my QNAP 251+ to get dlna to work / Qnap dlna was already off.

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