![]() ![]() VNC’s main function is to remotely control a computer (server) from a local computer (client) while displaying the VNC server’s screen content on the local monitor. Enjoy tunnelling VNC through SSH.VNC (Virtual Network Computing) was developed in the 1980s as a technique for controlling computers remotely. Not only is your VNC connection good to go, but it’s also more secure than if you had simply used the default VNC port. You should then be able to work on the remote desktop, using VNC, thanks to SSH. Once you click connect, your VNC client will use the encrypted SSH tunnel and make the connection between local and remote machines on port 5901. Why? Because we’ve created an SSH tunnel from localhost:5901 to REMOTE_IP:5901 (where REMOTE_IP is the IP address of the remote machine). Instead of entering, say, 192.168.1.83:5901 for the remote address, enter localhost:5901. What does matter, however, is the address you use to make the connection. ![]() ( See: How to set up ssh key authentication.) Connecting your VNC Client Note: For an even more secure connection, I suggest you make use of SSH Key Authentication. Ssh -L 5901:localhost:5901 USER is the remote username and REMOTE_IP is the remote IP address. If you do not, you can always add the remote username like so: This will assume you have the same username on both local and remote machines. You will then be prompted for the remote user’s password. If you’ve never SSH’d to this remote host, you will be asked if you want to add the remote host to your local ~/.ssh/known_hosts file ( Figure A). Where REMOTE_IP is the IP address of the remote host. The first thing to do is create the tunnel that routes packets from localhost (at port 5901) to the remote host (at port 5901) through port 22. I will assume you already have everything you need installed, and your VNC server is running and accepting connections.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |