Universal Media Server | Forum

Hey,
I just let UMS update from 9.8.2 to 9.8.3 and now my PS3 cant see UMS. The log for UMS keeps saying "Network is unreachable: no further information". I have tried forwarding ports in windows firewall, totally turning off windows firewall, and resetting to default. None of them worked. I looked to update my routers firmware but its up to date. I am at a loss and am not sure what else to do. Any help would be greatly appreciated.

Occcasionally it will give this error "[Fatal Error] :1:1: Premature end of file." But it says that once every ten minutes or so compared to the couple times a minute I get the other error.

It seems like the problem with your network setting. The UMS has an IP address 10.0.0.2 but there is a device with the IP address 169.254.9.6 sending M-SEARCH and the UMS is responding with Network is unreachable which is correct because all devices should have IP addresses in the same subnet means interval 10.0.0.1-10.0.0.255. There is also other problem. You named files like

D:\Videos\GHOST in the SHELL (1995-2015) - 3 Movies, COMPLETE Stand Alone Complex SERIES, Arise OVAs - 1080p DUAL Audio x264\b. STAND Alone COMPLEX (2002-06)\1a. 1st Gig (2002-03)\Ghost in the Shell (S.A.C) - S01 E17 - SA - Angel's Share (1080p - DUAL Audio).mkv

which is unreadable for FFmpeg and making thumbnails failed with error

[ffmpeg64.exe-9-2] net.pms.io.OutputTextConsumer D:\Videos\GHOST in the SHELL (1995-2015) - 3 Movies, COMPLETE Stand Alone Complex SERIES, Arise OVAs - 1080p DUAL Audio x264\b. STAND Alone COMPLEX (2002-06)\1a. 1st Gig (2002-03)\Ghost in the Shell (S.A.C) - S01 E17 - SA - Angel's Share (1080p - DUAL Audio).mkv: No such file or directory

Maybe the FFmpeg limits the filename length to 255 as it was before WIN 10. Your filename is about 258 characters including the file path.

It looks like you have a VPN which sometimes can confuse UMS to what network to use, usually after an update that changes the order of the network interfaces.

Try changing "Force networking on interface" in the general settings tab and manually select your physical adapter.

valib wrote: ↑Sun Jan 03, 2021 8:44 am It seems like the problem with your network setting. The UMS has an IP address 10.0.0.2 but there is a device with the IP address 169.254.9.6 sending M-SEARCH and the UMS is responding with Network is unreachable which is correct because all devices should have IP addresses in the same subnet means interval 10.0.0.1-10.0.0.255. There is also other problem. You named files like

D:\Videos\GHOST in the SHELL (1995-2015) - 3 Movies, COMPLETE Stand Alone Complex SERIES, Arise OVAs - 1080p DUAL Audio x264\b. STAND Alone COMPLEX (2002-06)\1a. 1st Gig (2002-03)\Ghost in the Shell (S.A.C) - S01 E17 - SA - Angel's Share (1080p - DUAL Audio).mkv

which is unreadable for FFmpeg and making thumbnails failed with error

[ffmpeg64.exe-9-2] net.pms.io.OutputTextConsumer D:\Videos\GHOST in the SHELL (1995-2015) - 3 Movies, COMPLETE Stand Alone Complex SERIES, Arise OVAs - 1080p DUAL Audio x264\b. STAND Alone COMPLEX (2002-06)\1a. 1st Gig (2002-03)\Ghost in the Shell (S.A.C) - S01 E17 - SA - Angel's Share (1080p - DUAL Audio).mkv: No such file or directory

Maybe the FFmpeg limits the filename length to 255 as it was before WIN 10. Your filename is about 258 characters including the file path.

Sorry, I dont understand the first part with all the networking stuff. I shortened the file name so it should be under 255 character limit as well.

mik_s wrote: ↑Sun Jan 03, 2021 10:13 am It looks like you have a VPN which sometimes can confuse UMS to what network to use, usually after an update that changes the order of the network interfaces.

Try changing "Force networking on interface" in the general settings tab and manually select your physical adapter.

Well this seems to have fixed the unreachable error. TY for that. The UMS and PS3 still don't see each other.

you selected your VPN interface Select your physical interface, probably "Killer E2200 Gigabit Ethernet Controller"


As for what Valib says the total length of the path is too long for some files. best to rename the first directory like

Ah, ty Im stupid. Its the "Killer E2200 Gigabit Ethernet Conroller #2 (10.0.0.2)".

After you mentioned the VPN I tried turning it off and UMS finds everything on my network in about two seconds. With the VPN on UMS finds about half of the stuff in about a minute. So now I know its the VPN, I just wish I knew why it worked before the update and now it doesnt?

Edit: Anyway thanks for all the help guys. I now know how to make it work again which is all I need.

I think it was using the #2 controller the first time, maybe it should be the first one? Don't know anything about your hardware but maybe you have 2 Ethernet ports?

If there are still conflicts with your VPN just try other interfaces till UMS can see your devices.