Windows Client Unable to Connect to Pi Server

Submitted by gigamajig on #1

My VirtualHere Client, which has previously worked with no issues, has stopped connecting to my Raspberry Pi v3. The autofind attempts to connect to the server, but repeatedly fails, with the System Messages just repeating:

INFO :Could not connect to raspberrypi.local.:7575

over and over again. I've attempted to manually put the Pi's IP address in but I get the same error with the IP address in place of "raspberrypi.local".

The client does continue to work with an Android server I have set up on my Nvidia Shield, so I don't think the issue is on Windows' end, but nothing has changed on my Pi that would make me think it should fail. Any help or advice possible would be appreciated.

Submitted by Michael on Mon, 2020/03/02 - 07:50

#2

OK that is a bug in Bonjour.

In windows -> Apps and Features-> Bonjour -> Repair (or uninstall)

Then let the virtualhere client install bonjour again

Submitted by gigamajig on Mon, 2020/03/02 - 08:48

#3

I have tried reinstalling Bonjour, as that was the only similar issue I could find here on the support forums, but even after a fresh install the error still occurs. Also I thought that Bonjour was just for the auto find functionality but as I said even if I manually enter the IP address I get the same error over and over.

Is there maybe anything on the Pi itself that could need correcting? The status of the server on the Pi looks good, but I just don't know where else to look because it's such a vague error I'm getting.

Submitted by Michael on Mon, 2020/03/02 - 09:06

#4

What version of the server are you running? And what is the name of the binary of the server that you are running?

Submitted by gigamajig on Mon, 2020/03/02 - 09:50

#5

I'm using ./vhusbdarmpi3 version 4.0.6.

I'd like to make a note that I seem to have temporarily gotten a fix by manually searching for "raspberrypi.local.:7575" instead of the "raspberrypi-2.local" it was attempting to find on its own. I say temporarily, because I managed to get it fixed briefly, because this only seems to work until I close the client. Afterwards, I do have to do the Bonjour reinstallation process again every time I start the client, and I do have to keep that hub specified because the one it tries to auto find will not work.

I think it really IS Bonjour causing some pretty bad issues, but I can't seem to get a permanent fix on it.

Submitted by Michael on Mon, 2020/03/02 - 12:06

#6

In the client uncheck autofind hubs, then manually specify the IP address of the server, something is probably wrong with your bonjour setup but I'm not sure what it is