I'm hoping this is something like I'm confused about which is the local host or something like that. The vnc server on A has port 5902 (I have turned loopback on and off, tried listening server). After starting the vnc server on machine A, an example of the initial ssh command I've gotten to work from A to B is: My assumption which may be the problem is to use reverse ssh from A->B (I've tried the -L option too instead of -R), and then use tightvnc to access machine A back from B. At that point person B on Machine B could VNC back to machine A and help. The idea would be Person A on machine A starts the VNC server on machine A, and connects over reverse ssh to machine B (so far so good). It is:Ĭurrently win10 vm (same LAN as machine A at present) I am wondering if my overall approach is flawed or not. It would appear others have gotten this to work, but am stumped.įor starters, have have gotten passwordless reverse ssh working between two windows 10 virtual machines (hyperv) on my laptop (i.e., I'm not trying to deal with port forwarding on my firewall or the static WAN address yet) but can't get the vcn to work over the reverse ssh tunnel, though it works just using the lan IP address instead of "localhost" for the reverse ssh. I've been trying to rough this out in small steps to manage the unknowns (for me, a lot:). I am trying to get a remote access approach (open source) working involving openssh and tightvnc that deals with NAT, that allows someone to remote to my server and then allows me to vnc back to their machine w/o having to mess with their firewall and allows me to use a static WAN address down the road.
|
AuthorWrite something about yourself. No need to be fancy, just an overview. Archives
March 2023
Categories |