This page contains information and guidance for solving various problems that come up frequently in forum posts. It will be expanded over time to cover additional topics.
Table of contents
My control point can't see MinimServer
If your control point can't see MinimServer or if MinimServer takes a long time to appear in your control point or if MinimServer appears for a time and then disappears, this probably means your network has a problem with multicast discovery messages.
Multicast networking problems can be difficult to diagnose and solve. They don't affect normal network traffic and only show up when you try to do something that involves multicast discovery.
As a first step, try disabling IGMP snooping (not IGMP proxy) in the configuration settings for your router and any switches (if this option is available).
If you have a BT HomeHub, try completely disabling the 5 GHz wireless band and using the 2.4 GHz band instead. This router is known to have problems with multicast messaging on the 5 Ghz band.
If this doesn't solve the problem, create a new thread in the Support section of the MinimServer forum as described on this page. Please include as much information about your network setup as possible, including the make and model number of your router and any switches, how the router and switches are connected to each other and how your other devices (including the NAS or computer running MinimServer) are connected to the router and switches.
Can't load AMD 64-bit .dll on a IA 32-bit platformIf you try to run the x64 version of MinimServer or MinimWatch on Windows using 32-bit Java, you'll get a message like this:
java.lang.UnsatisfiedLinkError:......\ohNet.dll: Can't load AMD 64-bit .dll on a IA 32-bit platform
You are getting this message because you have installed the x64 version of MinimServer or MinimWatch and you are using 32-bit Java as the system Java runtime. To fix the problem, you can uninstall 32-bit Java and replace it by 64-bit Java. Alternatively, you can leave 32-bit Java installed and use the x86 version of MinimServer or MinimWatch.
If you are seeing this message immediately after applying a Java update, this means the 32-bit version of the Java update was installed and has overwritten your previous installation of 64-bit Java. This can happen if you used a 32-bit browser to install the Java update. To fix the problem, uninstall the 32-bit version of the Java update and install the 64-bit version of the Java update by visiting this page, then clicking the JRE Download button and choosing the Windows x64 .exe file.
If you have both 64-bit Java and 32-bit Java installed and you get this message, this means that Windows is using 32-bit Java as the system Java runtime. To solve this problem, you need to uninstall 32-bit Java. If for some reason you need to keep 32-bit Java installed, you need to uninstall 64-bit Java and install the x86 version of MinimServer or MinimWatch.
MinimWatch can't find MinimServer
If MinimWatch can't find MinimServer and you are seeing a grey minim icon with only the Options, Refresh and Exit menu choices available, the first step is to check whether MinimServer is running. You can do this by using a UPnP control point to find your MinimServer library or you can try to access the MinimServer status web page by entering http://x.x.x.x:9790 into the address bar of a web browser, where x.x.x.x is the IP address of the machine running MinimServer.
If MinimServer is running, the next step is to check whether there is a firewall setting on the PC or Mac running MinimWatch that is blocking access to MinimServer. Try completely disabling the firewall to see whether this is the problem. If this enables MinimWatch to discover MinimServer, you need to change your firewall settings to allow inbound connections to the Java(TM) Platform SE binary (if MinimWatch is running on Windows) or to allow inbound connections to MinimWatch (if MinimWatch is running on a Mac).
Another possibility is that there are multiple network adapters (real or virtual) on the
PC or Mac running MinimWatch. In this case, MinimWatch might be listening on the wrong adapter. You can check
this by selecting Options > Show log (watch) from the grey minim icon and looking for the
"Active subnet" line. If this isn't the correct subnet for the machine running MinimServer,
you need to selecting Options > Properties (watch) from the grey minim icon and set the
ohnet.subnet property for MinimWatch as
described in this section.
After changing the
ohnet.subnet property, exit and relaunch MinimWatch.