Minimwatch issue

[paulM]

I appear to have created a bit of an issue with Minimwatch on my Windows 10 desktop PC. It happened when I upgraded Java to version 431.

I have 2 implementations of Minimserver and both are fine. They are visible on all of my control points and play music without issue. Minimwatch can see one of them, but since the upgrade has stopped seeing the other. The one that Minimwatch can see is on a QNAP HS251 running QTS 4.3.6.2805 and the one that Minimwatch can't see is on a QNAP TS651 running QTS 5.2.1.2930. The main difference that I can see is the version of QTS, but I don't know whether that is the issue.

Given that Minimserver, Minimwatch and Java all work together on the HS251, I am guessing that the Java upgrade has created an issue with the TS651 but I don't undestand why.

The Minimwatch log gives the following information. It seems to be in a loop, continually retrying to find the TS651 as shown below. The minimwatch log provides the only clue I know how to find.

MinimWatch 2.2 update 114, Copyright © 2012-2024 Simon Nash. All rights reserved.
Java™ SE Runtime Environment (build 1.8.0_431-b10)
Java HotSpot™ 64-Bit Server VM (build 25.431-b10, mixed mode)
Platform default charset is windows-1252
System platform is windows-x64
UPnP port 9791 has been selected
Active subnet is 192.168.0.0
Startup complete
MinimServer[NAS-Media] is running
Retrying monitor subscription for server at 192.168.0.2:9791 (attempt 1)
Retrying monitor subscription for server at 192.168.0.2:9791 (attempt 2)....
etc....
etc....
Retrying monitor subscription for server at 192.168.0.2:9791 (attempt 316)

I have rebooted the TS651 in the hope that a reboot will help but to no avail

Is there something that I need to do to correct this issue?

[simoncn]

Please see this thread (created by you) for a solution.

[paulM]

Yet again, thanks Simon. My lack of understanding of how all these things work together knows no bounds. In this case, even my memory of a previous instance escaped me as well. I clearly have the memory span of a gnat.

I still don't understand why ESET blocks one server but not the other after a Java update, not that it matters. The funny thing is that the blocked address in ESET was 192.168.0.3 and not 192.168.0.2. Unblocking it nevertheless cured the problem.

Thank you very much.