Timeout of 2 minutes on mdns resolution

[sleman]

I'm advertising a service on similar to the example:

var service = new ServiceProfile("x", "_foo._tcp", 1024);
var sd = new ServiceDiscovery();
sd.Announce(service);
sd.Advertise(service);

I run this on a windows machine with .net 4.6.1.

On Mac, I can see the service using dns-sd. It resolves to x.foo.local. If I ping x.foo.local on the mac, it resolves the windows machine IP address and pings are successful. After exactly two minutes, If i start a new ping, it fails to resolve the IP address even though my app is still running.

I also tried sd .Mdns.Start(); and the issue still occurs.

I'm running latest (0.27.0) from NuGet.

[davidzwa]

Hmm, I'm able to successfully keep a connection live for more than weeks, but I do have to admit I havent got true logging information. I will ask my work group to setup a e2e testing setup, so we can test the ins and outs of this library.

My experience: firewall of Windows throws mud in the water. Maybe try and use something like Bonjour Browser or ZeroconfDiscovery tools to get more info on that moment. I'd be eager to hear back if you've done so.

@richardschneider any hunch to what the cause might be?