hg paths runs a full Zeroconf conversation as well (basically serve uses
Zeroconf to multicast that it serves something, paths multicast that it want
to know who is serving _hg._tcp-based services). We can also get the
"client-based" exceptions at the server-side if we interrupt it at "just the
right time".