Windows 10 & McAfee Firewall issues with Bonjour

Submitted by ReedN on #1

I am using VirtualHere between a Windows 10 host and a Windows 10 Hyper-V virtual machine. I can get VirtualHere to work if I lookup the host's IP address and paste it into the client tool. However, the host IP address is DHCP and can change and it is cumbersome to do it this way.

I would like to use Bonjour to automatically detect the host server. However, due to firewall issues (I assume), I'm not able to get that to work.

Can anyone suggest:
1) Ways to get it to work with Windows 10/McAfee?
2) If I can't get Bonjour to work, are there easier ways than manually looking up the host IP and pasting it into the client tool?

Submitted by ReedN on Wed, 2020/05/06 - 11:11

#2

If there is a way for the Virtual Machine (Hyper-V) to discover the IP address of the host, could I issue a command using the API, like this to tell the client where to look?

Specify server to connect to:
"MANUAL HUB ADD,
[:port] | "

Submitted by Michael on Wed, 2020/05/06 - 11:59

#3

Bonjour (Auto-Find) uses UDP port 5353 so just open that and it will work

Submitted by ReedN on Thu, 2020/05/07 - 00:50

#4

In some corporate environments the computer user isn't at liberty to control the firewall. I'm checking with IT to see if it is possible to open it, but they may just be lazy and say they won't help or adjust their settings.

Submitted by Michael on Thu, 2020/05/07 - 09:50

#5

If you cant control the firewall you must manually look up the server ip address somehow and then add it to the client by right clicking USB Hubs->Specify Hubs.. or you can use the MANUAL HUB ADD call that would also work fine.

Submitted by ReedN on Thu, 2020/05/07 - 10:28

#6

This I think might work. It plucks the host name out of the Hyper-V VM's registry and adds it to the hub list. both the PhysicalHostNameFullyQualified and the PhysicalHostName seem to work.

Batch file implementation, remove the extra "%" for command line use:

for /F "tokens=3" %%A in ('reg query "HKLM\Software\Microsoft\Virtual Machine\Guest\Parameters" /v PhysicalHostNameFullyQualified') DO (vhui64 -t "manual hub add,%%A:7575")
for /F "tokens=3" %%A in ('reg query "HKLM\Software\Microsoft\Virtual Machine\Guest\Parameters" /v PhysicalHostName') DO (vhui64 -t "manual hub add,%%A:7575")

Can anyone think of a better solution? I was thinking of launching and then executing this right after to add the host.

Submitted by Michael on Thu, 2020/05/07 - 14:05

#7

Yes that should work (you dont need to bother putting the port in, although you can if you want)

Submitted by Shea S. on Sat, 2020/05/16 - 14:30

#8

I feel like you have bigger problems if you can't just resolve the host name. What is the lease time on the IP address?