I have a Windows 8 machine and need Virtual Machines. In order to share the network connection, there are a couple of options, but the "supported" method is to allow a wizard to create a virtual network adapter. Hyper-V takes over the machine and actually boots first and runs Windows 8 under it as well as the VMs. It maps the physical network adapter to a virtual one for the host operating system (windows 8) and other virtual adapters for each VM. Bottom line is that Profiler for the PC sees the virtual adapters IP address (169.254.xx.xx) instead of the "real" local IP (169.xx.xx.xx or 10.10.xx.xx). The mobile app (Android) can't navigate this and make the connection. For the moment, I am hard-coding the IP address for the physical adapter into the phone instead of the virtual IP. This works. But it would be better to be able to just type my server name, especially because the IP can change. I didn't want to have to assign static IPs for my machines. Not sure if this should be fixed on the PC side or the phone side, or if I am just going to have to setup static IPs or use the internet syncing instead.

Did I understand correctly that you are running DVDP share in host computer, not in virtual machines? I'm running my DVDP share in a virtual machine configured to use bridged network (VMware) and that's working correctly.

If the host is a "server" why don't you want to use static IPs? If you want to use DHCP you can always configure it so that it gives same IP for each machine based on their MAC-addresses. This way you can use DHCP and get the same IP every time (in your network).