![]() ppk on both my machines and I can connect to all my servers from both machines - only the forwarding does not work on the desktop machine. ![]() InterfaceAlias : Loopback Pseudo-Interface 1 Click on Session and then enter a name under Saved sessions and click on Save. In the Auto-login username field, enter mullvad. Note that excluding the username before the remote IP, makes ssh use the current username. Enable 'Don't start a shell or command at all'. Otherwise, check that the SSH key is installed in the remote. ServerAliveInterval (default 10): How often (in seconds) SSH will send a packet to check whether the connection is working. If you see the command in the output, we can proceed. WARNING: TCP connect to (127.0.0.1 : 49900) failed To check that the process is running, we can do: local: ps aux grep ssh. Test-NetConnection -ComputerName 127.0.0.1 -Port 49900 I've tried testing the port in Powershell on Windows 10 (below), as well as on two other servers (none of them works, including forwarding web ports): The easiest way to test that the connection is up, is to telnet to the port the forward has been created on (in your example 9999): telnet localhost 9999. When trying the same thing on my desktop (W10 Pro v1909), Workbench errors with Unable to connect to 127.0.0.1:49900 All it does is tell your computer to open up port 9999, and forward connections to that port to the remote machine (timserver) via your ssh connection. You can enter a port of your choice that you want to connect to under. I have an identical setup on my laptop (W10 Enterprise v1809) and it works fine, with both the PuTTY and Workbench configs exported from my laptop. On the left side, click Connection > SSH >Tunnels. You can then save this proxy configuration as PuTTY stored session. For details, see OpenSSH Prox圜ommand equivalent in PuTTY. This way, you can implement an SSH tunnel. In Workbench, I try to connect to localhost on port 49900 after establishing the SSH connection through PuTTY, but it fails to connect: Unable to connect to 127.0.0.1:49900 In PuTTY, you can use plink for 'local proxy command'.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |