mConnect and BubbleUpnP do not discover MinimServer

[Pepsican]

Oh my. Did I have an adventure this evening. Your question to swap connections made me discover that I had actually not yet connected my NAS to the switch (it was part of the plan for the new network so in my head this had happened). It was connected to the Arris Modem, which in turn is connected to the switch. Anyway, as soon as I connected the NAS to the switch, MinimServer was immediately discovered by Kazoo, mConnect and Bubble. So, it was not the switch or the NAS. It was the Arris.

I then tried to figure out why the Arris was not passing on the M-SEARCH and while I was searching I found some other things wrong with the modem. Its gigabit ports were working at 100Mb only. Long story short, I reset the damn thing, redid the configuration of it, fixed the port speed issue, found a bug for using NTP (if you want a different NTP server than the one set by the ISP/Arris, the device will not reboot and you have to reset it again), and never found the reason why the Arris will not pass on the M-SEARCH request (I tried port forwarding 1900 to the NAS, did not work, checked all settings but could not find anything obvious).

I give up, it just solidifies my believe that excluding the ISP provided device as much as possible from your network is a good move.

So in conclusion, the problem is solved by connecting the NAS directly to the switch (yay TP-Link!), but no idea why the Arris is not doing its job properly. And quite frankly, I must have had this issue before I think, but I either didn't care enough about it or it was not as bad as it has been in the past week.