Huh. I’m more of a command-line guy myself, and don’t use VNC all that often - but the jetson does seen to have a pretty much default Ubuntu install on it, so any regular vnc method (eg, tigervnc) “should” just work … and just for my own sanity, I just tried it and it does indeed seem to work.
Here’s what I did (largely following this page that “extensive literature research” - ie, google - pointed me to: https://www.cyberciti.biz/faq/install-and-configure-tigervnc-server-on-ubuntu-18-04/).
First, on my jetson agx (named, fittingly, “jetson”):
wald@jetson: sudo apt install tigervnc-standalone-server
wald@jetson: mkdir ~/.vnc
Then create a file ~/.vnc/xstartup with the following content:
Start Gnome 3 Desktop
[ -x /etc/vnc/xstartup ] && exec /etc/vnc/xstartup
[ -r $HOME/.Xresources ] && xrdb $HOME/.Xresources
vncconfig -iconic &
dbus-launch --exit-with-session gnome-session &
Then once this file exists, start tigervnc
TigerVNC should now be running, but since you already have a gnome display running you’ll get some warnings about display :1 already being used, and it using display :2. That’s OK, but will mean that the port forwarding will look a bit different from what the google’d page suggests, namely, display :2 uses port 5902, not 5901.
Thus, from your remote machine (in my case a linux box named ‘trinity’, but putty should allow the same from windows, too): Create a port-forward of localhost:5902 to jetson:5902
wald@trinity: ssh -vv wald@jetson -L 5902:127.0.0.1:5902
Then once that port is forwarded you can connect with any vnc viewer, in my case tigervnc as well:
wald@trinity:~$ xtigervncviewer 127.0.0.1:5902
And la voila, i get a window with my remote desktop.
Now as I said above, I’m not exactly a windows expert, nor a frequent VNC user, so I won’t even try to give guidance on using tigervnc or port forwarding on windows… Both should work, but that’s as far as I’ll go :-)
Hope that helps!