Minimserver greyed out

[nyron59]

Following recent updates of Java and Minimserver, each time I launch Minimwatch the boxes are greyed out except for the bottom 3.

I have had similar problems previously and have managed to resolve them but not this time. I am using Windows 7 and am convinced that the problem relates to Java.

What I have tried:

Control Panel
System and Security
Windows Firewall (managed by McAfee Personal Firewall)
Allow a program through Windows Firewall
Java ™ Platform SE Binary
Private/Public both ticked

Also: Evented I//Ofor v8 JavaScript unticked (I don't actually know what this means)

I have been at this for hours unsuccessfully looking for solutions. Can you help?

[simoncn]

This is a firewall issue. Either your Windows firewall or your McAfee firewall (perhaps both) is configured to accept incoming connections to the previous version of Java that you were using. You need to update the relevant firewall rule(s) to point to your new version of Java. There are a number of previous forum threads discussing this issue.

[nyron59]

Apologies Simon. Didn't intend to multiple post question. Error on my part.

Appreciate the problem is my Firewall. Have tried unsuccessfully to find posts that have provided the solution but will keep looking.

[simoncn]

For instructions on how to update the Windows firewall, see this post. I haven't used McAfee and I don't know what is needed there.

[janders1954]

I am also having the greyed out Minimwatch icon problem also. It started abot a week ago, when we replaced the wireless router. Router settings have to be correct. Music plays fine, playlists work fine. This greying out issue is the main problem now. I even had remote support from the company I pirchased the systems from. Their conclusion - old PC hardware is incompatible with newer versions of all of the software involved (minimserver, minimwatch, java, etc). I can't buy that answer, seeing how many others are having the same issue - worls one day, doesn't work the next.

I have tried pretty much everything I have seen in this forum, from the minimserver web site, and from Linn in England, the maker of my DAC

I can ping the NAS (QNAP-TS251+) and the DAC (Linn Akurate DS). I disabled the firewall. No good. I verified the correct subnet in Properties (onet.subnet). Is there anything else I can check?

Thanks;

John A.

[simoncn]

From the minim icon, select Options > Show log (Watch). What is the active subnet?

[janders1954]

(10-11-2017 11:45)simoncn Wrote:  From the minim icon, select Options > Show log (Watch). What is the active subnet?

JA: From the log, the active subnet is "192.168.0.0". This appears to jive with my router settings, with all of the network IP addresses being in the range of 192.168.0.1 through 192.168.0.61(subnet mask = 255.255.255.0). In this log, however, is an indication something isn't right. I see numerous (40 and counting) occurrences of the following:
"Retrying monitor subscription for server at 192.168.0.61:9791(attempt xx)"

where xx is 1-41 with new attempts every minute or so.
By the way, 192.168.0.61 is the IP address of the QNAP NAS (fixed, out of the DHCP allocation range) as instructed by Linn (the Akurate DS builder). Does this provide any additional clues?

Regards;

John

[DavidHB]

(10-11-2017 16:12)janders1954 Wrote:  Does this provide any additional clues?

9791 is the default ohNet (openHome/UpnP stack) port for MinimServer. I shall be interested to see what Simon says is going on here.

David

[simoncn]

Thanks for this information. This confirms that the active subnet is correct and MinimWatch has successfully contacted MinimServer to initiate a subscription request. However, MinimServer has not been able to contact MinimWatch to complete the subscription setup and this is why MinimWatch is repeatedly retrying the subscription.

The problem is almost certainly caused by something on the machine running MinimWatch blocking inbound messages from MinimServer. Is the LAN connection of the MinimWatch machine marked as private or public? (It should be private.) If this isn't the problem, it is very likely to be caused by an incorrect firewall/antivirus setting. (McAfee is notorious for this.) As a test, try completely disabling all antivirus/firewall protection to confirm that this is the issue.

[janders1954]

Dear simoncn;

Funny you should mention the firewall and Mcafee. It happens that I have McAfee, and it was the cause of a similar issue where a Linn routine called "Konfig" appeared to have lost contact with the Linn Akurate (not a misspelling) DS (a DAC, among other cool capabilities). At the Linn tech's suggestion, I disabled the firewall, but it made no difference. But he then suggested adding an exception for the Konfig application (not sure if this is the correct term for it, or perhaps App) in McAfee. Anyway, sure enough, after going into McAfee's "Web and Email Protection" under Firewall, then "Internet Connections for Programs", I found "Linn Konfig". I then changed the setting from "Use designated ports " to "Open to all devices" as McAfee's web site suggested. And voila, Linn's Konfig now works!!! But if I leave Konfig open as I typically do, I hope I'm not leaving myself open to an attack somehow.

Anyway, I looked for a similar entry in McAfee's "Internet Connections for Programs" for MinimWatch. I didn't see anything, unless you all have an idea how the name is formatted so I can select it and do a similar port/device change.

I feel we (you guys) are converging on the answer, especially considering how it resolved my Linn Konfig issue. Any furher suggestions?

Thanks for the support guys!!

John