My UMS is not showing up on my tvs

[superkyle96]

A few weeks ago my UMS stopped showing up on my tvs. When I start the UMS the available tvs show up on the computer, but the tvs don't see the UMS and the tvs go grey after awhile. I've used the UMS for years and this just started. My computer was running Win 10 when this happened. I was already looking at a newer computer witn Win 11. It's doing the same thing with this one. I've tried all of the different settings for the "Force Networking on interface". I changed the port to 6001. I put my computer's IP address and IP DNS Server address in the "Force IP of the Server". I have a VPN that I use. I've shut it down and tried running the UMS with it off. I've reset my router and network. I've allowed access for the UMS through the firewall. Nothing is working. I don't know why it started doing it. I didn't change any settings. I've tried older and the newest version of the UMS. Can anyone offer some assistance?

[mik_s]

Will need logs to know what is happening (see the section in red above)
But also you have changed a lot of networking options that may be working against each other, try resetting your settings to default and see if that helps.
You can make a backup of your current configuration by copying the folder C:\ProgramData\UMS to somewhere safe, or just rename it so a new one is created.
You could try a clean install by selecting that option in the installer too.

[superkyle96]

Here is my log. I restarted my UMS using the trace. I waited until the TV quit showing on the Status page even though the TV was still on. Any help will be soooo appreciated.

[mik_s]

I'm not sure what is going on here. UMS can see the TV but it looks like it is not getting a response for something and is being unregistered.

Code: Select all

