Emby DLNA not working on fresh Windows Server 2012 R2 or Windows Server 2016

[eTomm 4]

Hello, I setup a quick emby installation, last version beta, on both a Windows Server 2012 R2 and 2016. 

 

DLNA server is not seen on the network.

 

I should say that the very same installation on a Windows 10 box had no problem (same settings copied on the fly).

 

The two Server runs as VM in XCP-ng. The Windows 10 is my desktop.

 

I would like to know if I must enable some particular roles that are not available on Windows 10. For Now I installed Desktop Experience an nothing else on both Servers.

[Luke 37051]

Hi, have you checked windows firewall to see if any blocking rules have been created preventing Emby upnp communications?

[eTomm 4]

It was disabled the firewall, just in case.

Edited April 18, 2019 by eTomm

[eTomm 4]

Seems that after further investigations the problem was related to something I unthinking enabled on the two new installation of XCP-ng..... IGMP snooping. 

 

Sometimes Recommended is not really Recommended.

 

I was thinking it was the latest version of Emby that I installed after a 2 weeks downtime. But it was working on all the machines that were not inside a virtualization server, so I took a look at that case too and found the solution.

[Luke 37051]

Interesting, thanks for the info !

[eTomm 4]

And that is effecting even routers and switches. They have that option too... if you will enable it and don't manage it correctly bye bye dlna/upnp

[martincom 25]

I encountered a similar situation when I re-purposed some D-Link DIR-655 wifi routers for use as access points.  I was utilizing Serviio as media server at the time.  None of the client/renders downstream of the DIR-655, whether ethernet or wireless, would detect Serviio.  However, Serviio would detect the client/renders and list them.  Per D-Link's configuration instructions for use as an access point, I had disabled uPNP.   That was the issue.  As the Serviio "alive" broadcasts were similar to uPNP broadcasts, the DIR-655 would block them if uPNP was not enabled.  Enabling uPNP resolved the issue with no side effects.