Threaded Mode | Linear Mode

simoncn · 15-08-2012, 09:33

(15-08-2012 09:05)psme Wrote: I don't know what happened, but recently, in my system, Controller can not see minimServer.

My PC is Win7 64bit. I have Asset UPnP 4, foobar2000 foo_upnp, and minimServer 0.52 running on the PC, all seeing the same song library.

On both iPad and desktop Kinsky (on the same PC with the servers), the Controller can always see the Asset UPnP and foobar2000 upnp.

But both Kinsky on desktop and iPad do not show minimServer. But, once I do a "restart" on minimServer control, then both Kinsky will show minimServer immediately. Then if I close either (or both) Kinsky and start Kinsky again, it won't show minimServer, while another Kinsky can access minimServer fine.

Besides "restart" the minimServer, if I let Kinsky at the "library" page long enough, maybe 10-15mins, then sometimes minimServer will show again.

This is a problem with multicast SSDP messages not being delivered by your network. I spent several months tracking this down and fixing it on my network.

When you restart MinimServer, it sends out an SSDP multicast 'alive' message. This message is being received correctly by Kinsky. This indicates that your PC is able to send multicast messages.

When you close Kinsky and start it again, Kinsky sends out an SSDP multicast M-SEARCH message, and MinimServer should respond with a unicast message. Because Kinsky doesn't get this response, this indicates that your PC isn't able to receive multicast messages.

MinimServer sends out repeated SSDP 'alive' messages at approximately 15-minute intervals. This explains why MinimServer appears in the Kinsky Library page some time later.

Is your PC connected to the network by a wireless network adapter, a wired network adapter, or both? If it is both, which adapter is configured for Kinsky on your PC?

If you're using a wireless network and it isn't set up correctly for IGMP snooping, this can cause SSDP multicast messages not to be delivered.

If your PC is connected to the network by a wireless adapter, try disabling and re-enabling this adapter, or disconnecting from and reconnecting to your wireless network. This is likely to get things working properly for a while.

Do you by any chance get this problem after suspending and resuming your PC? I had this issue and I tracked it down to a problem with the driver for my Intel wireless network adapter. If this is related to your problem, I have some software that might help you solve this.