Suddenly cannot find renderers

[zoan2013]

Installed UMS 6.0 for Java 8 on my new computer (Windows 10-64bit) and it worked fine for a couple of days. Then starting today, it suddenly finds no renderers, and is not detectable on any comp or my PS4.

I've tried turning off the firewall (avast), I've uninstalled and reinstalled Java and UMS several times, I've made sure my sharing settings are as they should be... nothing. I even installed the last stable version of UMS and it did not help.

Gonna have to stop using it unless someone (or I) can find out why it's not working.

[Nadahar]

Only turning off Avast might not be enough, have you turned off Windows firewall as well?

I can see that UMS sees a lot of devices on your network, but it seems that they never contact UMS. I strongly suspect that some of the ports are blocked. The devices found in the log are:

Code: Select all

10.0.0.232
10.0.0.1
10.0.0.69
10.0.0.142
10.0.0.27

[zoan2013]

I have Windows Firewall turned off, did that right after the install. I tried a few other things like uninstalling and reinstalling the network driver. Did not help.

[zoan2013]

Finally found the problem. It was in Avast's Internet Security firewall. Under system rules, the setting for "Allow Windows File and Printer Sharing" was set to "not configured". Once I set it to Enabled, the problem was solved.

[Nadahar]

That should not affect UMS, but I'm glad it's working now. I was pretty confident that this was a firewall issue.

[lunitunez]

I was having a similar problem where after using UMS for some time all of a sudden my smart tv and ps3 couldn't see the media server anymore. After doing some tests with Wireshark and the default listening port 5001 I discovered that my computer sees the request come through to the computer which UMS is installed on. When I opened a command prompt (cmd) as an administrator and ran "netstat -b" Avast! Free Antivirus has a service that starts when Windows first boots up called AvastSvc.exe, at the time that I ran that command it was listening on port 5001. My guess is that this damn anti-virus service is hijacking the port and therefore UMS isn't able to listen on it since it is already in use.

I tried digging around the Avast interface and also a search on google and it isn't immediately apparent how to change the port that service listens on or if there is some kind of configuration change I can make, other than completely un-installing Avast and rebooting to see if that resolves the issue. Also I'm not sure if I can just tell my PS3 and Smart TV a different port to communicate on, I just discovered it so I'll dig into it further and see if that is indeed the issue and what my solution is, I might just have to find another AV solution that doesn't install anything listening on 5001, thanks.

[Nadahar]

You can configure UMS to use a different port if that is really the problem.

[lunitunez]

I ended up using a Java un-install tool to uninstall any Javas I had installed (I think the only one on my system was like Java 8 Update 80 64-bit) and then I installed the latest java Java 8 Update 101 8.0.1010.13. After that I rebooted and now when I do a port scan with a tool called PingTools on my Android phone, port 5001 finally indicates it is open, and my Smart TV which is on is being detected under the media renderers. So looks like in my situation Avast was a red herring and it was just a matter of un-installing the Java I had and installing the lastest Java.

[Nadahar]

I doubt the problem was with the installed Java versions either, is if they weren't compatible UMS wouldn't have started. When you run the Java installer on Windows, it will (re)create rules for the Windows firewall that lets (all) Java programs through. I'd say your real issue were probably with Windows firewall.

[lunitunez]

During my troubleshooting I was checking my Windows Firewall and did see the rule to allow traffic for that UMS executable and followed it back to the folder specified in that rule.

As you indicated though when I installed the latest Java and ran the UMS it did prompt me to allow or block the traffic again. I did allow it on the private network since I am at home, so that must have fixed whatever broke that firewall rule. Happy to get that working again, thanks for UMS it is great software.