- This topic has 1 reply, 2 voices, and was last updated 1 year, 10 months ago by
.
-
Posts
-
Forgive me if this question is too basic. I searched for VNC on the forum and got 32 pages of results, and trying to add more specific terms wasn’t working to narrow it down.
Looking at the documentation, as well as many posts, it doesn’t say specifically that when you use VNC it can be done from the WMS server’s web interface to a Thin Client at a remote site like somebody’s house (a remote worker).
When I’m in WMS, and I click on a thin client device, then go to “More Actions” > “Remote Shadow (VNC)” – the box that pops up has the thin clients PRIVATE IP in it (and port 5900 which can be edited) but the IP is greyed out. If I try and connect, a new tab opens that says “Starting VNC Handshake” but then goes to “Failed to connect to server (code: 101)”
I have a brand new test client at home running Windows 10. I can connect to the thin client from my home PC using VNC from inside my home network. But from the server, if it’s auto-filling the internal IP of the thin client, how will it ever be able to connect over a WAN to a remote users home? I’ve also tried using the VNC client to connect from another outside site using my WAN IP at home. That doesn’t work either.
If every remote user will need to setup port forwarding or something on their own personal router in order to get VNC working, that won’t scale for us. I figured each thin client might be listening or connecting back the WMS server on port 5900 so the outbound connection is already there – so the inbound traffic could just pass without having to change port forwarding or anything at the user’s house.
I’m I missing something? Or is VNC in WMS intended for thin clients that are used inside the corporate LAN?
- You must be logged in to reply to this topic.