AlbumArtist and multiple tag values

[simoncn]

(29-06-2014 08:23)rpatriarca Wrote:  I do see the message. As per Windows firewall, I had the same thought while writing, and tried disabling it. Unfortunately without success.
Oddly enough, minimwatch seems also unable to detect the instance of minimserver running on the same PC (of course after changing the ohnet.subnet parameter). Unless it is an intentional behaviour, there is something wrong here.

This is intentional behaviour. It would be confusing to have both a MinimWatch icon and a MinimServer icon for the same local instance of MinimServer.

Quote:I used Wireshark to sniff network traffic and see what is happening. For simplicity I used one of vmWare subnets where there is no traffic. I can see minimwatch query packets being sent to a multicast address:

1 0.000000000 192.168.131.1 239.255.255.250 SSDP 159 M-SEARCH * HTTP/1.1
2 0.000151000 192.168.131.1 239.255.255.250 SSDP 160 M-SEARCH * HTTP/1.1
3 0.000268000 192.168.131.1 239.255.255.250 SSDP 156 M-SEARCH * HTTP/1.1

but nothing replies to them.

The source IP address should be 192.168.2.6, not 192.168.131.1. These packets are being sent by multicast to the 192.168.131.0 subnet and there are no UPnP devices on this subnet to respond to the packets.

If you set the ohnet.subnet property to 192.168.2.4 and restart MinimWatch, what do you see in Wireshark? Are any M-SEARCH packets sent from the 192.168.2.6 address? If so, are there any responses to these packets?