Minimwatch

[paulM]

MinimServer has been performing flawlessly on my QNAP NAS for quite some time now - and continues to do so. However, for the past couple of days, MinimWatch has been unable to see MinimServer and is greyed out on my toolbar. This is despite the fact that all of my control points (on Windows PC, IPad and Android devices) can see and MinimServer and control the playback functions. Even my TV sees MinimServer (and I never play music via the TV!).

The MinimWatch log repeats the line

Retrying monitor subscription for server at 192.168.0.4:9791

This line repeats every so often and can attempt several hundred time over.

I have made no changes on my NAS - I'm not competent enough to go tinkering with settings, but something has happened to prevent MinimWatch from seeing MinimServer. Does anyone have any idea how to resolve this?

[simoncn]

This message means that MinimWatch is being blocked by the Windows firewall. This is probably caused by a recent update to Java on your Windows system. For details of how to fix this problem, see this post.

[paulM]

(02-03-2023 12:10)simoncn Wrote:  This message means that MinimWatch is being blocked by the Windows firewall. This is probably caused by a recent update to Java on your Windows system. For details of how to fix this problem, see this post.

Thanks for that Simon. I don't use the Windows firewall, so the advice on how to fix it does not apply to my case, but I momentarily turned off my ESET internet security firewall and refreshed MinimWatch and bingo! - Minimwatch turned green and returned to full functionality.

The firewall is back on now though, and MinimWatch has turned grey again, but at least I now have my culprit. I'm not sure whether the advanced setup of the ESET firewall has any similarities to the Windows setup, but TCP and UDP port scanning are mentioned as shown on the attachment. I can't see anything obvious, but I will see if I can find any clues in the ESET program.

[paulM]

(02-03-2023 14:02)paulM Wrote:  

(02-03-2023 12:10)simoncn Wrote:  This message means that MinimWatch is being blocked by the Windows firewall. This is probably caused by a recent update to Java on your Windows system. For details of how to fix this problem, see this post.

Thanks for that Simon. I don't use the Windows firewall, so the advice on how to fix it does not apply to my case, but I momentarily turned off my ESET internet security firewall and refreshed MinimWatch and bingo! - Minimwatch turned green and returned to full functionality.

The firewall is back on now though, and MinimWatch has turned grey again, but at least I now have my culprit. I'm not sure whether the advanced setup of the ESET firewall has any similarities to the Windows setup, but TCP and UDP port scanning are mentioned as shown on the attachment. I can't see anything obvious, but I will see if I can find any clues in the ESET program.

Simon - the ESET troubleshooting wizard took me straight to the problem. Java had recently been blocked by ESET but I had the option to unblock as shown on the attachment. All is now well again and thanks again.

[Peter StreamMagic]

The ESET troubleshooting wizard took me straight to the problem. Java had recently been blocked by ESET but I had the option to unblock as shown on the attachment. All is now well again and thanks again.


I also use ESET and sometimes have the same problem.
Unblocking solves the problem but it is no guarantee it will not come back.
It would be nice to find an advanced setting to prevent ESET blocking.

[simoncn]

This problem occurs because the Java update changes the path to the Java executable. It is a problem with Java, not with ESET.

[Peter StreamMagic]

(02-03-2023 17:51)simoncn Wrote:  This problem occurs because the Java update changes the path to the Java executable. It is a problem with Java, not with ESET.

Thanks for explaining.
In general I come across ESET blocking devices (linn,UniFi, tablets…) randomly ( there must be some problem) and unblocking always solves the problem.
Sometimes frequently, sometimes months without any issues

[paulM]

(02-03-2023 17:38)Peter StreamMagic Wrote:  The ESET troubleshooting wizard took me straight to the problem. Java had recently been blocked by ESET but I had the option to unblock as shown on the attachment. All is now well again and thanks again.


I also use ESET and sometimes have the same problem.
Unblocking solves the problem but it is no guarantee it will not come back.
It would be nice to find an advanced setting to prevent ESET blocking.

I've had ESET in one form or another for getting on for two decades and until yesterday I knew nothing about it blocking network traffic. Yet here I am today, unblocking essential traffic for a second consecutive day. This time it took 5 other services with it. I can't understand why, after all this time, ESET has started to do this. I certainly hope that it sorts itself out.