MinimWatch problem with Hyper-V
|
25-02-2018, 16:51
Post: #1
|
|||
|
|||
MinimWatch problem with Hyper-V
I'm running MinimWatch on a Windows 10 Pro system, that has Hyper-V installed, monitoring MinimServer on a QNAP system. This has been fine for several years, but I've recently noticed that MinimWatch is now greyed out.
The only recent changes that I recall are Java 8 to Update 161 and some Windows updates including 2018-02 Cumulative Update for Windows 10 Version 1709. I've read the "MinimWatch not running after Java update" thread but think this is different. The MinimWatch logs shows MinimWatch 0.8.4 update 57, Copyright © 2012-2017 Simon Nash. All rights reserved. Java SE Runtime Environment (build 1.8.0_161-b12) Java HotSpot 64-Bit Server VM (build 25.161-b12, mixed mode) Platform default charset is windows-1252 Active subnet is 192.168.50.176 Startup complete That active subnet is not what I'm expecting, it should be 192.168.128... ipconfig /all shows Ethernet adapter vEthernet (Default Switch): Connection-specific DNS Suffix . : Description . . . . . . . . . . . : Hyper-V Virtual Ethernet Adapter Physical Address. . . . . . . . . : 7E-15-F8-78-CF-26 DHCP Enabled. . . . . . . . . . . : Yes Autoconfiguration Enabled . . . . : Yes Link-local IPv6 Address . . . . . : fe80::c8dc:be56:732f:c7e9%2(Preferred) IPv4 Address. . . . . . . . . . . : 192.168.50.177(Preferred) Subnet Mask . . . . . . . . . . . : 255.255.255.240 Ethernet adapter vEthernet (External Virtual Switch): Connection-specific DNS Suffix . : Home Description . . . . . . . . . . . : Hyper-V Virtual Ethernet Adapter #2 Physical Address. . . . . . . . . : 64-00-6A-30-8F-5A DHCP Enabled. . . . . . . . . . . : Yes Autoconfiguration Enabled . . . . : Yes IPv6 Address. . . . . . . . . . . : 2a02:c7d:7e63:c600:a15c:865c:560d:2e9a(Preferred) IPv6 Address. . . . . . . . . . . : fdc4:c74f:c51a:0:a15c:865c:560d:2e9a(Preferred) Temporary IPv6 Address. . . . . . : 2a02:c7d:7e63:c600:1117:26ec:208e:602b(Preferred) Temporary IPv6 Address. . . . . . : fdc4:c74f:c51a:0:1117:26ec:208e:602b(Preferred) Link-local IPv6 Address . . . . . : fe80::a15c:865c:560d:2e9a%7(Preferred) IPv4 Address. . . . . . . . . . . : 192.168.128.4(Preferred) Subnet Mask . . . . . . . . . . . : 255.255.255.0 It looks like MinimWatch is getting the active subnet based on the IPv4 adddress of Ethernet adapter vEthernet (Default Switch) and one of the Windows updates has changed Hyper-V networking. Any ideas to get MinimWatch working again would be gratefully appreciated. Thanks Paul |
|||
25-02-2018, 18:28
Post: #2
|
|||
|
|||
RE: MinimWatch problem with Hyper-V
Sorted - as documented in the Troubleshooting section, I've used the ohnet.subnet property to specify the correct subnet.
|
|||
« Next Oldest | Next Newest »
|
User(s) browsing this thread: 1 Guest(s)