PS4 no longer detects UMS

[redpat2061]

Hello

On 5/17 my PS4 suddenly stopped seeing UMS. I can't pull up anything on my phone either so assuming it's UMS. There were no updates from sony or microsoft or java or netgear or anything else I've checked - something seems to have just decided that it doesn't wanna anymore.

Things I've ruled out so far:

It isn't Java: I uninstalled that completely
It isn't the subnet: I can see both devices and they are practically touching
It isn't firewall - that is totally 100% disabled
It isn't Media Streaming: that is on
It isn't the VPN: that is off, signed out & disabled
It isn't my router: firmware is up to date
It isn't my network card: bought a new one

Any other ideas? I tried turning off any settings that didn't look essential. I disabled all the renderers that aren't PS4 because I don't have any others. I tried forcing the interface, the ip and the port just to see if something different did anything, but it did not.

Thanks!

[Nadahar]

I think you have to reevaluate some of the things you've ruled out:

It isn't Java: I uninstalled that completely

OK, I don't know how that's relevant.

It isn't the subnet: I can see both devices and they are practically touching

Networking isn't affected by physical location. It wouldn't matter if you melted them into one lump. Unless of course, what you're referring to is WiFi signal strength - for that it matters. But, if devices aren't on the same IP subnet, they won't see each other (Subnet masks must be identical and IP addresses from the same "range"/subnet).

It isn't firewall - that is totally 100% disabled

OK

It isn't Media Streaming: that is on

What is that, and how is that related to UMS?

It isn't the VPN: that is off, signed out & disabled

OK

It isn't my router: firmware is up to date

This absolutely means nothing as to whether it's your router. Most bugs arrive with new software/firmware, and router issues can also be caused by faulty hardware. That said, I don't find the router itself to be the most likely cause of this.

It isn't my network card: bought a new one

How is that relevant? Do you mean to say that you bought a new one because of this issue with UMS, and that the problem is identical with both the old and the new network card? Generally speaking I don't think I've ever seen discovery issues being caused by the network card itself, if the network card works for other use (like connecting to the Internet), it probably works just fine for UMS as well.

[redpat2061]

This is everything I've found on this and other boards that might be relevant. I tried to search thoroughly and explore every possibility I could find before wasting anyone's time with my question.

[mik_s]

check what the network interface UMS is using, from your logs it is:

Code: Select all

TRACE 2020-06-07 16:58:01.886 [main] net.pms.network.UPNPHelper Setting SSDP network interface: name:wlan0 (Intel(R) Wi-Fi 6 AX200 160MHz)
TRACE 2020-06-07 16:58:02.011 [main] net.pms.network.UPNPHelper Sending message from multicast socket on network interface: name:wlan0 (Intel(R) Wi-Fi 6 AX200 160MHz)
TRACE 2020-06-07 16:58:02.011 [main] net.pms.network.UPNPHelper Multicast socket is on interface address: /10.0.0.32 and local port 1900

Your IP should be something like 192.168.x.x, try changing the "force networking on interface" in general settings to select the correct interface.

More info here

[Nadahar]

@mik_s From what I could see in the log, this is the only NIC with a valid IPv4 address - which makes me think it's the correct one. That's why I didn't suggest doing anything with it. 10.x.x.x are all valid "private" IP addresses, but there is often some confusion as to what subnet mask to use for that network, which is why I mentioned the subnet masks in particular.

@redpat2061 Your log showed no sign of communication with any other UPnP device, which leaves only two possibilities: There are none, or there's something preventing the network communication from flowing. That can be firewalls, VPN clients, antivirus software, router configuration or erroneous network configuration. To exclude a simple network configuration issue, getting both the IP addresses and subnet masks of all "involved parties" (UMS computer + renderer(s)) would be a good start.

[redpat2061]

There are no other devices, but since that's not testable let's try to rule out network communication.

There is no firewall, I've turned everything off and windows keeps bitching at me to turn it back on, so i'm fairly sure that it's still off. I removed Nord VPN for now. I have no antivirus installed.

My PC is on 10.0.0.32 with subnet mask 255.255.255.0 and my PS4 is on 10.0.0.17 with subnet mask 255.255.255.0

What else can we check?

Thanks for your help!

[Nadahar]

The subnet masks...

With every IP address there is a subnet mask, for example 10.0.0.32 normally have either subnet mask 255.255.255.0 or 255.0.0.0. To make it extra complicated, there are two ways to write subnet masks, either the dot-decimal notation or with a slash and the number of bits. There isn't much consistency as to where what form is used, but 255.255.255.0 is the same as /24, and 255.0.0.0 is the same as /8. For more information, see one of the many online IP calculators for example this one: http://www.subnet-calculator.com/subnet.php?net_class=A

What is essential is that both devices use the same subnet mask, regardless of in which notation it is written. Home networks usually use either 192.168.x.x or 10.x.x.x, and 192.168.x.x is "simpler" in that subnet mask 255.255.255.0 (/24) is pretty much always what's used. For the 10.x.x.x net, I've seen defaults for either of the two masks mentioned.

If your PC use 255.255.255.0 and the PS4 uses 255.0.0.0 (or vice versa), they won't be able to "see" to each other. I don't think this is very likely since this used to work, but it would be nice to be certain that they both use the same subnet mask.

[mik_s]

If the IP doesn't start 192.168.x.x then that is past my knowledge in networking

The most common cause I have seen of suddenly not being abe to connect to a device is a change in the networking interface, sometimes changing it to the VPN instead of the local connection probably due to some update.

[Nadahar]

@redpat2061 Edits aren't very easy for others to see, and it doesn't trigger a "new post notification". I only noticed that you added the subnet masks now, and it was pure coincidence.

Since your subnet masks match, the IP setup looks correct. That only leaves router and "firewall" issues. To make sure unicast is working, please ping 10.0.0.17 from your PC. You should get a reply.

If the ping test works fine, I can't see any other option than that something is blocking the communication on your PC. I would double check that the firewall is off, so that it's just some other part of Windows Defender that is disabled and which Windows is bitching about.

[redpat2061]

So I think we're making progress - when I ping I don't get a reply, I get General Failure - so you say it must be a router or network issue.

I went to Security providers and it says Windows Firewall is turned off. Under device security it says standard hardware security not supported. I go into firewall and I see

Domain network
Firewall is off
Private network
Firewall is off
Public network
Firewall is off

There's an option at bottom to allow an app through firewall. UMS has private and public both checked.

On the router side in the Nighthawk app under Security it says not activated. Parental controls are also off. I don't really see any options in here that let me do anything except disable internet for each device, and that isn't a problem. Nothing changed on the router before I started trying to fix this problem and updated firmware.

I feel like it has to be something that microsoft pushed out. Any ideas what else I can check in windows?