Connecting via ZeroTier

Submitted by DiggyBong on #1

Hiya,

I've a team who can all successfully connect to VirtualHere via Zerotier. Amazing how well it works.

But there is this one laptop that used to be able to connect but now cannot. I've tried it on multiple networks, and verified the network isn't an issue by successfully connecting other devices on those networks.

I've tried uninstalling and re-installing VirtualHere and ZeroTier multiple times, and that doesnt solve the issue.

This one laptop can connect when physically plugged into the same LAN as the dongle server, but never remotely via the ZeroTier network.

Any ideas of what to try, logs to check etc?

Submitted by Michael on Tue, 2025/04/01 - 07:11

#2

Try tailscale, that is also good

Submitted by DiggyBong on Tue, 2025/04/01 - 20:22

#3

Thanks, but that doesn't really help the issue.

Any other ideas of what to check to figure this out?

Submitted by Michael on Tue, 2025/04/01 - 21:22

#4

Ok no sorry, I don't debug network issues.

 What I meant is that I find tailscale is a bit better than zeroteir though difficult networks. So it's worth giving that a try if it's not too hatd

Submitted by DiggyBong on Tue, 2025/04/01 - 22:01

#5

Ahh, ok. I was posting because I wasn't sure if it was a VirtualHere issue or not. I am trying to figure out if there is some logging that I can access in VirtualHere that could help me.

No issues on 10 other devices with ZeroTier, and Tailscale doesn't fit our commercial needs, but that's a separate issue.

I'm really asking if you have any guidance on logs and other info I can gleam from VirtualHere to help me find the cause of the issue.

Submitted by Michael on Wed, 2025/04/02 - 02:17

#6

Virtualhere does not have any extra logging, regarding initiating a connection. If a connection is successfully established and then drops that is logged in the server and client with a bit of extra technical information.

Try using plain putty and telnet to port 7575. Does that work? It should return some garbage characters after a few seconds.

 

Submitted by DiggyBong on Thu, 2025/04/03 - 19:46

#7

Thanks for the reply.

I can't telnet into the server using putty on that port; it doesn't return any text at all and just says it can't connect. I can telnet in using the standard SSH port. And the "netstat -lntu" command shows 7575 TCP is open, as is 5353 udp open.

As we have 10 devices that can connect to the server, I suspect it's a local laptop issue. We've tried configuring the firewall on that (and disabling it fully!) and that isn't work.

We've given up and are rebuilding the laptop from scratch, with a fresh install of windows.

 

Submitted by Michael on Fri, 2025/04/04 - 07:21

#8

OK let me know if that resolves it