TRACE 2022-07-03 12:09:10.480 [jupnp-registry-maintainer-1] org.jupnp.registry.Registry Device '(RemoteDevice) Identity: (RemoteDeviceIdentity) UDN: uuid:56897635-989d-4741-af6f-4e4378054a50, Descriptor: http://192.168.1.4:7676/rcr/, Root: true' expires in seconds: 15
TRACE 2022-07-03 12:09:10.480 [jupnp-registry-maintainer-1] org.jupnp.registry.Registry Device '(RemoteDevice) Identity: (RemoteDeviceIdentity) UDN: uuid:b98a07c0-ce0a-4d7a-96fe-a910b8a598ef, Descriptor: http://192.168.1.4:7678/nservice/, Root: true' expires in seconds: 15
TRACE 2022-07-03 12:09:10.480 [jupnp-registry-maintainer-1] org.jupnp.registry.Registry Device '(RemoteDevice) Identity: (RemoteDeviceIdentity) UDN: uuid:3652781f-2a94-4d6b-b872-b639acd69878, Descriptor: http://192.168.1.4:9197/dmr, Root: true' expires in seconds: 15
TRACE 2022-07-03 12:09:10.480 [jupnp-registry-maintainer-1] org.jupnp.registry.Registry Device '(RemoteDevice) Identity: (RemoteDeviceIdentity) UDN: uuid:4e059cce-e9c4-427f-93b9-4fbe4a69276c, Descriptor: http://192.168.1.4:9119/screen_sharing, Root: true' expires in seconds: 15
TRACE 2022-07-03 12:09:25.481 [jupnp-registry-maintainer-1] org.jupnp.registry.Registry Device '(RemoteDevice) Identity: (RemoteDeviceIdentity) UDN: uuid:56897635-989d-4741-af6f-4e4378054a50, Descriptor: http://192.168.1.4:7676/rcr/, Root: true' expires in seconds: 0
TRACE 2022-07-03 12:09:25.481 [jupnp-registry-maintainer-1] org.jupnp.registry.Registry Device '(RemoteDevice) Identity: (RemoteDeviceIdentity) UDN: uuid:b98a07c0-ce0a-4d7a-96fe-a910b8a598ef, Descriptor: http://192.168.1.4:7678/nservice/, Root: true' expires in seconds: 0
TRACE 2022-07-03 12:09:25.481 [jupnp-registry-maintainer-1] org.jupnp.registry.Registry Device '(RemoteDevice) Identity: (RemoteDeviceIdentity) UDN: uuid:3652781f-2a94-4d6b-b872-b639acd69878, Descriptor: http://192.168.1.4:9197/dmr, Root: true' expires in seconds: 0
TRACE 2022-07-03 12:09:25.481 [jupnp-registry-maintainer-1] org.jupnp.registry.Registry Device '(RemoteDevice) Identity: (RemoteDeviceIdentity) UDN: uuid:4e059cce-e9c4-427f-93b9-4fbe4a69276c, Descriptor: http://192.168.1.4:9119/screen_sharing, Root: true' expires in seconds: 0
TRACE 2022-07-03 12:09:40.487 [jupnp-registry-maintainer-1] org.jupnp.registry.Registry Device '(RemoteDevice) Identity: (RemoteDeviceIdentity) UDN: uuid:56897635-989d-4741-af6f-4e4378054a50, Descriptor: http://192.168.1.4:7676/rcr/, Root: true' expires in seconds: -15
TRACE 2022-07-03 12:09:40.487 [jupnp-registry-maintainer-1] org.jupnp.registry.Registry Device '(RemoteDevice) Identity: (RemoteDeviceIdentity) UDN: uuid:b98a07c0-ce0a-4d7a-96fe-a910b8a598ef, Descriptor: http://192.168.1.4:7678/nservice/, Root: true' expires in seconds: -15
TRACE 2022-07-03 12:09:40.487 [jupnp-registry-maintainer-1] org.jupnp.registry.Registry Device '(RemoteDevice) Identity: (RemoteDeviceIdentity) UDN: uuid:3652781f-2a94-4d6b-b872-b639acd69878, Descriptor: http://192.168.1.4:9197/dmr, Root: true' expires in seconds: -15
TRACE 2022-07-03 12:09:40.487 [jupnp-registry-maintainer-1] org.jupnp.registry.Registry Device '(RemoteDevice) Identity: (RemoteDeviceIdentity) UDN: uuid:4e059cce-e9c4-427f-93b9-4fbe4a69276c, Descriptor: http://192.168.1.4:9119/screen_sharing, Root: true' expires in seconds: -15
TRACE 2022-07-03 12:09:40.488 [jupnp-registry-maintainer-1] org.jupnp.registry.Registry Removing expired: (RemoteDevice) Identity: (RemoteDeviceIdentity) UDN: uuid:56897635-989d-4741-af6f-4e4378054a50, Descriptor: http://192.168.1.4:7676/rcr/, Root: true
TRACE 2022-07-03 12:09:40.488 [jupnp-registry-maintainer-1] org.jupnp.registry.Registry Removing remote device from registry: (RemoteDevice) Identity: (RemoteDeviceIdentity) UDN: uuid:56897635-989d-4741-af6f-4e4378054a50, Descriptor: http://192.168.1.4:7676/rcr/, Root: true
TRACE 2022-07-03 12:09:40.488 [jupnp-registry-maintainer-1] org.jupnp.registry.Registry Removing expired: (RemoteDevice) Identity: (RemoteDeviceIdentity) UDN: uuid:b98a07c0-ce0a-4d7a-96fe-a910b8a598ef, Descriptor: http://192.168.1.4:7678/nservice/, Root: true
TRACE 2022-07-03 12:09:40.488 [jupnp-registry-maintainer-1] org.jupnp.registry.Registry Removing remote device from registry: (RemoteDevice) Identity: (RemoteDeviceIdentity) UDN: uuid:b98a07c0-ce0a-4d7a-96fe-a910b8a598ef, Descriptor: http://192.168.1.4:7678/nservice/, Root: true
TRACE 2022-07-03 12:09:40.488 [jupnp-registry-maintainer-1] org.jupnp.registry.Registry Removing expired: (RemoteDevice) Identity: (RemoteDeviceIdentity) UDN: uuid:3652781f-2a94-4d6b-b872-b639acd69878, Descriptor: http://192.168.1.4:9197/dmr, Root: true
TRACE 2022-07-03 12:09:40.488 [jupnp-registry-maintainer-1] org.jupnp.registry.Registry Removing remote device from registry: (RemoteDevice) Identity: (RemoteDeviceIdentity) UDN: uuid:3652781f-2a94-4d6b-b872-b639acd69878, Descriptor: http://192.168.1.4:9197/dmr, Root: true
TRACE 2022-07-03 12:09:40.489 [jupnp-registry-maintainer-1] org.jupnp.registry.Registry Removing expired: (RemoteDevice) Identity: (RemoteDeviceIdentity) UDN: uuid:4e059cce-e9c4-427f-93b9-4fbe4a69276c, Descriptor: http://192.168.1.4:9119/screen_sharing, Root: true
TRACE 2022-07-03 12:09:40.489 [jupnp-registry-maintainer-1] org.jupnp.registry.Registry Removing remote device from registry: (RemoteDevice) Identity: (RemoteDeviceIdentity) UDN: uuid:4e059cce-e9c4-427f-93b9-4fbe4a69276c, Descriptor: http://192.168.1.4:9119/screen_sharing, Root: true

Not sure if this has anything to do with it as it mentions screen sharing but that is the last time your TV's IP is listed.

There has been a lot of changes to the logging in V11 so I am not familiar with it yet but I don't see anything obvious that is stopping it.
I think this is one the Devs will have to look at.

[superkyle96]

I appreciate anything you can suggest!

[SubJunk]

Sorry to see you're having this problem, let's try to fix it.
Usually we see this when UMS has bound to a different interface than the device, meaning we can receive their messages but they can't receive ours. I see you've already thought the same thing but maybe we have a related bug to track down.

Please select the correct network interface in the forced setting, fully close UMS, start it again, and then provide logs after reproducing the bug. Then I will look in the logs and see if the setting is being ignored or something

[superkyle96]

Thanks for helping. I didn't/don't know which interface I'm supposed to you...so I tried them all. I also tried forcing the port to 6001 as another person suggested.

[SubJunk]

The correct one is the one that is on the same network as your TVs. From your previous logs it looks like they're on the IP `192.168.1.4` which the computer is receiving via 192.168.1.36 which is "Realtek Gaming GbE Family Controller".
So if you can please force that interface, close and start UMS, and then attach the logs, that will help

[AmyWilliams]

It sounds like a firewall issue: UMS sees TV, but TV doesn't see UMS. Try disabling the Windows firewall to see if it fixes the issue.