Error 'No such host is known. ' getaddrinfo failed for CloudHub_a55604.local.:7575

5 posts / 0 new
Last post
BrocadeElephant
Error 'No such host is known. ' getaddrinfo failed for CloudHub_a55604.local.:7575

Brand new user trying to get started.

brand new TPLink WR902AC, loaded with firmware downloaded today (cloudhub-tl-wr902ac-v1-initial.bin). Running Windows 10 Enterprise with the latest updates. Connect to the hub via WiFi, start vhui64.exe.

VHUI intermittently shows 'connecting to hub' but never connects, and the log window shows:

18:23:46 INFO :VirtualHere Client 4.5.2 starting (Compiled: May 14 2018 19:34:42)
18:23:46 INFO :Using config at C:\Users\wcl.TECHATL\AppData\Roaming\vhui.ini
18:23:46 INFO :IPC available at \\.\pipe\vhclient
18:23:46 INFO :Auto-find (Bonjour) on
18:23:46 INFO :Auto-find (Bonjour SSL) on
18:23:48 INFO :Error 'No such host is known. ' getaddrinfo failed for CloudHub_a55604.local.:7575
18:24:18 INFO :Error 'No such host is known. ' getaddrinfo failed for CloudHub_a55604.local.:7575
18:24:48 INFO :Error 'No such host is known. ' getaddrinfo failed for CloudHub_a55604.local.:7575
18:26:48 INFO :Error 'No such host is known. ' getaddrinfo failed for CloudHub_a55604.local.:7575
18:27:18 INFO :Error 'No such host is known. ' getaddrinfo failed for CloudHub_a55604.local.:7575
18:27:48 INFO :Error 'No such host is known. ' getaddrinfo failed for CloudHub_a55604.local.:7575

What is the next debugging step?

Thanks - I am looking forward to using this in a lot of places if I can get it to work...

Michael
.

OK the switch to windows 1803 update seems to have broken bonjour. Could you reinstall bonjour by uninstalling it in windows -> Apps and Features then letting the virtualhere client install it again. See if that fixes the issue.

BrocadeElephant
Bonjour was part of the problem - stopping the service needed

Michael - Bonjour does not show up in Apps and Features. I found it in 'Services" and stopped it at which point VirtualHere offered to re-install it. That got the Virtual Here client to see the hub.

Using the VirtualHere GUI, I configured the hub to connect to my wireless network. Looking at the router I see that it has connected and has an IP address, but VirtualHere's GUI can't find it. By manually adding the hub manually (by :7575 it has connected.

I am connected to the same WiFi SSID as the hub.

Any suggestsions as to how to make the hub discoverable?

Thanks for your help.

BrocadeElephant
..and it is only some machines that don't see the hub

On a VMWare Win10 system on the same host that can't autodiscover the WiFi connected hub VirtualHere CAN autodiscover the hub.

The only big difference is that the virtual machine is a 'virgin' - it is brand new and nothing has been installed on it other than Visual Studio. It did not already have the Bonjour service, so VirtualHere installed it.

Now that I've manually told the VH client to use the hub by IP address I don't know how to undo that to test auto-discover.

I am up and running so this isn't urgent - but any suggestions as to how to figure out what's wrong with the host's Bonjour setup would be appreciated.

Thanks!

Michael
.

Bonjour should always show in the Apps and Features in Windows otherwise Auto-Find will not work.

Log in or register to post comments