Minimwatch stopped working immediately as scanning was completed

[echable]

(09-12-2019 09:39)simoncn Wrote:  The value 255.255.255.0 is not the correct subnet value. It is a subnet mask, which is not the same thing.

From what you have said about the icon being green before changing to grey and also abut your computer being connected to a VPN, it is very likely that entering the correct subnet value in MinimWatch will fix the problem.

MinimWatch uses ohNet for UPnP communication with MinimServer. ohNet has a limitation that it can only communicate on a single subnet. If more than one subnet is available, ohNet picks a subnet at random. If it happens to pick the local subnet that includes your NAS, you will get the green icon. If it happens to pick the remote subnet for your VPN, you will get the grey icon. By entering a specific subnet in the ohnet.subnet property, you are preventing this random choice and ensuring that MinimWatch picks the correct subnet every time.

What is the local IP address of your NAS? The correct subnet value will be similar to this address but with the last number changed to 0. For example, if the local IP address of your NAS is 192.168.1.77, the correct subnet value to enter in MinimWatch would be 192.168.1.0.

MinimWatch works with both 32-bit and 64-bit Java.

Thanks for your reply.

Yes, I tried uninstalling and reinstalling both two Javas and Minimwatch. I've realised the correct value for the property in question is not the same as the subnet mask. The very short period Minimwatch was actually green it had 192.168.0.1 written there.

Now, however, I've reinstalled Minimwatch a thousand times. and trying to do it now proceeds as normal through the install process, but the resulting program never launches. How would I go about fixing a problem like that ? I've used both Iobit Uninstaller, which is more thorough, and its own uninstall interface.