![]() ![]() To start using it you need a config like this: # LocalPort TargetHost TargetPort SshHost SshUsername SshKeyPathġ8080 80 User D:\secure\path\to\private_key. That's why I come up with custom Powershell script, easy configurable, changeable, small, but works. I tried many solutions like SSH tunnel managers, but all were inconvinient for me: too many configuration screens, sometimes buggy (one time SSH tunnel manager purged all! settings I had! So I had to restore settings for all 30 tunnels). I did find this question: How to reliably keep an SSH tunnel open?, but that's using Linux as the SSH client, and I'm using Windows. Look for SSH Server Broker and SSH Server Proxy in the Services. You should then be able to work on the remote. Open the run box by pressing Start+R, then enter services.msc to open the Services window. I'm planning on making a dedicated user with no privileges and not allowed to interactively log in, and use that.) 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. (Yes, I am aware of the hazards of automatically logging in to SSH. In windows I would use applications like freecap + putty combo. The two tunnels are one local tunnel, and one remote tunnel. Next, you would start another instance of PuTTY and use localhost:7000 as the host. First you need to setup a tunnel to outside using the 'Local' radio button with the 'Source Port' set to 7000 and the 'Destination' set to inside:22. Vino, 230 Virtual Network Computing (see VNC) VLAN (Virtual LAN), 586 VLANs, 9. So to answer your second question first, yes, both steps are done from PuTTY. The data I'm sending across the two tunnels is VNC connections, so I often won't be at the machine to clear errors and enter passwords. tunnel brokers (6to4), 451 tunneling, 205 X Windows over SSH, 220 x11vnc. What I'd like to do is have an application that can set up the two SSH tunnels, and can automatically reconnect, without needing to manually do anything, including enter a password. This works well, except when the SSH connection drops: PuTTY displays an error message, and I need to manually close the error and reconnect to the server. I'm trying to set up a Windows computer to always have two SSH tunnels to my Linux server.Ĭurrently, I'm using PuTTY to open the two SSH tunnels: I log in to the server in PuTTY, leave it minimized, and never touch it. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |