controller cannot see minimServer

[simoncn]

(20-08-2012 09:44)psme Wrote:  I'm not 100% sure, but it does seem both PC and QNAP minimServer SSDP listening stopped at the same time. I will pay more attention next time.

Also, the minimServer on my PC will stay in gray color and inoperative.

Do you mean the MininWatch tray icon on your PC? It isn't possible for the MinimServer tray icon to be gray. The MinimServer tray icon on your PC should be green if MinimServer is still running. The MinimWatch tray icon on your PC would be gray if MinimServer on the QNAP isn't receiving multicast messages or if MinimWatch on the PC isn't receving multicast messages.

Quote:If there is no other test that I'd do, then I'll quite minimServer and start again.

I've compared the output from your netstat -nab to my output from this command, and there seems to be an important difference. In your output, the address that's bound to port 1900 is 0.0.0.0. In my output, this address is my PC's network IP address 192.168.0.14. This might be related to the problem. Please can you redirect the complete output from netstat -nab to a file and attach it here.

What happens if you exit the MinimServer process and restart it? Do you still see 0.0.0.0 bound to port 1900, or do you see your PC's IP network IP address? Please can you also attach the complete output from doing this.

Quote:PS: maybe minimServer can add some code to check SSDP bounding as well?

Port binding is handled by ohNet. I don't think it would be useful for MinimServer to check that port 1900 is bound by the process, because it couldn't do anything to fix this problem if the port becomes unbound.