While I using MobaXTerm I can make a ssh connection to remote machine and I can use Ctrl+C combination to kill a process that works on remote machine. But while I use PuTTy I can make a ssh to remote machine but the Ctrl+C combination works on local machine and kills ssh session.
It wasn't like that at first times but I think so something has changed (it is not my personal computer, it's a work computer). I cannot use Ctrl+C combination to kill any process on remote machine via PuTTy. How can I change this setting to get same with MobaXTerm (Ctrl+C kills the process on remote machine, not the ssh session on local machine).
For clear anything, the scenario is like this:
- I connect to our main Linux server (host1) -that open to everywhere- from my PC (windows). I go to anywhere must from here.
- I make ssh to client1 from this terminal machine (host1). Because there is no way to make ssh to client1 (Linux) from local pc directly.
While I working on client1 if I hit Ctrl+C from any reason I lose my ssh connection between host1 and client1 and I fall to host1. And the output is: "Killed by signal 2"
[client1 ~]# <-- I hit Ctrl+C here [client1 ~]# Killed by signal 2. [host1 ~]#
Edit: I detected another issue about this problem. Maybe It be a clue: If I login to host1 with using GUI of MobaXTerm, same problem is happenning (killing ssh session). But, if I use command line to make ssh on local to host1 (ssh host1 command) problem doesn't happen on client1. And If the problem will be happened the "dzdo" command hangs while checking the password until I hit enter. This hanging problem is exist on PuTTy already.
Edit & Note: I deleted PuTTy settings with using regedit (delete \HKEY_CURRENT_USER\Software\SimonTatham) and everything is OK. But I won't be learned the reason of the problem anymore.
