MinimWatch Java Connection Problem
|
10-08-2023, 13:58
(This post was last modified: 10-08-2023 14:02 by cromac.)
Post: #1
|
|||
|
|||
MinimWatch Java Connection Problem
Hi Simon,
since the last Java version 8 Update build 381 (WIN 64Bit) the MinimWatch app (2.2 update 110) can't no longer connect to my Synology server. The result is a grey tray icon. I checked the firewall-inbound rules and UDP/TCP traffic is allowed on Java installation path C:\program files\java\jre-1.8\bin\javaw.exe The server access via browser works as expected. MinimServer 2.2 update 240 on Synology (DS220+) Version: 7.2-64570 Update 1, MinimStreamer 2.0.11 It worked with the previous Java version (think it was build 361). The only difference I see in the FW rules is that they are no longer referencing the Java build version as seen before. Maybe that's the problem? My System is WIN 11 Pro, version 22H2 latest update. Could you please check, if there's something on it or if it is only my computer? Thank you in advance Best cromac |
|||
11-08-2023, 11:13
Post: #2
|
|||
|
|||
RE: MinimWatch Java Connection Problem
This setup should be fine if Windows is using the file C:\Program Files\Java\jre-1.8\bin\javaw.exe to run MinimWatch. You can check this by running the command "ftype jarfile" from a Windows command prompt. What output do you see from this command?
|
|||
11-08-2023, 17:07
Post: #3
|
|||
|
|||
RE: MinimWatch Java Connection Problem
(11-08-2023 11:13)simoncn Wrote: This setup should be fine if Windows is using the file C:\Program Files\Java\jre-1.8\bin\javaw.exe to run MinimWatch. You can check this by running the command "ftype jarfile" from a Windows command prompt. What output do you see from this command? I see this output Code: jarfile="C:\Program Files\Java\jre-1.8\bin\javaw.exe" -jar "%1" %* so seems to be right, but still a gray tray icon. Mysterious |
|||
11-08-2023, 19:15
Post: #4
|
|||
|
|||
RE: MinimWatch Java Connection Problem
This can happen if your Windows network type has somehow been changed from private to public. The firewall usually blocks all inbound messages if the network type is public and applies inbound rules if the network type is private.
|
|||
14-08-2023, 08:02
Post: #5
|
|||
|
|||
RE: MinimWatch Java Connection Problem
(11-08-2023 19:15)simoncn Wrote: This can happen if your Windows network type has somehow been changed from private to public. The firewall usually blocks all inbound messages if the network type is public and applies inbound rules if the network type is private. The firewall is open on both networks (private and public), nothing changed. Any other idea? Best cromac |
|||
14-08-2023, 10:45
Post: #6
|
|||
|
|||
RE: MinimWatch Java Connection Problem
From the grey MinimWatch icon, select Options > Show log (watch). Do you see any error messages in the MinimWatch log? Also, what is shown for the active subnet?
|
|||
14-08-2023, 11:41
Post: #7
|
|||
|
|||
RE: MinimWatch Java Connection Problem
(14-08-2023 10:45)simoncn Wrote: From the grey MinimWatch icon, select Options > Show log (watch). Do you see any error messages in the MinimWatch log? Also, what is shown for the active subnet? Yes, that was the right approach. It has used my Virtual Box Ethernet Adapter which is called 'Ethernet 4' and my normal network adapter is 'Ethernet 5', so I renamed it to 'Ethernet 3' and the problem is fixed. It moved alphabetically through the network adapter. Is there a way to assign the right adapter to the program manually or is it done on the system level? Best cromac |
|||
14-08-2023, 13:22
(This post was last modified: 14-08-2023 14:44 by simoncn.)
Post: #8
|
|||
|
|||
RE: MinimWatch Java Connection Problem
To ensure you are using the correct subnet (selection in alphabetical order is not guaranteed), set the ohnet.subnet property on the MinimWatch properties page (not the MinimServer properties page) as described in the last paragraph of this page.
|
|||
« Next Oldest | Next Newest »
|
User(s) browsing this thread: 1 Guest(s)