DLNA stops 'working' after hyper-v installation

I know this isn't a serviio problem, but I've exhausted several other avenues to try and solve this and wondered if you guys have any thoughts.

As a developer, I use Hyper-V for all sorts of reasons on my home Windows 8 Professional PC. When I first installed Serviio I didn't have hyper-v installed and things worked like a charm, then suddenly (visual studio 2012, I'm looking at you) my xbox (as a DLNA client) stopped being able to contact the serviio service. After many evenings of pain, I figured out that it was indeed the hyper-v installation and simply disabling the role - effectively uninstalling it - let serviio do it's thing again.

While hyper-v is installed, it creates duplicate virtual network adapters for each of the physical cards available and assigns the IP address and other associated settings up to the virtual adapter. The physical adapters can not be configured separately any more which is a trick to allow hyper-v to manage the virtual network and VM communication.

What I can't work out is why this would make any difference to a DLNA service - I've tried disabling the firewall in windows as the only thing I can think of that would block this traffic, but that made no difference.
All other network traffic seems to work find (I host a personal website on my machine showing how traffic can get to my PC still without any issue).

Short of installing a packet sniffer (and probably not getting anywhere with the traffic analysis there anyway) can anyone suggest what I could try?

Cheers.

I might had a similar problem, turning off the Windows firewall did not help, but on the NIC a driver called "Virtual PC Network Filter driver" was enabled. After disabling it Serviio works fine. However, I do not know what effects disabling it has on Hyper-V, as I do not use it (honestly I do not know why this was enabled at all...).

I'm pretty sure that disabling that option stops the VM from communicating with the physical network adapters.

I found a workaround, but it doesn't seem to be a complete science, just something that worked then broke again after a reboot, then worked again when I re-did the 'fix'. I hate that kind of issue, but I rarely reboot my PC so it's not often an issue.

The fix for me was to go to serviio's console, on the status drop-down click another adapter, or "automatically detect" which will light up the "reset" and "save" button. Click "Reset" and you'll find that instead of the physical adapter name (e.g. Marvell Yukon......") you'll see the Hyper-V virtual adapter(s). Pick the one that is connected to your LAN if you have more than one, and click Save.

I can't remember if I had to restart the service, but that seemed to work for me.

Look like there's a problem with the adapter binding in serviio, possible at a very low level. When installing Hyper-V, the LANA numbers or MAC addresses might change or get screwed up which mucks up the stored binding for serviio... Just a guess, hopefully the above helps someone.