hgewald 8 Posted August 8, 2018 Posted August 8, 2018 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.
Luke 38860 Posted August 8, 2018 Posted August 8, 2018 Hi there, please attach the information requested in how to report a problem. thanks.
hgewald 8 Posted August 9, 2018 Author Posted August 9, 2018 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.
Luke 38860 Posted August 10, 2018 Posted August 10, 2018 Can you try upgrading back to 3.5.2 and reboot your nas?
hgewald 8 Posted August 10, 2018 Author Posted August 10, 2018 I did - same result as before. Sent you the log file. Downgraded again.
Luke 38860 Posted August 14, 2018 Posted August 14, 2018 Do you have other dlna software running on the NAS?
hgewald 8 Posted August 17, 2018 Author Posted August 17, 2018 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.
Luke 38860 Posted August 17, 2018 Posted August 17, 2018 Yea I don't know the reason for the conflict yet, but for now shutting down other dlna software should resolve it.
hgewald 8 Posted August 17, 2018 Author Posted August 17, 2018 I can test that on Monday. Will get back to you
hgewald 8 Posted August 20, 2018 Author Posted August 20, 2018 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.
joho500 1 Posted September 13, 2018 Posted September 13, 2018 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
Luke 38860 Posted September 13, 2018 Posted September 13, 2018 Upnp is a very generic protocol. It could be anything on your system that is grabbing the port.
h0me5k1n 1 Posted October 30, 2018 Posted October 30, 2018 I had to stop download station and turn off upnp discovery on my qnap to get dlna to work on 3.5.3.0. Qnap dlna was already off (and twonky). This link shows how to check what is using a particular port (in this case I was looking for "1900"). First it was "dsd" (download station daemon) then "qvs0" (qnap upnp discovery)... https://www.tecmint.com/find-out-which-process-listening-on-a-particular-port/
Guest Posted November 7, 2018 Posted November 7, 2018 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
Guest Posted November 7, 2018 Posted November 7, 2018 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.
Haxy 9 Posted November 11, 2018 Posted November 11, 2018 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
gruni 2 Posted December 7, 2018 Posted December 7, 2018 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.
Recommended Posts
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 accountSign in
Already have an account? Sign in here.
Sign In Now