mConnect and BubbleUpnP do not discover MinimServer

[Pepsican]

(18-03-2024 16:34)simoncn Wrote:  Thanks for this capture log.

In packets 5696-5700 (213 seconds), MinimServer sends NOTIFY messages for the first time. Kazoo running on the PC receives these messages and connects to MinimServer.

Prior to this in packets 421/440/444 (18 seconds), Kazoo sends some M-SEARCH requests to the multicast address 239.255.255.250 (the multicast address for UPnP discovery). This request is looking for UPnP devices on the network. There are many subsequent similar M-SEARCH requests. MinimServer running on the NAS doesn't respond to any of these but a Linn device at address 192.168.22.20 does respond in packet 422. This means that your network is able to forward M-SEARCH requests to the Linn device but is not able to forward M-SEARCH requests to the NAS.

Is there a difference in how the Linn device and the NAS are connected to the network?

That Linn device is my SOtM SMS-200. Both are connected by cable to the Switch. The SMS-200 is connected on the AP Gigabit port (which is pass-through) and the NAS is connected via cable directly to the switch. As we have now eliminated the switch as being the problem, we should focus on the NAS then?