Page 1 of 1

UMS network issue Android[XT1068]<->UMS

Posted: Mon Nov 30, 2015 5:45 pm
by seemax1991
Hello,

I installed UMS to test the Samsung TV and Home Theater devices (both DLNA-Certified(!)) that will arrive today.
I tried Serviio as well (worked) but had no transcoding profile for Android.

Issue:
ums_dbg.zip
(24.93 KiB) Downloaded 373 times
- 5001 UDP TCP in firewall open
- usm.exe allowed
- wrapper.exe allowed
- javaw.exe allowed by default

UMS shows incoming connection and recognizes my XT1068 as BubbleUPnP.
On my Android though, BubbleUPnP, Media House and other cleints are unable to detect and request files lists, UMS is not even shown.
HTTP server just works fine...

I will try (Serviio and UMS) with the Samsung TV as well and edit this post here later on.

- Seemax

Re: UMS network issue Android[XT1068]<->UMS

Posted: Wed Dec 02, 2015 5:54 am
by seemax1991
So i tested it with my Samsung TV and other devices even while deactivated firewall (what technically should not be needed with such software).
Any idea on what might is going wrong here?

Re: UMS network issue Android[XT1068]<->UMS

Posted: Wed Dec 02, 2015 7:01 am
by seemax1991
DLNA client of Kodi works fine o.O I do not get it...

Re: UMS network issue Android[XT1068]<->UMS

Posted: Thu Dec 03, 2015 1:41 am
by Nadahar
I've used BubbleuPnP against UMS many times (I usually use it to remote control other renderers), and that works "out of the box"/without any need for configuration. If you can't see UMS in BubbleuPnP I'd say you have problems on the network level. Either they are not on the same ip subnet (DLNA requirement) or a firewall or anti virus software is blocking something.

When it comes to disabling firewalls, the easy answer is that DLNA really isn't made for working with firewalls. It relies on multicast/broadcast of UDP packets, but also uses HTTP (TCP). Multiple incoming ports needs to be opened in addition to outgoing access.

I find that usually people run firewalls without any need. The OS makers want to play it safe and enable firewalls by default because they expect their users to not know what they are doing, but the fact is that you only need to run a local firewall if:
  • You connect directly to the internet without a router with NAT (your PC's IP will be a public IP).
  • You connect to unsecure/public/untrusted Wifi networks
  • You wish to block access to your computer from other devices on your local network
  • If you have IPv6 internet access and haven't properly configured the firewall in your router (IPv6 has no NAT which makes it more complicated)
For most people the answer to all of the above is no, and a local firewall is not needed.