6/10/2023 0 Comments Vnc connect linux vs puttyEstablish a connection to ETH network with VPN If you wanna get into more deeply, read next paragraphs.ġ. If you wanna have fast access by using VNC, do this. R: This variable is used as a placeholder for the remote port on internal_host where a VNC server will be listening after a successfull startup. L: This variable is used as a placeholder for the local port on current_host where VNC connections will be made to. If you're using a shared student PC, check it's availability at login.Įth_username: This is the username you use to log in anywhere on an ETH provided IT service.Įth_password: This is your password used in combination with your eth_username which lets you access ETH provided IT services, except for network authentications (see below).Įth_network_password: This is your password also used in combination with your eth_username which is used for authentication to network services like Wifi and VPN. Students can use an arbitrary shared student room PC like tardis-d12. Internal_host: This is the fully qualified DNS name of the target host you intend to connect to, as shown by the command hostname -f on the target host. It is used to tunnel SSH connections in case you choose not to use VPN. Gateway_host: This is the entrance gateway to the ETH network to bypass the firewall restrictions for connections from the outside, by the name of login.ee.ethz.ch. It will run the software to view a remote Linux desktop, the VNC viewer. your office computer or home computer the host you are currently working on. Throughout his article, the following placeholders are used:Ĭurrent_host: This is a remote host in- or outside the ETH network, i.e. ![]() The following article explains how to access the desktop of a Linux host residing inside the ETH network from another host on the in- or outside by using Virtual Network Computing (VNC) 1. Remote access to a Linux host's desktop with VNC Connect your VNC viewer to the VNC server on internal_host.Use a VNC viewer to view and control the desktop on internal_host.Terminating a running VNC server process.SSH connection on Windows 10 with OpenSSH.Initiate a SSH connection to internal_host.Alternative method: Connect through an SSH tunnel.Initiate a VPN connection to internal_host.Install the VPN client on your current host.Preferred method: Connect through a VPN connection.Remote access to a Linux host's desktop with VNC.It therefore seems that PuTTY appears to have the tendency to not properly close the tunnel to the server upon logout. by using pkill ssh (to kill all current ssh connections). Under linux it seems I can effectively kill the ssh tunnel, e.g. If anybody knows a way to speed up the process, I would be grateful to hear the solution. It seems that everything is functional, but that there is a cool down period after I close my connection with PuTTY before I can establish another connection from a different instance of Windows or Linux. Proto Recv-Q Send-Q Local Address Foreign Address State The out put of netstat -tulpn might also be relevant: Active Internet connections (only servers) The main issue here is perhaps that when I close PuTTY, the connection is still active (I just tested this, as I was still able to connect to vnc using localhost:5901). ![]() ![]() (Perhaps there is some sort of cool down setting I am not aware of after a connection has been closed out that still keeps the connection open/address assigned?)Įdit: This is the error I receive using PuTTY on Linux if the address hasn't reset yet: ![]() It seems I am able to connect using the same settings, and I can connect to vnc, though this wasn't working earlier. I also tried to tunnel on Debian using PuTTY and the same settings I have under Windows. I'm not sure what this means, but it sounds as though the previous connection I opened under Windows is still active somehow? Gives the following output (I have shortened the output): debug1: Local connections to LOCALHOST:5901 forwarded to remoteĭebug1: Local forwarding listening on 127.0.0.1 port 5901.ĭebug1: Local forwarding listening on ::1 port 5901.Ĭhannel_setup_fwd_listener_tcpip: cannot listen to port: 5901ĭebug1: Requesting forking to background Running the same command with the verbose option: ssh - v -L 5901:127.0.0.1:5901 -N -f -l username server_ip_address I receive an error: bind: Cannot assign requested address On the same laptop, if I boot into Debian 9 to try to replicate the connection using: ssh -L 5901:127.0.0.1:5901 -N -f -l username server_ip_address Using my laptop, I am able to establish an SSH tunnel connection using PuTTY on Windows and establish a connection to vnc through localhost:5901. I have a Linux server running xtightvnc on Ubuntu 18.04.
0 Comments
Leave a Reply. |