Why is Windows routing not respected?

[Daniel Miller]

I've lost a little hair diagnosing this - I didn't have it to lose.

My office location's IP has been allowed to pass the firewall of a remote VNC server. So if I need to access the remote location I have to do it through my office router.

I have a Wireguard VPN connection to my office. The remote IP is allowed to pass through the Wireguard peer config. Yet I simply could not get TurboVNC to connect. Checking packet logs I see no traffic coming from my PC to my gateway.

I've been checking every network config I have and second, third, and fourth guessing myself trying to figure out what's broken. Finally, on a whim, I tried a different VNC program. It worked.

I'm running Windows 11, TurboVNC x64 v3 (previously 3.0, now 3.0.1). I don't know what else to share or what else to check to resolve this.

[DRC]

I have no idea, unfortunately. Could it have something to do with IPv4 vs. IPv6? How exactly are you trying to connect with TurboVNC? What was the other VNC viewer you tried that worked? Are you using the TurboVNC server or a different VNC server?

On Nov 25, 2022, at 9:34 PM, Daniel Miller <heavyt...@gmail.com> wrote:



--
You received this message because you are subscribed to the Google Groups "TurboVNC User Discussion/Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email to turbovnc-user...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/turbovnc-users/e020c632-3e4a-4b3b-a717-7a04d6422e8bn%40googlegroups.com.

[DRC]

I would love to help you resolve this issue, but I need you to answer my
questions first.

DRC