Universal Media Server | Forum

Good evening,

Apologies if I seem a little daft - but I first installed UMS a few weeks ago and it ran perfectly fine on my Xbox One X, which I have connected up to my tv in my lounge. Installed, launched and it ran like a dream. However, a couple of days ago I updated to the latest version of UMS, and after that my Xbox One X will no longer detect the media server when I try to find it on my Xbox. My smart TV in the lounge will detect UMS and plays movies no problem, but the fact that my Xbox was working fine previously has encouraged me to try and find out what the problem is, plus I prefer running things through my XBOX as it is connected via an ethernet cable to my router (my pc is also connected to the router via ethernet cable) so it offers greater bandwidth than my tv which is Wi-Fi.

I have several devices connected (my son and daughter have their own Xbox Ones, and these are picked up fine), but my own Xbox isn't detected via UMS nor is UMS detected on my Xbox. I can ping my Xbox from my pc, so I know its accessible across the network, so am at a loss.

Haven't attached any logs or anything yet, as I'm unsure what to attach - my Xbox One is sat on 192.168.1.234, and this isn't detected by the UMS logs, but is definitely pingable from my PC. I also know that Microsoft recently pushed out an update in the last couple of days, so its possible that too has affected something.

Thank you in advance for your help, if you do need logs, etc, just let me know and will do my best to send them.

Can you try setting the Network Interface on the General Settings tab, in the "Force networking on interface" dropdown?

Hi SubJunk, thank you for the reply.

I read that in one of the other posts before posting here - I've set it to the correct interface which in my case is Internet Ethernet Connection (192.168.1.133).

I have noticed one other thing, which may or may not be an issue, when I go into media streaming in my windows control panel and look at my Xbox One X in there it doesn't have an assigned IP.
All my other renderers do, so one is 192.168.1.158, another is on 192.168.1.116 - but my XBOX one instead of having an IP is displaying this:

"fe80::64b6:6bd1d2fc%5"

Unsure why this is, according to my network and the Xbox One itself it is on IP 192.168.1.234.

Thank you so much.

fe80::64b6:6bd1:34c6... is IPv6, while 192.168.1.234 is IPv4. This explains the issue, as UMS doesn't support IPv6. Hopefully there is a setting in your Xbox One that lets you make it use IPv4.


IPv6 wasn't originally supported by UPnP AV/DLNA. There have later been made some amendments to both standards for IPv6, but I haven't studied the details. Most equipment sticks to the original IPv4 implementation, and so does UMS.

Personally I don't see any upside to IPv6. It was originally designed because IPv4 was "running out of address space" as the Internet grew and more devices connected. The challenge couldn't wait for IPv6 though, so other solutions was found with IPv4 like "address translation" (NAT). Today "everybody" use NAT in their routers, so that the IP's in their home network aren't valid on the Internet. The router "translates" all traffic from your home network to use the router's "public" (Internet valid) IP address. This technique largely solved the address space issue, but there might still be a shortage of IP addressed globally, I'm not sure of that. I do know that early on there was a lot of waste of addresses, many companies reserved huge ranges that they will never need, because only resources that should be reachable from the internet (web servers, mail servers etc) needs "public" addresses, all others (the majority) can use private/NAT addresses. So, there are huge gains to be made by freeing all these reserved addresses that aren't needed.

In the beginning, one assumed that every connected device would need its own public IP, but it turns out that using NAT also has other advantages. First of all, it makes devices harder to attack from the Internet, as they are not directly reachable. Second, it makes it harder for governments or others to "spy" on the traffic, as they can only tell which "house" something comes from, and not which device/computer.

With IPv6, the original goal of one address for one device is finally possible, but my question is: Who wants that? The only difference is that you will be much easier to track, and potentially easier to attack. Why would anyone want that?

Thanks again for the reply.

That would explain why I can't see the Xbox. I don't recall ever setting the Xbox to run on IPv6 - wonder if the MS update a few days ago has done something with my settings.

Regardless thank you for the explanation, at least now I know what changes I need to look into.

Appreciate the help.

Lol I'm back again.

Ok, having checked my Xbox one it is definitely running on IPv6 with the IP address I mentioned before, there is no mention of IPv6.
But for some reason on my Windows 10 PC, under media streming the Xbox has been assigned an IPv6 address.
I tried disabling IPv6 on my network adapter settings and that removed the Xbox completely from my list of devices.

I thought the issue was with the Xbox. Is it possible that for some reason my Windows 10 PC has assigned an Ipv6 address to the Xbox? According to my ISP my main router doesn't even have IPv6 functionality.

Thanks again.

Sorry what I should have said is that my Xbox One is definitely running on IPv4 - IPv6 isn't even displayed on the network settings.

Something doesn't make sense if the Xbox is discovered with an IPv6 address. It must mean that the Xbox is running IPv6, and if you can't find it when disabling IPv6 on the PC, it means that the Xbox is running IPv6 only. Windows usually runs both.

You need to go look at the IP setup of the Xbox. If it's set to automatic, maybe you can assign a manual address that is IPv4?

I agree, its really odd. I've just gone onto my home router and it hasn't even been setup for IPv6. The Xbox def says its running IPv4, and I've set up a static address, but its still showing as IPv6 in Windows.
I may email Microsoft as its really funny all this happened after their latest Xbox update which was on the 16th June (when all this started happening).

I can't think of anything else to try to be honest.

It sounds like an issue with their firmware yes. As long as the "problem" is the same with Windows when you disable IPv6, you can rule out UMS as the problem - since it only supports IPv4.

Don't you just love updates that breaks things? I certainly do... especially when they push them at you.