Minimwatch doesn't connect to minimserver on qnap

[leo0815]

Hello

I'm actually facing the problem that minimwatch on Linux x86 doesn't connect to minimserver on my QNAP NAS anymore. Th icon just remains grey. There have been no major updates on either the linux machine or the NAS.

minimserver itself is running, working fine and responds to browser requests on 192.168.10.3:9790 and 192.168.10.4:9790 (the NAS' ip addresses)

According to the troubleshooting page I've checked:
- there is no firewall on the linux machine (sudo ufw status returns 'disabled')
- I've set ohnet.subnet to 192.168.10.0 in the minmwatch properties but with no success

Versions are
- minimserver: 2.0.12 update 193, there is no update offered by the QNAP app store
- minimwatch: 2.0.18

Is there anything else to check?

[simoncn]

If you haven't already done so, you could try powering off all your network equipment and powering it on again, as described in this section.

A first step would be to just power off the Linux machine and the QNAP and power them on again.

[leo0815]

as already mentioned, I'm already facing the problem for a couple of weeks. Both machines have been powered off several times since then (the linux machine every night to be exact). Furthermore I've just opened vlc on linux and it connects to minimserver too, so there doesn't seem to be a problem with the connection between both machines,

But in the moment when I wanted to click 'Post Reply' I've seen then now minimwatch could connect too. Is it possible that my vlc test somwhow enabled the connection or is it just coincidence?

[simoncn]

As starting VLC somehow made a difference, this seems likely to be a multicast discovery issue, possibly caused by IGMP snooping being enabled on your router. Please let me know if MinimWatch loses its connection to MinimServer after 30 minutes or so.

[apw2607]

Hi there, I seem to have ran into the same issue. The weird thing is, it was working fine. Not sure why now the icon is grey.

My setup is just a little bit different.

Minimserver is running on a Synology DS218+
Mimiwatch is running on a Intel MacMini. Mimiwatch icon remains grey.

Minimserver, functionally seems to be working fine.

Like I said, it was working fine. Tried rebooting Synology, Mac, etc ... Firewall is not enabled on Mac or Synology.

Is there anyway to troubleshoot the issue. is there a log file i can look at? Thanks, Adrian

[simoncn]

Please start by powering all your network equipment and network-attached devices off and on, as described in this section. If this doesn't fix the problem, I can post additional suggestions.

[apw2607]

Hi there, got it working again. The link was helpful. What happened was that my Mac has two network adapters where it belongs to multiple networks. For some reason the network order on my Mac had switched, so minimwatch was looking for minimserver on the wrong network. Hence the greg icon. Once I reordered the networks correctly on my mac, minimwatch found minimserver again, and Harmony was returned.

[simoncn]

You can also set the ohnet.subnet property in MinimWatch (not MinimServer) to force the use of a specific network adapter.

[RSJ]

I have recently developed a similar problem. I have MinimServer running on a QNAP and MinimWatch on a Windows 11 lap top. Until two days ago, everything was functioning as expected. Since then, MinimWatch has failed to connect to MinimServer.

What I find puzzling is that I can see the MinimServer music library as a network media device in File Explorer. Linn Kazoo and Linn Konfig are also connecting to MinimServer. So, there is no problem playing music, but I would not be able to use MinimWatch to edit MinimServer properties.

I suspect it may be that a Windows update may have caused this glitch, but it is still strange that MinimServer can be seen on the network, just not by MinimWatch.

[simoncn]

(15-11-2022 16:04)RSJ Wrote:  I suspect it may be that a Windows update may have caused this glitch, but it is still strange that MinimServer can be seen on the network, just not by MinimWatch.

This indicates that the problem is on the MinimWatch/Windows side, not the MinimServer side.

This problem (where a working setup suddenly stopped working) is usually caused by one of the following:

1) Your Windows network type has changed from private to public
2) A Java update has changed your Windows firewall settings and these settings are now blocking Java and MinimWatch from receiving inbound network messages
3) A change to your Windows network configuration is causing MinimWatch to connect to the wrong network adapter

For information about how to solve these issues, see this section.