

Once you’ve added your folders, press Restart Server at the top to finish off the setup.

That folder will be added to the shared folders list.ħ.

Find the folder containing your media files and press open.ĥ. Press the Folder icon to choose a folder.Ĥ. Under the 'Shared Folders' section, highlight all drives, and press the red x to remove them.ģ. Click Navigation/Share Settings at the top of the UMS main panel.Ģ. Once it's installed, you should be looking at the UMS main screen:ġ. When it's downloaded, install it on your computer. Go to their website, and click the Windows logo to start downloading. Next, you need to download and install the Windows version of Universal Media Server. To stay safe, you should never download Java from any other websites. You might already have Java on your computer, but if not, go to and download it from there. To get started, you'll need to make sure you have an up-to-date version of Java installed on your PC. The simplest way of doing this is through a program called Universal Media Server (UMS), which shares your files across your home network, and lets the PS4 see them, and play them on your TV. So your PS4 can display films, TV shows and other bits from your PC, you'll have to set up the PC so that it acts as a 'media server'. You have to have "Hide advanced options" unchecked for this setting to be visible.Downloading and Setting up Universal Media Server Alternatively, you'd have to select which NIC UMS should use on the "General Configuration" tab under "Network settings". If I were you I'd just remove adapter #2 from the VM, since it's lack of connectivity indicates that it's not being used for anything.

My guess is that "Hyper-V Virtual Ethernet Adapter #2" isn't connected to anything in the Hyper-V configuration. So, you're right that in normally means connection problems. It's not strange that the 169.x.x.x answers, the IP adresses are real enough but IP's in this series is selected by the OS when the NIC is set to receive IP adress via DHCP but can't find any DHCP server. For some reason, UMS lists "Hyper-V Virtual Ethernet Adapter #2" as eth 0 (the first network adapter), and it might be that UMS binds to this adapter. The one with the "invalid" IP address is called "Hyper-V Virtual Ethernet Adapter #2", while you have a real IP address at "Hyper-V Virtual Ethernet Adapter". I see from your log that your running this on a VM, and you have defined two network adapters for this VM.
