MinimServer Forum

Full Version: minimwatch problems
You're currently viewing a stripped down version of our content. View the full version with proper formatting.
Hi Simon

I just updated my Windows 64bit 8.0 pro to 8.1

From that moment on minimwatch isn't showing my
Minimserver Instances anymore.

I am running 32bit Minimwatch and 32bit Java

Deactivating the firewall didn't help
Reinstalling Minimwatch 0.81 update 10 didn't help either
(I did delete the AppData files)

Kinsky desktop shows all 9 running instances of Minimserver

The log of Minimwatch says:
Startup complete

Any Ideas ?
(31-12-2013 17:24)Oliviander Wrote: [ -> ]Hi Simon

I just updated my Windows 64bit 8.0 pro to 8.1

From that moment on minimwatch isn't showing my
Minimserver Instances anymore.

I am running 32bit Minimwatch and 32bit Java

Deactivating the firewall didn't help
Reinstalling Minimwatch 0.81 update 10 didn't help either
(I did delete the AppData files)

Kinsky desktop shows all 9 running instances of Minimserver

The log of Minimwatch says:
Startup complete

Any Ideas ?

Do you have more than one active network adapter (real or virtual)? If so, MinimWatch is probably using the wrong adapter. You can use the ohnet.subnet property in Options > Properties (watch) to make MinimWatch use the correct adapter.
(31-12-2013 17:35)simoncn Wrote: [ -> ]Do you have more than one active network adapter (real or virtual)? If so, MinimWatch is probably using the wrong adapter. You can use the ohnet.subnet property in Options > Properties (watch) to make MinimWatch use the correct adapter.

On this machine I have only one adapter
so this shouldn't be a problem.

I have other machines with more adapters
all with Win 7 pro 64 bit and with minimwatch working
without problems by now.
Even without specifying a subnet.
Do I have to write something like

172.20.0.0

in the ohnet.subnet property to specify it ?

I tried that but it didn't help !

Anybody other ideas ?
Problem solved !

Accidentally my Network Settings changed from
private to public through the upgrade process.
(I Can't imagine how this happened ??)

So it was actually a firewall issue, that I didn't
recognize at first, as I deactivated the firewall for
private networks only.
Reference URL's