controller cannot see minimServer

[simoncn]

(16-08-2012 08:13)psme Wrote:  I didn't reboot the Qnap. "Disable", then "Enable" minimServer via Qnap web admin solves the problem. So I guess I don't really need to reboot my Win7 PC either. I should "quite/close", then re-run minimServer on my PC.

That might work, depending on how the Windows networking stack handles this situation. If this happens again on the PC, please try doing this and let me know if it fixes the problem.

Note that just because this makes MinimServer show up in the control point doesn't mean the problem is fixed. You'd need to close and restart the control point to be sure of that.

Quote:From a non technical end user point of view, it seems the problem comes from minimServer,

Yes, I agree that a non-technical user would think that, which is a problem. The arcane mysteries of IGMP snooping and multicast groups aren't something that users should need to know about. Unfortunately, the use of SSDP discovery and multicast messages is an unavoidable part of the UPnP architecture.

Quote:as all other network applications work fine, and I don't really need to reboot any hardware.

I don't accept that all other network applications work fine. I could probably find 100 threads or posts on the Linn forum over the last couple of years (not related to MinimServer) saying that Kinsky/Chorus/Songbook can't discover the DS or the server until one or other of these components is restarted. These problems are likely to be caused by similar network issues.

Quote:Anyway, will try those network stuff you mentioned...

I'll be interested to hear whether it solves the problem. I've had no more of these problems since I made these changes to my own network. Also, it's a good thing that you're not trying to do this with a wireless LAN, which introduces yet another dimension of multicast complexity.