Problems with MinimWatch and Updates

[simoncn]

Thanks for this log. When MinimWatch starts, it sends an M-SEARCH multicast discovery message to the active subnet 172.19.0.0. Any MinimServer instance that receives this message sends a response. These responses are not being received by MinimWatch. This means that either the M-SEARCH message from MinimWatch is being blocked by your network or the M-SEARCH responses from the MinimServer instances are being blocked by your network.

To confirm which of these it is, please do the following:

1) On one (only) of the MinimServer instances, set the ohnet.debug property to All. I will refer to this instance as the test MinimServer instance.
2) On the test MinimServer instance (only), set the logging level to Debug (not Trace)
3) On MinimWatch, set the ohnet.debug property to All and set the logging level to Debug (not Trace)
4) Exit MinimWatch
5) Exit and restart the test MinimServer instance
6) Start MinimWatch
7) Wait until the test MinimServer instance has been discovered by MinimWatch
8) Copy the minimwatch.log file to another location
9) Copy the minimserver.log file of the test MinimServer instance to another location
10) Compress both these log files to save space. This step is important.
11) If these files are small enough, attach them to a forum post. If they are too large for this, let me know and I will tell you how you can get them to me.

Important: Do not save either of these log files using the log window. You must use the minimwatch.log file and minimserver.log file from disk as described above. The disk files contain essential information that is not written when you save the log using the log window.