7/1/2023 0 Comments Vnc viewer plusNow run your local VNCviewer application (an excellent free one is Chicken of the VNC) and connect to localhost:XX (remember this is the remote-machine-name the machine that you qlogin'ned into in and the same XX that you chose for vncserver in Step 1.) Ssh -L 59XX:remote-macine-name.bu.edu:59XX Now connect to the remote machine, and then run your local VNCviewer application (an excellent free one is TightVNC) and connect to localhost:XX (or localhost:59XX, depending on your VNC client.)Īlternate STEP 2 for MacOS with command-line ssh: Open a terminal window and ssh to eng-grid or eng-grid2 and do STEP 1 from there. (Remember this is the remote-machine-name of the machine that you qlogin'ned into and the same XX that you chose for vncserver in Step 1.) Under Add new forwarded port, use source port 59XX and destination port remote-machine-name.bu.edu:59XX But before you click Open, go to the Category menu and choose Connection->SSH->Tunnels For the host name, choose eng-grid or eng-grid2 again. (Use the PuTTy client - do a google search for it and download it if you don’t already have it.)Īlternate STEP 2 for Windows with PuTTy: Start up a PuTTy session and connect to eng-grid or eng-grid2, and do STEP 1 from there. If your VNC client doesn’t have ssh support compiled in, you will have to use an additional step to open the tunnel from your SSH client. # Uncomment the following two lines for normal desktop: You may want to edit your ~/.vnc/xstartup file and uncomment the two lines that it says to uncomment for “normal desktop”, and then you’ll get your full window manager, same as you’d see on any Linux lab machine in ENG. Now you can run whatever you want from here, such as: $ mwm &Īnd this will get you a very simple, fast window manager, and an xterm in your VNC window. STEP 3: Back in your first bash window: $ export DISPLAY=localhost:XX (where remote-machine-name.bu.edu is the remote machine that you qlogin'ned into) STEP 2: In a separate bash window, you will run vncviewer from the local client: $ vncviewer -via remote-machine-name.bu.edu localhost:XX If the VNCserver says it's already taken, pick a different one. Where XX is some two-digit number that you will remember. $ vncserver :XX -geometry 1024x768 -depth 16 -name yourloginname ![]() (or qlogin -q interactive.q or bme.q or wherever you need to be) Ssh to eng-grid.bu.edu or eng-grid2.bu.edu and once you’re logged in, run: $ qlogin ![]() STEP 1: From a bash window on your local client, you will ssh to the remote server: These instructions assume you are logging into the Engineering Grid as described in the main instructions but you can do this to any UN*X system you have access to just by ignoring the “qlogin” part. If your home client is running a full version of vncviewer (such as the one that comes with most Linux distributions), you can use vnc’s “-via” switch. Connect using the VNC session and enter the custom password.Make a new VNC-type session in MobaXterm (this can be re-used later) with these settings:.the digits for the screen number vncserver assigned you (5901 for :1, etc).the hostname of the system the grid assigned you.$ ssh 9999:hostname:59XX need to fill these parts: In a MobaXterm tab with a local shell (click the little “plus” icon at the top of the terminal pane to get a local shell if needed), run:.Log file is /home/user/.vnc/signals26:1.log Starting applications specified in /home/user/.vnc/xstartup New 'signals26:1 (jkgoebel)' desktop is signals26:1Ĭreating default config /home/user/.vnc/config ![]() Importantly, note the screen number assigned to your session after the hostname, like hostname:1 for screen vncserver
0 Comments
Leave a Reply. |