![]() ![]() If that doesn't clear up your issues, let me know. If your VNC client doesnt have ssh support compiled in, you will have to use an additional step to open the tunnel from your SSH client. sometimes it's on 5901, and it's important to remove this as a possible problem source. For hostname, enter: Destination: localhost: Using the above example, the source port would be 5915 and.Next, on REMOTE, please run netstat -an | grep 590 (not a typo, really 590) to make sure that your VNC software is listening on 5900 as expected. Creating an SSH tunnel On Windows, open PuTTY. ![]() This is almost certainly the source of the problem if you're not also using localhost in your putty config. 1 - Following is the command which i am using to establish the tunnel putty.exe -ssh w2182110.31.128.23 -L 5900:10.31.128.23:5900 2 - Following is my SSHDconfig file, This is the sshd server system-wide configuration file. It connects port 61000 on the local machine to port 5901 on the server via an SSH tunnel. If it's * or 0.0.0.0 then just use localhost.ĮDIT: I just noticed that you use "localhost" in your -R tunnel spec from REMOTE. Creating a SSH Tunnel The following command must be run on the client computer from which you are connecting to the VNC server. if it's 127.0.0.1 or localhost, you'll need to make sure that you put LOCALHOST as the "remote" part of the tunnel spec in putty. First, on HOP, please run netstat -an | grep 55900 and note what IP address the server is listening on. It is set to listen on 14900 and configured to 'Allow loopback' and only loopback connections. To this end I installed the TightVNC-server (2.8.8 GPL) on the Windows machine. Second (answering your original question), if you want to make sure that you're encrypting the session the entire way (completely reasonable) then I get why you want to use from LOCAL to HOP. 1 I need to connect to a particular Windows machine, which is behind firewall, from a remote Unix machine. first I'll answer with a different question: Since you can hit the ports you need on HOP from LOCAL, why not just have TightVNC Viewer connect directly to HOP:PORT? From a connectivity perspective, you shouldn't need to. I tried to change some putty options after looking for solutions on the web, as "enable X11 forwarding", or "Allow agent forwarding", but without success. Once the second tunnel is made on local, when I try to reach the remote SSH or VNC, the connection is straight closed.įor SSH (via another instance of putty), I get the error "Server unexpectedty closed the connection"įor VNC (TightVNC Viewer) : "Connection has been gracefully closed" From the hop, I can ssh the remote connecting to localhost port 50022 : ssh -p 50022 from the local, I make ssh tunnels to the hop, with putty : I want to connect hereĪs the remote has dynamic IP and is behind NAT, I make ssh reverse tunnels to the hop : ssh -R 55900:localhost:5900 -R 50022:localhost:22 step seems to work. 2 Answers Sorted by: 0 First of all you should check the vncsever is running with ps fax Then you must check the listening 5900 port with netstat -ntpl If the Unix server on the same LAN, just use vncviewer to the port. Remote : Linux box behind NAT, dynamic IP. ![]() I'm gettin a headache trying to access a remote VLC & SSH. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |