MinimWatch icon greyed-out

[tchuyev]

Hi, I'm trying to setup MinimServer on a Windows 8.1 PC and on a Synology NAS (DSM 5.1).
On the server side of things, both instances are up and running.
Java has previously been installed as per prerequisites, and seem to work no problem.

Wether it is on a Windows 7 (64-bit) client machine or on a Apple OS X (Mountain Lion), I just can't manage MinimWatch to work!
The only menus available are: Options, Refresh and Exit.
All other features are greyed out from the system tray icon.

>>> All firewall disabled, same subnet, no NAT...
>>> MinimWatch installer version matches locally installed Java (32 or 64-bit)...
>>> MinimServer and MinimWatch can ping each other both ways...
>>> All versions are up-to-date as of today...
>>> Logs do not show anything interesting...

MinimServer 0.8.3 update 6 + Java 1.7.9_79 (32-bit) are installed and running on DSM 5.1.5022 Update 4.
MinimServer 0.8.3 update 6 + Java 1.8.0_51 (64-bit) are installed and running on Windows 8.1 (64-bit).

Latest versions of Java are installed on Windows 7 and OS X clients.
MinimWatch is 0.8.3 update 32 on both Operating Systems.
Same behaviour on both clients.
No error message at launch.

What else should I check please? What am I missing?
This is driving me nuts. Thanks.

[simoncn]

(03-08-2015 22:47)tchuyev Wrote:  What else should I check please? What am I missing?
This is driving me nuts. Thanks.

If you have more than one network adapter (real or virtual) in the machine running MinimWatch, MinimWatch might be choosing the wrong adapter and/or subnet for listening. If the adapters are on different subnets, you can fix the problem by setting the ohnet.subnet property for MinimWatch as described in this section.

You can see which subnet is active for MinimWatch by selecting Options > Show log from the minim icon.

[tchuyev]

(04-08-2015 10:42)simoncn Wrote:  

(03-08-2015 22:47)tchuyev Wrote:  What else should I check please? What am I missing?
This is driving me nuts. Thanks.

If you have more than one network adapter (real or virtual) in the machine running MinimWatch, MinimWatch might be choosing the wrong adapter and/or subnet for listening. If the adapters are on different subnets, you can fix the problem by setting the ohnet.subnet property for MinimWatch as described in this section.

You can see which subnet is active for MinimWatch by selecting Options > Show log from the minim icon.

Spot on!!!

That was it: both client instances of MinimWatch (PC and Mac) were actually pointing to the wrong subnet due to Virtual Network adapters.
Edited 'ohnet.subnet' variable and all is good now.

Thanks for your support